From: "Michael Walle" <michael@walle.cc>
To: "Job Sava" <jsava@criticallink.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>
Cc: "Lee Jones" <lee@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Julien Panis" <jpanis@baylibre.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-input@vger.kernel.org>, <jcormier@criticallink.com>
Subject: Re: [PATCH 1/3] dt-bindings: mfd: Add power-button option for TI TPS6594 PMIC
Date: Thu, 17 Jul 2025 15:58:00 +0200 [thread overview]
Message-ID: <DBEDT0OKPYAC.EX6HDQCKUWIS@walle.cc> (raw)
In-Reply-To: <CAKMwjwSZEhXav2U-bd+JNyVDK3JdJoN1kJjnxpfKXBKsW2XxdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Hi,
> > Someone knowing the device should come with arguments whether
> > other states for this are useful at all. Or not useful and then argument
> > that in commit msg for example.
> The other states are not useful for the kernel. Only the push button
> has a need for an interrupt handler. The other states the PMIC handles
> on its own.
>
> What exactly do you want me to change?
Because the driver isn't setting the configuration anyway, wouldn't
it be possible to read the config bits (Register 0x3c, bits 7-6) to
figure out whether the pin is configured as power-button instead of
having this property?
I mean, the correct config is likely stored in the NVM anyway, and
reconfiguring it to another value seems unlikely.
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-07-17 13:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 17:43 [PATCH 0/3] Powerbutton driver and powerdown request for TPS65224 PMIC Job Sava
2025-05-20 17:43 ` [PATCH 1/3] dt-bindings: mfd: Add power-button option for TI TPS6594 PMIC Job Sava
2025-05-21 10:01 ` Krzysztof Kozlowski
2025-05-23 13:46 ` Job Sava
2025-05-29 9:25 ` Krzysztof Kozlowski
2025-06-02 13:07 ` Job Sava
2025-06-03 6:51 ` Krzysztof Kozlowski
2025-06-17 16:07 ` Job Sava
2025-07-17 13:58 ` Michael Walle [this message]
2025-07-18 19:07 ` Jon Cormier
2025-07-21 6:42 ` Michael Walle
2025-07-30 13:52 ` Markus Schneider-Pargmann
2025-05-20 17:43 ` [PATCH 2/3] mfd: tps6594-pwrbutton: Add powerbutton functionality Job Sava
2025-05-20 18:15 ` Dmitry Torokhov
2025-06-13 14:09 ` Lee Jones
2025-06-17 15:54 ` Job Sava
2025-05-20 17:43 ` [PATCH 3/3] mfd: tps6594: Adds support for powering off the PMIC Job Sava
2025-06-13 14:11 ` Lee Jones
2025-06-17 16:00 ` Job Sava
2025-08-19 11:27 ` [PATCH 0/3] Powerbutton driver and powerdown request for TPS65224 PMIC Michael Walle
2025-08-19 11:30 ` Michael Walle
2025-08-19 16:22 ` Jon Cormier
2025-08-20 7:06 ` Michael Walle
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=DBEDT0OKPYAC.EX6HDQCKUWIS@walle.cc \
--to=michael@walle.cc \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jcormier@criticallink.com \
--cc=jpanis@baylibre.com \
--cc=jsava@criticallink.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).