linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: anilkumar@ti.com (AnilKumar Ch)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] leds: leds-gpio: adopt pinctrl support
Date: Sat, 1 Sep 2012 13:46:30 +0530	[thread overview]
Message-ID: <1346487390-11399-1-git-send-email-anilkumar@ti.com> (raw)

Adopt pinctrl support to leds-gpio driver based on leds-gpio
device pointer, pinctrl driver configure SoC pins to GPIO
mode according to definitions provided in .dts file.

Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
---
Changes from v1:
	- Seperated from "Add DT for AM33XX devices" patch series
	- Incorporated Tony's comments on v1
	  * Changed to warning message instead od error return

 drivers/leds/leds-gpio.c |    7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
index c032b21..ad577f4 100644
--- a/drivers/leds/leds-gpio.c
+++ b/drivers/leds/leds-gpio.c
@@ -20,6 +20,7 @@
 #include <linux/slab.h>
 #include <linux/workqueue.h>
 #include <linux/module.h>
+#include <linux/pinctrl/consumer.h>
 
 struct gpio_led_data {
 	struct led_classdev cdev;
@@ -236,8 +237,14 @@ static int __devinit gpio_led_probe(struct platform_device *pdev)
 {
 	struct gpio_led_platform_data *pdata = pdev->dev.platform_data;
 	struct gpio_leds_priv *priv;
+	struct pinctrl *pinctrl;
 	int i, ret = 0;
 
+	pinctrl = devm_pinctrl_get_select_default(&pdev->dev);
+	if (IS_ERR(pinctrl))
+		dev_warn(&pdev->dev,
+			"pins are not configured from the driver\n");
+
 	if (pdata && pdata->num_leds) {
 		priv = devm_kzalloc(&pdev->dev,
 				sizeof_gpio_leds_priv(pdata->num_leds),
-- 
1.7.9.5

             reply	other threads:[~2012-09-01  8:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-01  8:16 AnilKumar Ch [this message]
2012-09-05  3:06 ` [PATCH v2] leds: leds-gpio: adopt pinctrl support Bryan Wu
2012-09-05  3:13   ` Marek Vasut
2012-09-05 23:34     ` Tony Lindgren
2012-09-06  2:05       ` Marek Vasut
2012-09-06 17:45         ` Tony Lindgren
2012-09-07  0:09           ` Marek Vasut
2012-09-07  7:59             ` AnilKumar, Chimata
2012-09-07  8:22               ` Marek Vasut
2012-09-07 16:00               ` Bryan Wu
2012-09-07 21:39           ` Linus Walleij
2012-09-07 21:46             ` Tony Lindgren
2012-09-07  8:48 ` Domenico Andreoli
2012-09-07  9:10   ` AnilKumar, Chimata
2012-09-07 11:02     ` Domenico Andreoli
2012-09-07 14:30       ` AnilKumar, Chimata
2012-09-07 16:00         ` Domenico Andreoli
2012-09-07 16:35           ` Tony Lindgren
2012-09-07 21:59             ` Linus Walleij
2012-09-07 21:57           ` Linus Walleij
2012-09-08 23:44             ` Domenico Andreoli
2012-09-10 15:23               ` Linus Walleij
2012-09-10 17:41                 ` Stephen Warren
2012-09-10 19:34                   ` Linus Walleij
2012-09-10 19:44                     ` Stephen Warren
2012-09-07 21:36 ` Linus Walleij
2012-09-10 19:40 ` Linus Walleij
2012-10-01  7:03   ` AnilKumar, Chimata
2012-10-01  8:24     ` Linus Walleij
2012-10-01 15:44       ` Tony Lindgren
2012-10-01 19:59         ` Linus Walleij
2012-10-03 10:52           ` AnilKumar, Chimata
2012-10-03 12:36             ` Linus Walleij
2012-10-30 14:12               ` AnilKumar, Chimata
2012-11-04 17:37                 ` Linus Walleij
2012-11-05  6:44                   ` AnilKumar, Chimata
2012-11-05 16:27                   ` Tony Lindgren
2012-10-03 15:53             ` Tony Lindgren

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=1346487390-11399-1-git-send-email-anilkumar@ti.com \
    --to=anilkumar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).