[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaZvQ0eazTnxbxKmhHWCk2yT3mkBHM=vAMytLK3H6VFyw@mail.gmail.com>
Date: Wed, 10 Feb 2016 15:23:43 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: "Andrew F. Davis" <afd@...com>
Cc: "linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>,
Richard Purdie <rpurdie@...ys.net>,
Jacek Anaszewski <j.anaszewski@...sung.com>,
Alexandre Courbot <gnurou@...il.com>,
Javier Martinez Canillas <javier@...hile0.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] gpio: Add driver for TI TPIC2810
On Thu, Jan 28, 2016 at 3:56 PM, Andrew F. Davis <afd@...com> wrote:
>> I understand that it can also be used as a GPIO (and that it
>> is then nice to put leds-gpio on top of it) but then
>> I want a reference to the hardware that actually went ahead
>> and used this as a GPIO chip rather than using a proper
>> GPIO expander.
>
> These don't really have the traditional LED features (current control,
> HW blinking, etc), and all the use cases I've found treat them as GPO,
> including our Industrial Dev Kits (although they run them to test LEDs
> as well as the IO header):
>
> http://www.ti.com/tool/tmdsice3359
> http://www.ti.com/tool/tmdxidk437x
>
> And a couple more that I don't think have any public schematics yet.
>
> Like you said, they can still be used for LEDs with leds-gpio, as they
> don't have any LED specific features I figure this way we get both
> uses with one driver.
Fair enough, merged as you see.
Yours,
Linus Walleij
Powered by blists - more mailing lists