[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191007124437.20367-2-jjhiblot@ti.com>
Date: Mon, 7 Oct 2019 14:44:33 +0200
From: Jean-Jacques Hiblot <jjhiblot@...com>
To: <jacek.anaszewski@...il.com>, <pavel@....cz>, <sre@...nel.org>,
<robh+dt@...nel.org>, <mark.rutland@....com>,
<lee.jones@...aro.org>, <daniel.thompson@...aro.org>
CC: <dmurphy@...com>, <linux-leds@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<tomi.valkeinen@...com>, Jean-Jacques Hiblot <jjhiblot@...com>
Subject: [PATCH v9 1/5] leds: populate the device's of_node
If initialization data is available and its fwnode is actually a of_node,
store this information in the led device's structure. This will allow the
device to use or provide OF-based API such (devm_xxx).
Signed-off-by: Jean-Jacques Hiblot <jjhiblot@...com>
---
drivers/leds/led-class.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
index 647b1263c579..bfa1b1033274 100644
--- a/drivers/leds/led-class.c
+++ b/drivers/leds/led-class.c
@@ -276,8 +276,10 @@ int led_classdev_register_ext(struct device *parent,
mutex_unlock(&led_cdev->led_access);
return PTR_ERR(led_cdev->dev);
}
- if (init_data && init_data->fwnode)
+ if (init_data && init_data->fwnode) {
led_cdev->dev->fwnode = init_data->fwnode;
+ led_cdev->dev->of_node = to_of_node(init_data->fwnode);
+ }
if (ret)
dev_warn(parent, "Led %s renamed to %s due to name collision",
--
2.17.1
Powered by blists - more mailing lists