[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200630213423.GG37466@atomide.com>
Date: Tue, 30 Jun 2020 14:34:23 -0700
From: Tony Lindgren <tony@...mide.com>
To: Drew Fustini <drew@...gleboard.org>
Cc: Rob Herring <robh+dt@...nel.org>, bcousson@...libre.com,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jason Kridner <jkridner@...gleboard.org>,
Robert Nelson <robertcnelson@...il.com>,
"H . Nikolaus Schaller" <hns@...delico.com>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH v2] ARM: dts: am335x-pocketbeagle: set default mux for
gpio pins
* Drew Fustini <drew@...gleboard.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.
Regards,
Tony
Powered by blists - more mailing lists