[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbYF5WCy7yc3t6VSU8CK-MKpxQnVWmRE-YCSKJ1hJDkug@mail.gmail.com>
Date: Tue, 15 Oct 2024 23:43:14 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Prabhakar <prabhakar.csengg@...il.com>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, Geert Uytterhoeven <geert+renesas@...der.be>, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
Biju Das <biju.das.jz@...renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [RFC PATCH] pinctrl: pinmux: Introduce API to check if a pin is requested
Hi Prabhakar,
thanks for your patch!
On Tue, Oct 15, 2024 at 6:21 PM Prabhakar <prabhakar.csengg@...il.com> wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
>
> Introduce `pin_requestesd` API to check if a pin is currently requested.
What kind of function name is this?
Do you mean
pin_requested()?
> This API allows pinctrl drivers to verify whether a pin is requested or
> not by checking if the pin is owned by either `gpio_owner` or `mux_owner`.
There is nothing wrong with the patch as such, but it needs to be
illustrated by submitting it together with the first intended user
and show how it is used, we don't add upfront APIs.
Yours,
Linus Walleij
Powered by blists - more mailing lists