From:   Mattijs Korpershoek <mkorpershoek@baylibre.com>
To:     =?utf-8?B?QXLEsW7DpyDDnE5BTA==?= <arinc.unal@arinc9.com>,
        Dmitry Torokhov <dmitry.torokhov@gmail.com>,
        Matthias Brugger <matthias.bgg@gmail.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@collabora.com>,
        Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc:     linux-input@vger.kernel.org,
        Linux ARM <linux-arm-kernel@lists.infradead.org>,
        "moderated list:ARM/Mediatek SoC support" 
        <linux-mediatek@lists.infradead.org>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        Frank Wunderlich <frank-w@public-files.de>,
        erkin.bozoglu@xeront.com
Subject: Re: mtk-pmic-keys: Ignore power button if pressed before driver loads
In-Reply-To: <883798d8-f7d9-eadc-1343-7d241741ff67@arinc9.com>
References: <883798d8-f7d9-eadc-1343-7d241741ff67@arinc9.com>
Date:   Mon, 30 Jan 2023 18:21:04 +0100
Message-ID: <87r0vcc51b.fsf@baylibre.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Ar=C4=B1n=C3=A7,

On lun., janv. 30, 2023 at 16:36, Ar=C4=B1n=C3=A7 =C3=9CNAL <arinc.unal@ari=
nc9.com> wrote:

> Hi all,
>
> The power button on my Bananapi BPI-R2 (MT7623NI SoC, mt6323-keys) is=20
> shorted, so the device automatically boots when there's power. This=20
> causes the device to reboot when KEYBOARD_MTK_PMIC is loaded because the=
=20
> driver sees the power button being pressed.

What evidence do you have that there is actually a "press" event being
received by userspace? Did you tested this with evtest or something
similar?

If a "power button press" is generated, than I imagine that a userspace
process must receive it and halt the system, right?

The PMIC also has a feature to shutdown in case detect a long key-press,
which is controlled by the mediatek,long-press-mode device-tree
property.
So is it the pmic that shutdown your board (probably no evidence in
logs, just a "power cut" behaviour) or is it userspace?

>
> I was wondering if it's possible to change the driver in a way that=20
> doesn't break in this situation. Maybe don't do anything if the first=20
> state of the the power button the driver sees is being pressed, and if=20
> the state doesn't change.

If the driver is an issue, can't we blacklist it from being probed
instead? or do you want to use the home key feature that that same
driver provides?

Hope that helps,

Mattijs

>
> To address an edge case, if the power button was being pressed before=20
> the driver loads, look for if it's ever released. Only after then start=20
> working as usual.
>
> Looking forward to hearing your thoughts.
> Ar=C4=B1n=C3=A7