From patchwork Tue Dec 12 22:01:37 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dan Murphy X-Patchwork-Id: 121659 Delivered-To: patch@linaro.org Received: by 10.140.22.227 with SMTP id 90csp4680918qgn; Tue, 12 Dec 2017 14:02:11 -0800 (PST) X-Google-Smtp-Source: ACJfBouoEsn7Es56mdbiJzYHbrpmNQHtqTjdstwlNiLUEKKs2la6Y1yenR87jz0XHy1lPfuD+ktx X-Received: by 10.98.178.17 with SMTP id x17mr3646968pfe.239.1513116131330; Tue, 12 Dec 2017 14:02:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1513116131; cv=none; d=google.com; s=arc-20160816; b=kaurz5G0mM7sfXYSUPB5YWrHjWoX722c8Zh0sPcPHCT8fTuj2Bz7Wk8pdC4TkN63AJ U425cmnKymSzK6Y/+wmI+acwvucbvo/BA2eo8pBP+RZ+VA9TxmPc3emFOahwNCeL6A3p UqJRSC/o9vQUTfbPOiBRhgV4ZHn9EgEm7ZoAa0pBL/pTQzrAN1ZWON4P37U4HWNzz9Dk coVm2u/u4R85o1evisyHVu4RK4/VZ1+rPTllIr8n9rNtaHlx4gBckihZ1VQzuV5Eamsd 5vbxTCWUmT56u4IKUXNBQGN+n8dPUgtee6GABQdI5saDktsZZoKcgMUygY0Y13W+C4iK Li2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:cc :to:from:dkim-signature:arc-authentication-results; bh=dVTScYWUvSnElvAPwRbsXkzqatnruXRm5nAi+UJOYF4=; b=NcjjmFgzR/RomM7GnLl3mxabvQ/FpHxBRhr8hMl8s0FKUg9mYSSssouxL36/yCdCNF IZ1kRoGj7g1ZovblL7cw3gWRieDlZOGgMAxvVmwX3cBzpnpU+t/OJDTb5LzVlrdaXqta Z9fR3G4AAR7+Yr/HyVmaV+GvZO3hUfUxMPOw7NCvDuIwc9EMswdMfCcz2tIzOLQ7DeBe 2LN/BVVcDkGt5mOsi/H073N4i2oc2KA1P/6P99wD3M03I8hAEbhXhX9jj2LGAxEiSEeg j9R61c4CP12YZn1QTYzVtL1GND7RuXq3Lve63W6a7fXRrh8YvAojwY6jFsleOv2q4B1P ar8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=neutral (body hash did not verify) header.i=@ti.com header.s=ti-com-17Q1 header.b=GfkyoV40; spf=pass (google.com: best guess record for domain of devicetree-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=devicetree-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l1si134480pld.20.2017.12.12.14.02.11; Tue, 12 Dec 2017 14:02:11 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of devicetree-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@ti.com header.s=ti-com-17Q1 header.b=GfkyoV40; spf=pass (google.com: best guess record for domain of devicetree-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=devicetree-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752790AbdLLWCJ (ORCPT + 6 others); Tue, 12 Dec 2017 17:02:09 -0500 Received: from fllnx210.ext.ti.com ([198.47.19.17]:24953 "EHLO fllnx210.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752603AbdLLWCD (ORCPT ); Tue, 12 Dec 2017 17:02:03 -0500 Received: from dlelxv90.itg.ti.com ([172.17.2.17]) by fllnx210.ext.ti.com (8.15.1/8.15.1) with ESMTP id vBCM1lWg015494; Tue, 12 Dec 2017 16:01:47 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1513116107; bh=roqLlb/+ubPtP8HapXPJ1G+o2VuEqxQnySpQCkuab0E=; h=From:To:CC:Subject:Date; b=GfkyoV40EGUb0U8NH+Lwn56jeB+Jz0nmQfh6Go5hjYtbhHnC16xMbhv2GKXUgUpVQ C46WkKxDgrVys3QlyaN3GzdC2GZ0j7O+GczblQMl45XKUl12ooyDbQbgEv5defCm8h GZ728xE0ZwsrdcfGYKKUhXxga8O1S12Rx45IqRNk= Received: from DFLE115.ent.ti.com (dfle115.ent.ti.com [10.64.6.36]) by dlelxv90.itg.ti.com (8.14.3/8.13.8) with ESMTP id vBCM1lmC022601; Tue, 12 Dec 2017 16:01:47 -0600 Received: from DFLE107.ent.ti.com (10.64.6.28) by DFLE115.ent.ti.com (10.64.6.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.845.34; Tue, 12 Dec 2017 16:01:46 -0600 Received: from dflp33.itg.ti.com (10.64.6.16) by DFLE107.ent.ti.com (10.64.6.28) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.1.845.34 via Frontend Transport; Tue, 12 Dec 2017 16:01:46 -0600 Received: from legion.dal.design.ti.com (legion.dal.design.ti.com [128.247.22.53]) by dflp33.itg.ti.com (8.14.3/8.13.8) with ESMTP id vBCM1k1O026190; Tue, 12 Dec 2017 16:01:46 -0600 Received: from localhost (a0272616local-lt.dhcp.ti.com [172.22.69.253]) by legion.dal.design.ti.com (8.11.7p1+Sun/8.11.7) with ESMTP id vBCM1kx11329; Tue, 12 Dec 2017 16:01:46 -0600 (CST) From: Dan Murphy To: , , , , CC: , , , Dan Murphy Subject: [PATCH v4 0/6] Updated LP8860 driver series Date: Tue, 12 Dec 2017 16:01:37 -0600 Message-ID: <20171212220143.31210-1-dmurphy@ti.com> X-Mailer: git-send-email 2.12.2 MIME-Version: 1.0 X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org All v4 - Fix checkpatch warning for code indentation on the leds: lp8860: Update the dt parsing for LED labeling patch. v3 - Made changes to the patch set to address concerns on DT node naming conventions based on discussion in the RFC patch https://patchwork.kernel.org/patch/10089047/ also made requested changes to the DT and driver based on feedback. Patchworks links in each patch. v2 - Added an initial patch to bring the DT binding up to standard prior to adding the changes for the label and triggers. v1 Cover letter repeat below After creating a new LED driver for the LM3692x device I went back to the LP8860 driver that I authored and found some updates that need to be applied. First the way the LP8860 retrieved the label from the DT was incorrect as the label should have been from a child node as opposed to the parent. This is now fixed with this series. Second, since that device can be used to as either a backlight driver or as a string agnostic driver a trigger to the backlight needed to be added. Finally there are changes to the driver that need to be made as either unnoticed bugs or updates to the driver to align with the current LED framework. For instance moving to the devm LED class registration, destroying the mutex upon driver removal and removing the in driver dependency on CONFIG_OF and moving it to the Kconfig. With these changes this should at least bring the driver into a better shape. There are additional changes coming for this driver but I wanted to get the driver up to snuff before adding a feature to it. Dan Dan Murphy (6): dt: bindings: lp8860: Update bindings for lp8860 dt: bindings: lp8860: Update DT label binding leds: lp8860: Update the dt parsing for LED labeling dt: bindings: lp8860: Add trigger binding to the lp8860 leds: lp8860: Add DT parsing to retrieve the trigger node leds: lp8860: Various fixes to align with LED framework .../devicetree/bindings/leds/leds-lp8860.txt | 32 ++++++++++++----- drivers/leds/Kconfig | 2 +- drivers/leds/leds-lp8860.c | 40 ++++++++++++---------- 3 files changed, 46 insertions(+), 28 deletions(-) -- 2.15.0.124.g7668cbc60 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html