[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zvv1FuXBZpjDefb8@google.com>
Date: Tue, 1 Oct 2024 06:11:50 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Chen-Yu Tsai <wenst@...omium.org>, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH] Input: elan_i2c - Wait for initialization after enabling
regulator supply
On Tue, Oct 01, 2024 at 02:06:19PM +0100, Mark Brown wrote:
> On Tue, Oct 01, 2024 at 05:58:58AM -0700, Dmitry Torokhov wrote:
> > On Tue, Oct 01, 2024 at 12:07:16PM +0100, Mark Brown wrote:
>
> > > availalbe when a regulator is turned on? There's also no difference
> > > between DT and ACPI systems here, both could have the regulator fixed on
> > > and I'd certainly not want to rely on an ACPI system implementing a
> > > device specific delay after power on given the sort of stuff they like
> > > to put into machine specific drivers.
>
> > Well with Elan in native mode ACPI FW does do proper power sequencing,
> > that is why this commit mentions failures observed on Mediatek devices.
>
> Yeah, but that's got to get washed through the individual system
> firmwares to get deployed and my confidence in vendors is not high.
I think native Elan is only used in Chromebooks where firmware is
decent, the rest are I2C-HID.
Thanks.
--
Dmitry
Powered by blists - more mailing lists