[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ee32b9a0d6f8ecef9c70fb684e5e29b873993cf5.camel@alliedtelesis.co.nz>
Date: Mon, 4 Nov 2019 19:58:52 +0000
From: Chris Packham <Chris.Packham@...iedtelesis.co.nz>
To: "linus.walleij@...aro.org" <linus.walleij@...aro.org>
CC: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bcm-kernel-feedback-list@...adcom.com"
<bcm-kernel-feedback-list@...adcom.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"sbranden@...adcom.com" <sbranden@...adcom.com>,
"rjui@...adcom.com" <rjui@...adcom.com>
Subject: Re: [PATCH v3 2/2] pinctrl: bcm: nsp: implement get_direction
On Mon, 2019-11-04 at 16:24 +0100, Linus Walleij wrote:
> On Mon, Nov 4, 2019 at 1:18 AM Chris Packham
> <chris.packham@...iedtelesis.co.nz> wrote:
>
> > The get_direction api is strongly recommended to be implemented. In fact
> > if it is not implemented gpio-hogs will not get the correct direction.
> > Add an implementation of get_direction for the nsp-gpio driver.
> >
> > Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
> > Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
>
> BTW I think it looks like this the GPIO part of this driver can be
> converted to use GPIO_GENERIC. Compare to other
> drivers such as drivers/gpio/gpio-ftgpio010.c.
>
> It's a fun way to cut down lines if you have time to check
> and test!
>
I'll see if I can fit it in. Got another problem I'm chasing on the
same platform.
Powered by blists - more mailing lists