[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaOfU=OLp5D-EXK2oU9bScLZ-QjLdCSrewiSBa0SRRNwg@mail.gmail.com>
Date: Sat, 9 Jan 2021 22:14:37 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Drew Fustini <drew@...gleboard.org>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@...sulko.com>,
Pantelis Antoniou <pantelis.antoniou@...aro.org>,
Pantelis Antoniou <pantelis.antoniou@...il.com>,
Jason Kridner <jkridner@...gleboard.org>,
Robert Nelson <robertcnelson@...gleboard.org>,
Tony Lindgren <tony@...mide.com>
Subject: Re: [RFC PATCH v2] pinctrl: add helper to expose pinctrl state in debugfs
On Sat, Jan 9, 2021 at 3:55 AM Drew Fustini <drew@...gleboard.org> wrote:
> I discussed my use case and this patch on #armlinux earlier this week
> and Alexandre Belloni suggested looking at the pinmux-pins debugfs file.
This sounds reasonable.
> This made me think that a possible solution could be to define a store
> function for pinmux-pins to handle something like "<pin#> <function#>".
> I believe the ability to activate a pin function (or pin group) from
> userspace would satisfy our beagleboard.org use-case.
>
> Does that seem like a reasonable approach?
This sounds like a good approach.
Yours,
Linus Walleij
Powered by blists - more mailing lists