From: Drew Fustini <drew@beagleboard.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Rob Herring <robh+dt@kernel.org>,
bcousson@baylibre.com, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Kridner <jkridner@beagleboard.org>,
Robert Nelson <robertcnelson@gmail.com>,
"H . Nikolaus Schaller" <hns@goldelico.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2] ARM: dts: am335x-pocketbeagle: set default mux for gpio pins
Date: Tue, 30 Jun 2020 23:42:31 +0200 [thread overview]
Message-ID: <20200630214231.GA116238@x1> (raw)
In-Reply-To: <20200630213423.GG37466@atomide.com>
On Tue, Jun 30, 2020 at 02:34:23PM -0700, Tony Lindgren wrote:
> * Drew Fustini <drew@beagleboard.org> [200630 21:32]:
> > On Tue, Jun 30, 2020 at 11:20:37AM -0700, Tony Lindgren wrote:
> ...
> > > > > Needing to change the dts does not sound good to me.. But maybe you mean
> > > > > this is needed until the gpio-omap and pinctrl-single patches are merged?
> > > >
> > > > I agree that I would like for userspace to be able to do run-time
> > > > changes. However, I think something would need to be added to the
> > > > pinconf support in pinctrl-single for that to be possible. There are
> > > > bias properties but non for receiver enable.
> > > >
> > > > Does it seem sensible to add that?
> > >
> > > Well let's see with Linus W says. To me it seems this might be a good
> > > reason to allow a sysfs interface to change the pinctrl if we don't
> > > have it yet? With the proper gpio line naming it should be quite simple
> > > to use too :)
> >
> > I think if pinctrl-single allowed mux to be set through debugfs that
> > could be one solution to the use case of users prototyping with a
> > beaglebone. Maybe that could be acceptable?
>
> I think this should not depend on debugfs though, it should be a
> generic interface.
Ok, thanks. I'm trying to imagine a solution as there no existing
pinctrl uAPI. gpiod uAPI has gained some pinctrl functionality with
the work that Kent Gibson has been doing beyond just bias flags.
Do you think trying to plumb this through gpio-omap is a reasonable
approach?
thanks,
drew
next prev parent reply other threads:[~2020-06-30 21:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 15:24 [PATCH v2] ARM: dts: am335x-pocketbeagle: set default mux for gpio pins Drew Fustini
2020-06-29 17:03 ` Tony Lindgren
2020-06-30 2:01 ` Drew Fustini
2020-06-30 18:20 ` Tony Lindgren
2020-06-30 21:31 ` Drew Fustini
2020-06-30 21:34 ` Tony Lindgren
2020-06-30 21:42 ` Drew Fustini [this message]
2020-07-01 14:48 ` Tony Lindgren
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=20200630214231.GA116238@x1 \
--to=drew@beagleboard.org \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=jkridner@beagleboard.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/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).