From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Drew Fustini <drew@beagleboard.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Pantelis Antoniou <pantelis.antoniou@linaro.org>,
Pantelis Antoniou <pantelis.antoniou@gmail.com>,
Jason Kridner <jkridner@beagleboard.org>,
Robert Nelson <robertcnelson@beagleboard.org>
Subject: Re: [RFC PATCH v2] pinctrl: add helper to expose pinctrl state in debugfs
Date: Mon, 11 Jan 2021 12:03:18 +0200 [thread overview]
Message-ID: <X/wiZjioLqcTYVfj@atomide.com> (raw)
In-Reply-To: <CACRpkdaOfU=OLp5D-EXK2oU9bScLZ-QjLdCSrewiSBa0SRRNwg@mail.gmail.com>
Hi,
* Linus Walleij <linus.walleij@linaro.org> [210109 21:14]:
> On Sat, Jan 9, 2021 at 3:55 AM Drew Fustini <drew@beagleboard.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.
Makes sense to me too.
We may want to make it into a proper sysfs interface eventually to not
require debugfs be enabled in .config. But that's another set of patches,
certainly makes sense to first enable it for debugfs.
Regards,
Tony
next prev parent reply other threads:[~2021-01-11 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 4:51 [RFC PATCH v2] pinctrl: add helper to expose pinctrl state in debugfs Drew Fustini
2020-12-18 16:01 ` Andy Shevchenko
2020-12-24 20:36 ` Drew Fustini
2021-01-03 20:23 ` Drew Fustini
2021-01-09 1:22 ` Linus Walleij
2021-01-09 2:55 ` Drew Fustini
2021-01-09 21:14 ` Linus Walleij
2021-01-11 10:03 ` Tony Lindgren [this message]
2021-01-21 3:19 ` Drew Fustini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X/wiZjioLqcTYVfj@atomide.com \
--to=tony@atomide.com \
--cc=andy.shevchenko@gmail.com \
--cc=drew@beagleboard.org \
--cc=jkridner@beagleboard.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@gmail.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=pantelis.antoniou@linaro.org \
--cc=robertcnelson@beagleboard.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).