[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOiHx=kvsCx0cd5C8eza-V7H+ML2ff5zB=vjM6zDmb0A7d16+A@mail.gmail.com>
Date: Mon, 30 Dec 2024 17:42:12 +0100
From: Jonas Gorski <jonas.gorski@...il.com>
To: Álvaro Fernández Rojas <noltari@...il.com>
Cc: linus.walleij@...aro.org, kylehendrydev@...il.com,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] pinctrl: bcm63268: add gpio function
Hi,
On Tue, Dec 24, 2024 at 11:41 AM Álvaro Fernández Rojas
<noltari@...il.com> wrote:
>
> From: Kyle Hendry <kylehendrydev@...il.com>
>
> There is no guarantee that the bootloader will leave the pin configuration
> in a known default state, so pinctrl needs to be explicitly set in some
> cases. This patch adds a gpio function for drivers that need it, i.e.
> gpio-leds.
>
> Signed-off-by: Kyle Hendry <kylehendrydev@...il.com>
> Signed-off-by: Álvaro Fernández Rojas <noltari@...il.com>
bcm63268-pinctrl implements pinmux_ops::gpio_request_enable(), which
should automatically set any requested GPIO pin to the GPIO function,
so explicitly requesting the gpio function for a pin should not be
needed. Is this not enough?
Best Regards,
Jonas
Powered by blists - more mailing lists