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 3/4] input: keyboard: gpio_keys_polled: use gpio lookup table
Date: Wed, 24 Apr 2019 12:59:35 +0200 [thread overview]
Message-ID: <9819838f-9e35-c504-61da-f8c3f9b7ac8e@metux.net> (raw)
In-Reply-To: <20190419074811.7rkq3p6t7s56g4fo@penguin>
On 19.04.19 09:48, Dmitry Torokhov wrote:
> I would prefer if gpiod API could parse static board data/gpio lookup
> tables for child nodes, instead of adding this to gpio-keys. Now that
> Heikki Krogerus work on software nodes has landed I need to resurrect
> my patch to gpiolib.
Of course, a more generic approach would be better.
I did it that way I wasn't that aware that a more generic approach is
in the pipeline, and I needed something usable now.
The patch is already used in the field and seems to work quite well,
but if I'm alway open for better solutions.
I figure that the generic solution will still take some time, so can we
take this one for the next merge window and rework it in the next one ?
--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-04-24 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 19:57 gpio-keys-polled improvements Enrico Weigelt, metux IT consult
2019-04-16 19:57 ` [PATCH 1/4] mod_devicetable: helper macro for declaring oftree module device table Enrico Weigelt, metux IT consult
2019-04-19 7:40 ` Dmitry Torokhov
2019-04-24 10:48 ` Enrico Weigelt, metux IT consult
2019-04-29 19:48 ` Frank Rowand
2019-04-16 19:57 ` [PATCH 2/4] input: keyboard: gpio-keys-polled: use input name from pdata if available Enrico Weigelt, metux IT consult
2019-04-16 19:57 ` [PATCH 3/4] input: keyboard: gpio_keys_polled: use gpio lookup table Enrico Weigelt, metux IT consult
2019-04-19 7:48 ` Dmitry Torokhov
2019-04-24 10:59 ` Enrico Weigelt, metux IT consult [this message]
2019-04-16 19:57 ` [PATCH 4/4] input: keyboard: gpio-keys-polled: skip oftree code when CONFIG_OF disabled Enrico Weigelt, metux IT consult
2019-04-29 19:44 ` Frank Rowand
2019-04-29 21:40 ` 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=9819838f-9e35-c504-61da-f8c3f9b7ac8e@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 read-only IMAP folder(s) and NNTP newsgroup(s).