From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: [PATCH] Input: elan_i2c - Wait for initialization after enabling regulator supply
Date: Tue, 1 Oct 2024 06:11:50 -0700 [thread overview]
Message-ID: <Zvv1FuXBZpjDefb8@google.com> (raw)
In-Reply-To: <7db1299f-f925-4689-806f-f1ea4191fd4c@sirena.org.uk>
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
next prev parent reply other threads:[~2024-10-01 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 9:38 [PATCH] Input: elan_i2c - Wait for initialization after enabling regulator supply Chen-Yu Tsai
2024-10-01 9:57 ` Dmitry Torokhov
2024-10-01 11:07 ` Mark Brown
2024-10-01 12:58 ` Dmitry Torokhov
2024-10-01 13:06 ` Mark Brown
2024-10-01 13:11 ` Dmitry Torokhov [this message]
2024-10-01 13:13 ` Mark Brown
2024-10-04 3:57 ` Chen-Yu Tsai
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=Zvv1FuXBZpjDefb8@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=wenst@chromium.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).