linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Walle" <mwalle@kernel.org>
To: "Jon Cormier" <jcormier@criticallink.com>
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>
Subject: Re: [PATCH 0/3] Powerbutton driver and powerdown request for TPS65224 PMIC
Date: Wed, 20 Aug 2025 09:06:03 +0200	[thread overview]
Message-ID: <DC72C4R6NXKI.MF84P0PHWROB@kernel.org> (raw)
In-Reply-To: <CADL8D3Y0hRgJ6P59YvUKYzYBADjCXr7kevHNUDoqZXT41Ka2Yw@mail.gmail.com>

Hi,

On Tue Aug 19, 2025 at 6:22 PM CEST, Jon Cormier wrote:
> On Tue, Aug 19, 2025 at 7:30 AM Michael Walle <mwalle@kernel.org> wrote:
>>
>> On Tue Aug 19, 2025 at 1:27 PM CEST, Michael Walle wrote:
>> > Hi Job,
>> >
>> > > The following patches were created to get the tps65224 PMIC
>> > > powerbutton driver and power off request working on the
>> > > MitySOM-AM62PX. The patches are as follows:
>> >
>> > Are there any news on this series? Do you plan to post a new
>> > version soon, or do you want me to take over? I'd like to get
>> > support for this into the kernel :)
>>
>> FWIW, jsava@criticallink.com is bouncing.
> Yeah sorry, Job has gone back to school, he was on an internship.
>
> I'm not entirely sure how best to move forward with this change.
> There have been several suggestions thrown out and I'm a little lost
> on what's best/easiest.
>
> If you want to take over and add us as co authors that would be
> greatly appreciated.  I can get his personal email if that makes
> sense.  I'm not sure how the kernel normally deals with short term
> emails (interns).

I've asked around and Krzysztof said I should replace the mail with
his new address - or if I can't find it, use the old one. So yes,
you could ask him for his new (or private) address and if he's fine
with having that mentioned in the commit message.

> Note we are currently using the driver as is, on an Android prototype
> and for some reason Android isn't able to detect the power button
> hold, and open the power menu. Single push works fine to turn off the
> screen.  I haven't looked into it yet, to see if this is an Android
> issue or if we are using the POWER key events wrong. Just thought I'd
> mention it.

Thanks, FWIW I'm using it with (normal) linux and it's working fine.
I'll double check if the press and release event is actually working.

-michael

      reply	other threads:[~2025-08-20  7:06 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
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 [this message]

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=DC72C4R6NXKI.MF84P0PHWROB@kernel.org \
    --to=mwalle@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jcormier@criticallink.com \
    --cc=jpanis@baylibre.com \
    --cc=krzk+dt@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).