From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux Input <linux-input@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/5] Make gpio_keys accept board descriptors
Date: Wed, 26 Aug 2020 09:12:22 -0700 [thread overview]
Message-ID: <20200826161222.GA1665100@dtor-ws> (raw)
In-Reply-To: <20200826143543.GC813478@kuha.fi.intel.com>
On Wed, Aug 26, 2020 at 05:35:43PM +0300, Heikki Krogerus wrote:
> On Wed, Aug 26, 2020 at 03:20:14PM +0200, Linus Walleij wrote:
> > Hi Dmitry,
> >
> > On Sun, Nov 26, 2017 at 12:33 AM Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
> > > On Fri, Nov 24, 2017 at 10:30:40AM +0100, Linus Walleij wrote:
> >
> > > > The goal I'm working toward is to rid the kernel of the global
> > > > GPIO numberspace.
> > > >
> > > > This means GPIO lines should be references by the local offset
> > > > on the GPIO chip.
> > > >
> > > > This patch set starts to move gpio_keys toward using GPIO
> > > > look-up tables instead of global GPIO numbers to find their
> > > > GPIOs.
> > > >
> > > > As an example I did (I think) the necessary patches to
> > > > convert DaVinci and i.MX to use this. There are several users
> > > > also x86 platform devices.
> > (...)
> > > I think this is a worthy goal, but I wonder if we could get static GPIO
> > > descriptors work with fwnode_get_named_gpiod() so we could retire the
> > > platform data parsing altogether. We'd need to extend static device
> > > properties to have notion of children though.
> >
> > Do we have this now? I've looked at Heikki's et al work
> > on software nodes but I cannot see whether we are there now.
> >
> > We have fwnode_create_software_node() and friends, but
> > I haven't seen if this can be used with input and GPIO descriptors
> > are still a bit on the side. I can create a lot of properties but
> > not really add a descriptor table as a software node as far as
> > I can tell. I'm also a bit lost on whether it will be possible
> > to get there sadly :/
>
> I'm sorry but I'm not completely sure what is this about? Are software
> nodes still missing something that would prevent us from for example
> using them to describe the GPIO information exactly the same way it is
> described in DT? I don't know if that is what we want, but I'm just
> trying to understand what is still missing? Dmitry?
No, my changes to improve the fwnode handling of references have landed,
a while ago, so now I need to refresh the series of patches to gpiolib I
was working on around Plumbers time last year. Linus seemed mostly OK
with them, so it just a matter of finding time and picking this up
again.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2020-08-26 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 9:30 [PATCH 0/5] Make gpio_keys accept board descriptors Linus Walleij
2017-11-24 9:30 ` [PATCH 1/5] Input: gpio-keys: Support getting descriptors from board Linus Walleij
2017-11-24 9:30 ` [PATCH 2/5] gpio: pca953x: Name the gpiochip after the I2C address Linus Walleij
2017-11-24 14:26 ` Andrew Lunn
2017-11-30 14:45 ` Linus Walleij
2017-11-24 9:30 ` [PATCH 3/5] ARM: davinci: Switch DA850EVM to use GPIO descriptors Linus Walleij
2017-11-24 9:30 ` [PATCH 4/5] ARM: imx: Give all GPIO chips a unique name Linus Walleij
2017-11-24 9:30 ` [PATCH 5/5] ARM: imx: Use GPIO descriptors for gpio_keys Linus Walleij
2017-11-25 23:33 ` [PATCH 0/5] Make gpio_keys accept board descriptors Dmitry Torokhov
2017-11-30 15:44 ` Linus Walleij
2020-08-26 13:20 ` Linus Walleij
2020-08-26 14:35 ` Heikki Krogerus
2020-08-26 16:12 ` Dmitry Torokhov [this message]
2020-08-26 23:31 ` Linus Walleij
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=20200826161222.GA1665100@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.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).