From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Enrico Weigelt, metux IT consult" <info@metux.net>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 1/2] input: keyboard: gpio_keys_polled: use gpio lookup table
Date: Mon, 29 Jul 2019 20:14:52 +0200 [thread overview]
Message-ID: <b2912c1d-a6d8-ad2a-3e37-19e4d3d1bd3b@metux.net> (raw)
In-Reply-To: <20190729172607.GB755@penguin>
On 29.07.19 19:26, Dmitry Torokhov wrote:
Hi,
> As I think I mentioned a while back I would prefer to get gpiolob > support swnode-backed properties so that the driver would not need
to> know about differences between ACPI, DT and static board files.
Indeed would be nice. But I think we should get rid of raw gpio IDs in
favour of gpiod lookup tables first.
> I just recently re-posted patches for this, let's see if we can get them > landed in the kernel.
Can you give me a pointer ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-07-29 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 15:59 [PATCH 1/2] input: keyboard: gpio_keys_polled: use gpio lookup table Enrico Weigelt, metux IT consult
2019-07-29 15:59 ` [PATCH 2/2] input: keyboard: gpio-keys-polled: skip oftree code when CONFIG_OF disabled Enrico Weigelt, metux IT consult
2019-07-29 17:26 ` [PATCH 1/2] input: keyboard: gpio_keys_polled: use gpio lookup table Dmitry Torokhov
2019-07-29 18:14 ` Enrico Weigelt, metux IT consult [this message]
2019-07-29 18:43 ` Dmitry Torokhov
2019-07-31 17:26 ` Enrico Weigelt, metux IT consult
2019-11-21 13:32 Enrico Weigelt, metux IT consult
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=b2912c1d-a6d8-ad2a-3e37-19e4d3d1bd3b@metux.net \
--to=lkml@metux.net \
--cc=dmitry.torokhov@gmail.com \
--cc=info@metux.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).