linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: cavokz@gmail.com (Domenico Andreoli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] leds: leds-gpio: adopt pinctrl support
Date: Fri, 7 Sep 2012 13:02:51 +0200	[thread overview]
Message-ID: <20120907110251.GA7968@glitch> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA29819@DBDE01.ent.ti.com>

On Fri, Sep 07, 2012 at 09:10:50AM +0000, AnilKumar, Chimata wrote:
> Hi Domenico,

Hi,

> On Fri, Sep 07, 2012 at 14:18:39, Domenico Andreoli wrote:
> > On Sat, Sep 1, 2012 at 10:16 AM, AnilKumar Ch <anilkumar@ti.com> wrote:
> > > 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.
> > 
> > Shouldn't be the interaction with the pinctrl layer left to gpiolib?
> > 
> 
> No, these gpio's are configured specifically for user leds.

So there are some special pad configs to make the leds work which are not
only muxing and direction setting? Because I expect these to be managed
privately between gpiolib and pinctrl but now I'm not sure any more,
I'll look the code.

> So, leds-gpio driver should have this call, because these gpio
> pins are used by leds-gpio driver.
> 
> +       am33xx_pinmux: pinmux at 44e10800 {
> +               userled_pins: pinmux_userled_pins {
> +                       pinctrl-single,pins = <
> +                               0x54 0x7       
> +                               0x58 0x17       
> +                               0x5c 0x7        
> +                               0x60 0x17       
> +                       >;
> +               };
> +       };
> +
> 
> [...]
> 
> +               leds {
> +                       compatible = "gpio-leds";
> +                       pinctrl-names = "default";
> +                       pinctrl-0 = <&userled_pins>;
>                                       ^^^^^^^^^^^^

I'm surprised to not see any gpio controller (ala irq) involved.

> Lets take gpio-keypad driver, in that case we have to configure
> pins as INPUT mode (generic gpio driver might not know what
> the end usecase is) and this leds case we configure as OUTPUT
> mode.

gpio direction is modeled by gpiolib so, if no other out-of-gpiolib
capabilities are required for that led gpio, there is no need to directly
use pinctrl.

maybe I've just got it wrong. sorry.

thanks,
Domenico

  reply	other threads:[~2012-09-07 11:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-01  8:16 [PATCH v2] leds: leds-gpio: adopt pinctrl support AnilKumar Ch
2012-09-05  3:06 ` 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 [this message]
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=20120907110251.GA7968@glitch \
    --to=cavokz@gmail.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).