From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "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 19:26:07 +0200 [thread overview]
Message-ID: <20190729172607.GB755@penguin> (raw)
In-Reply-To: <1564415994-22871-1-git-send-email-info@metux.net>
Hi Enrico,
On Mon, Jul 29, 2019 at 05:59:53PM +0200, Enrico Weigelt, metux IT consult wrote:
> From: Enrico Weigelt <info@metux.net>
>
> Support the recently introduced gpio lookup tables for
> attaching to gpio lines. So, harcoded gpio numbers aren't
> needed anymore.
>
> changes v3:
> * fix printf string in gpio_keys_polled_get_gpiod()
> * fix unused variable 'error' in gpio_keys_polled_get_gpiod()
> * fix uninitialized variable in gpio_keys_polled_get_gpiod_fwnode()
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.
I just recently re-posted patches for this, let's see if we can get them
landed in the kernel.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-07-29 17:26 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 ` Dmitry Torokhov [this message]
2019-07-29 18:14 ` [PATCH 1/2] input: keyboard: gpio_keys_polled: use gpio lookup table Enrico Weigelt, metux IT consult
2019-07-29 18:43 ` Dmitry Torokhov
2019-07-31 17:26 ` Enrico Weigelt, metux IT consult
-- strict thread matches above, loose matches on Subject: below --
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=20190729172607.GB755@penguin \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.