From: "Nuno Sá" <noname.nuno@gmail.com>
To: Nuno Sa <nuno.sa@analog.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
Dmitry Torokhov <dtor@mail.ru>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <brgl@bgdev.pl>, Lee Jones <lee@kernel.org>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 00/13] Input: adp5589: refactor and platform_data removal
Date: Wed, 16 Oct 2024 15:36:03 +0200 [thread overview]
Message-ID: <d1395bd61ce58b3734121bca4e09605a3e997af3.camel@gmail.com> (raw)
In-Reply-To: <20241001-b4-dev-adp5589-fw-conversion-v1-0-fca0149dfc47@analog.com>
On Tue, 2024-10-01 at 15:41 +0200, Nuno Sa wrote:
> This series aims to remove platform data dependency from the adp5589
> driver (as no platform is really using it) and instead add support for
> FW properties. Note that rows and columns for the keypad are being given
> as masks and that was briefly discussed with Dmitry. For context
> on why this is being done as mask [1].
>
> The first couple of patches are fixes that we may want to backport...
>
> [1]:
> https://lore.kernel.org/linux-input/9db96c99c805e615ba40ca7fd3632174d1e8d11f.camel@gmail.com/
>
> ---
> Nuno Sa (13):
> Input: adp5589-keys: fix NULL pointer dereference
> Input: adp5589-keys: fix adp5589_gpio_get_value()
> Input: adp5589-keys: add chip_info structure
> Input: adp5589-keys: support gpi key events as 'gpio keys'
> dt-bindings: input: Document adp5589 and similar devices
> Input: adp5589-keys: add support for fw properties
> Input: adp5589-keys: add guard() notation
> Input: adp5589-keys: bail out on returned error
> Input: adp5589-keys: refactor adp5589_read()
> Input: adp5589-keys: fix coding style
> Input: adp5589-keys: unify adp_constants in info struct
> Input: adp5589-keys: make use of dev_err_probe()
> Input: adp5589-keys: add regulator support
>
> .../devicetree/bindings/input/adi,adp5589.yaml | 310 +++++
> .../devicetree/bindings/trivial-devices.yaml | 6 -
> MAINTAINERS | 8 +
> drivers/input/keyboard/Kconfig | 3 +
> drivers/input/keyboard/adp5589-keys.c | 1397 +++++++++++++-------
> include/linux/input/adp5589.h | 180 ---
> 6 files changed, 1254 insertions(+), 650 deletions(-)
> ---
> base-commit: c7bf046925dc5885d9c4d8fbcbb7e4e73665bfcf
> change-id: 20240930-b4-dev-adp5589-fw-conversion-955b2f42da70
> --
>
> Thanks!
> - Nuno Sá
>
Hi Dmitry,
Something really caught my attention now while checking 6.12 merge window. It seems
we have a new MFD device for adp5585 [1] which adds duplicated functionality (that
was already present in adp5589-keys.c). So, having this as MFD might makes sense
(even though it makes it harder to validate the keys and to make use of gpio-keys)
but we are now duplicating GPIO support. Bottom line, not sure what we should do next
and should I proceed for v2?
Also ccing Lee and Bartosz...
[1]: https://lore.kernel.org/lkml/20240816152738.GB5853@google.com/
- Nuno Sá
next prev parent reply other threads:[~2024-10-16 13:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 13:41 [PATCH 00/13] Input: adp5589: refactor and platform_data removal Nuno Sa
2024-10-01 13:41 ` [PATCH 01/13] Input: adp5589-keys: fix NULL pointer dereference Nuno Sa
2024-10-01 14:49 ` Dmitry Torokhov
2024-10-01 13:41 ` [PATCH 02/13] Input: adp5589-keys: fix adp5589_gpio_get_value() Nuno Sa
2024-10-01 14:50 ` Dmitry Torokhov
2024-10-01 13:41 ` [PATCH 03/13] Input: adp5589-keys: add chip_info structure Nuno Sa
2024-10-01 14:55 ` Dmitry Torokhov
2024-10-02 9:13 ` Nuno Sá
2024-10-02 9:47 ` Dmitry Torokhov
2024-10-02 10:57 ` Nuno Sá
2024-10-01 13:41 ` [PATCH 04/13] Input: adp5589-keys: support gpi key events as 'gpio keys' Nuno Sa
2024-10-01 13:41 ` [PATCH 05/13] dt-bindings: input: Document adp5589 and similar devices Nuno Sa
2024-10-02 20:58 ` Rob Herring
2024-10-08 7:01 ` Nuno Sá
2024-10-01 13:41 ` [PATCH 06/13] Input: adp5589-keys: add support for fw properties Nuno Sa
2024-10-01 14:59 ` Dmitry Torokhov
2024-10-02 9:01 ` Nuno Sá
2024-10-01 13:41 ` [PATCH 07/13] Input: adp5589-keys: add guard() notation Nuno Sa
2024-10-01 13:41 ` [PATCH 08/13] Input: adp5589-keys: bail out on returned error Nuno Sa
2024-10-01 13:41 ` [PATCH 09/13] Input: adp5589-keys: refactor adp5589_read() Nuno Sa
2024-10-01 13:41 ` [PATCH 10/13] Input: adp5589-keys: fix coding style Nuno Sa
2024-10-01 13:41 ` [PATCH 11/13] Input: adp5589-keys: unify adp_constants in info struct Nuno Sa
2024-10-01 13:41 ` [PATCH 12/13] Input: adp5589-keys: make use of dev_err_probe() Nuno Sa
2024-10-01 13:41 ` [PATCH 13/13] Input: adp5589-keys: add regulator support Nuno Sa
2024-10-16 13:36 ` Nuno Sá [this message]
2024-10-18 21:30 ` [PATCH 00/13] Input: adp5589: refactor and platform_data removal Dmitry Torokhov
2024-10-19 17:18 ` Laurent Pinchart
2024-10-21 11:26 ` Nuno Sá
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=d1395bd61ce58b3734121bca4e09605a3e997af3.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=vapier@gentoo.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).