On Thu, Mar 02, 2023 at 10:54:57AM +0800, Kever Yang wrote:
> Hi Linus,
>
> On 2023/2/23 16:59, Linus Walleij wrote:
> > On Mon, Feb 13, 2023 at 11:28 PM Chris Morgan
> > wrote:
> >
> > > From: Chris Morgan
> > >
> > > Use the new devicetree property of gpio-ranges to determine the GPIO
> > >
Hi Linus,
On 2023/2/23 16:59, Linus Walleij wrote:
On Mon, Feb 13, 2023 at 11:28 PM Chris Morgan wrote:
From: Chris Morgan
Use the new devicetree property of gpio-ranges to determine the GPIO
bank ID. Preserve the "old" way of doing things too, so that boards
can be migrated and tested grad
On Mon, Feb 13, 2023 at 11:28 PM Chris Morgan wrote:
> From: Chris Morgan
>
> Use the new devicetree property of gpio-ranges to determine the GPIO
> bank ID. Preserve the "old" way of doing things too, so that boards
> can be migrated and tested gradually (I only have a 3566 and 3326 to
> test).
Hi Kever, Linus Walleij, Heiko,
My Linux proposal has a little different logic (see below) and was "Acked-by",
but the merge status is unknown.
https://lore.kernel.org/linux-rockchip/890be9a0-8e82-a8f4-bc15-d5d159734...@gmail.com/
Could Linus/Heiko indicate if U-boot already can use this or are
On 2023/2/14 06:27, Chris Morgan wrote:
From: Chris Morgan
Use the new devicetree property of gpio-ranges to determine the GPIO
bank ID. Preserve the "old" way of doing things too, so that boards
can be migrated and tested gradually (I only have a 3566 and 3326 to
test).
Signed-off-by: Chris
From: Chris Morgan
Use the new devicetree property of gpio-ranges to determine the GPIO
bank ID. Preserve the "old" way of doing things too, so that boards
can be migrated and tested gradually (I only have a 3566 and 3326 to
test).
Signed-off-by: Chris Morgan
---
drivers/gpio/rk_gpio.c | 20 ++
6 matches
Mail list logo
