From: Daniel Mack <daniel@zonque.org>
To: jacek.anaszewski@gmail.com, robh+dt@kernel.org
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
Daniel Mack <daniel@zonque.org>
Subject: [PATCH] leds: lt3593: Move GPIO node from child to device node
Date: Tue, 26 Jun 2018 22:22:52 +0200 [thread overview]
Message-ID: <20180626202252.6127-1-daniel@zonque.org> (raw)
Move the GPIO node from the child node to the device node as it
is a property of the chip, not of the LED.
Reported-by: Rob Herring <robh@kernel.org>
Signed-off-by: Daniel Mack <daniel@zonque.org>
---
.../devicetree/bindings/leds/leds-lt3593.txt | 10 ++++------
drivers/leds/leds-lt3593.c | 12 ++++--------
2 files changed, 8 insertions(+), 14 deletions(-)
diff --git a/Documentation/devicetree/bindings/leds/leds-lt3593.txt b/Documentation/devicetree/bindings/leds/leds-lt3593.txt
index b31d427448f8..6b2cabc36c0c 100644
--- a/Documentation/devicetree/bindings/leds/leds-lt3593.txt
+++ b/Documentation/devicetree/bindings/leds/leds-lt3593.txt
@@ -1,15 +1,13 @@
Bindings for Linear Technologies LT3593 LED controller
Required properties:
-- compatible: Should be "lltc,lt3593".
+- compatible: Should be "lltc,lt3593".
+- lltc,ctrl-gpios: A handle to the GPIO that is connected to the 'CTRL'
+ pin of the chip.
The hardware supports only one LED. The properties of this LED are
configured in a sub-node in the device node.
-Required sub-node properties:
-- gpios: A handle to the GPIO that is connected to the 'CTRL'
- pin of the chip.
-
Optional sub-node properties:
- label: A label for the LED. If none is given, the LED will be
named "lt3595::".
@@ -25,10 +23,10 @@ Example:
led-controller {
compatible = "lltc,lt3593";
+ lltc,ctrl-gpios = <&gpio 0 GPIO_ACTIVE_HIGH>;
led {
label = "white:backlight";
- gpios = <&gpio 0 GPIO_ACTIVE_HIGH>;
default-state = "on";
};
};
diff --git a/drivers/leds/leds-lt3593.c b/drivers/leds/leds-lt3593.c
index f6aae616242e..9d4896aa8475 100644
--- a/drivers/leds/leds-lt3593.c
+++ b/drivers/leds/leds-lt3593.c
@@ -133,6 +133,10 @@ static int lt3593_led_probe(struct platform_device *pdev)
return -EINVAL;
}
+ led_data->gpiod = devm_gpiod_get(dev, "lltc,ctrl", 0);
+ if (IS_ERR(led_data->gpiod))
+ return PTR_ERR(led_data->gpiod);
+
child = device_get_next_child_node(dev, NULL);
ret = fwnode_property_read_string(child, "label", &tmp);
@@ -156,14 +160,6 @@ static int lt3593_led_probe(struct platform_device *pdev)
}
}
- led_data->gpiod = devm_fwnode_get_gpiod_from_child(dev, NULL, child,
- flags,
- led_data->name);
- if (IS_ERR(led_data->gpiod)) {
- fwnode_handle_put(child);
- return PTR_ERR(led_data->gpiod);
- }
-
led_data->cdev.name = led_data->name;
led_data->cdev.brightness_set_blocking = lt3593_led_set;
led_data->cdev.brightness = state ? LED_FULL : LED_OFF;
--
2.17.1
next reply other threads:[~2018-06-26 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 20:22 Daniel Mack [this message]
2018-06-27 17:59 ` [PATCH] leds: lt3593: Move GPIO node from child to device node Jacek Anaszewski
2018-06-27 18:47 ` Daniel Mack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180626202252.6127-1-daniel@zonque.org \
--to=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).