From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Karel Balej <karelb@gimli.ms.mff.cuni.cz>
Cc: "Karel Balej" <balejk@matfyz.cz>, "Lee Jones" <lee@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org,
"Duje Mihanović" <duje.mihanovic@skole.hr>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [RFC PATCH v3 4/5] input: add onkey driver for Marvell 88PM886 PMIC
Date: Sun, 3 Mar 2024 12:39:46 -0800 [thread overview]
Message-ID: <ZeTgEmjJc_VhYpLm@google.com> (raw)
In-Reply-To: <20240303101506.4187-5-karelb@gimli.ms.mff.cuni.cz>
Hi Karel,
On Sun, Mar 03, 2024 at 11:04:25AM +0100, Karel Balej wrote:
> From: Karel Balej <balejk@matfyz.cz>
>
> Marvell 88PM886 PMIC provides onkey among other things. Add client
> driver to handle it. The driver currently only provides a basic support
> omitting additional functions found in the vendor version, such as long
> onkey and GPIO integration.
>
> Signed-off-by: Karel Balej <balejk@matfyz.cz>
> ---
>
> Notes:
> RFC v3:
> - Drop wakeup-source.
> RFC v2:
> - Address Dmitry's feedback:
> - Sort includes alphabetically.
> - Drop onkey->irq.
> - ret -> err in irq_handler and no initialization.
> - Break long lines and other formatting.
> - Do not clobber platform_get_irq error.
> - Do not set device parent manually.
> - Use input_set_capability.
> - Use the wakeup-source DT property.
> - Drop of_match_table.
I only said that you should not be using of_match_ptr(), but you still
need to have of_match_table set and have MODULE_DEVICE_TABLE() for the
proper module loading support.
With that fixed:
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2024-03-03 20:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 10:04 [RFC PATCH v3 0/5] initial support for Marvell 88PM886 PMIC Karel Balej
2024-03-03 10:04 ` [RFC PATCH v3 1/5] dt-bindings: mfd: add entry " Karel Balej
2024-03-04 8:03 ` Krzysztof Kozlowski
2024-03-03 10:04 ` [RFC PATCH v3 2/5] mfd: add driver " Karel Balej
2024-03-05 11:44 ` Lee Jones
2024-03-05 18:53 ` Karel Balej
2024-03-07 8:16 ` Lee Jones
2024-03-03 10:04 ` [RFC PATCH v3 3/5] regulator: add regulators " Karel Balej
2024-03-03 10:04 ` [RFC PATCH v3 4/5] input: add onkey " Karel Balej
2024-03-03 20:39 ` Dmitry Torokhov [this message]
2024-03-04 20:28 ` Karel Balej
2024-03-05 1:10 ` Dmitry Torokhov
2024-03-10 11:35 ` Karel Balej
2024-03-10 20:35 ` Krzysztof Kozlowski
2024-03-10 21:48 ` Dmitry Torokhov
2024-03-11 10:26 ` Karel Balej
2024-03-11 10:41 ` Krzysztof Kozlowski
2024-03-11 12:12 ` Karel Balej
2024-03-11 16:18 ` Dmitry Torokhov
2024-03-03 10:04 ` [RFC PATCH v3 5/5] MAINTAINERS: add myself " Karel Balej
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=ZeTgEmjJc_VhYpLm@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=balejk@matfyz.cz \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=duje.mihanovic@skole.hr \
--cc=karelb@gimli.ms.mff.cuni.cz \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.