From: Hans de Goede <hansg@kernel.org>
To: "James Alexander" <opensource@inspiredexperts.com>,
"Daniel Scally" <dan.scally@ideasonboard.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: int3472: add HP Spectre handshake delay
Date: Tue, 18 Aug 2026 13:00:36 +0200 [thread overview]
Message-ID: <a135b02a-a4e6-4abe-940c-a93bf0ea807a@kernel.org> (raw)
In-Reply-To: <a062f34e-4e26-457e-a116-5481d34bf8ff@kernel.org>
Hi Alexander,
On 18-Aug-26 12:43, Hans de Goede wrote:
> Hi,
>
> On 16-Aug-26 22:42, James Alexander wrote:
>> The OVTI08F4 sensor on an HP Spectre x360 14-eu0xxx failed to read its
>> chip ID with error -121 when the existing 45 ms handshake delay was used.
>> Increasing the delay to 150 ms allowed the sensor to probe.
>>
>> Keep the existing delay for other OVTI08F4 systems. Add a reusable
>> handshake-delay field to the discrete-device quirks and set it only for the
>> affected HP Spectre family through DMI matching.
>>
>> Compile-tested against Linux base fd923b32d761. Hardware-tested with the
>> full patch set across 25 consecutive reboots on the affected laptop running
>> Ubuntu 7.0.0-29-generic; the sensor probed successfully on every boot.
>>
>> Signed-off-by: James Alexander <opensource@inspiredexperts.com>
>
> Thank you for your patch.
>
> There have been more reports about the 45 ms not being enough of a delay,
> but IIRC I never got around to bumping the delay because even with
> a bigger delay on the laptop in question the probe would still fail
> approx. every 1 out of 10 boots and we got stuck on debugging that.
>
> And then I dropped the bal on this, sorry.
>
> See:
> https://bugzilla.redhat.com/show_bug.cgi?id=2333331
Funny after re-reading that bug I see you are one of the reporters
of it, again sorry for dropping the ball on this.
> https://bugzilla.redhat.com/show_bug.cgi?id=2333647
And this is more or less the same thing, but here the sensor is
a hi556. So it looks like the fix is to simply boost the handshake
pin default delay to 200 ms instead of having a model / device
specific quirk, dropping the existing OVTI08F4 quirk.
I'll go and prepare a patch for this and submit it upstream myself.
Regards,
Hans
prev parent reply other threads:[~2026-08-18 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 20:42 [PATCH] platform/x86: int3472: add HP Spectre handshake delay James Alexander
2026-08-18 10:15 ` Ilpo Järvinen
2026-08-18 10:43 ` Hans de Goede
2026-08-18 11:00 ` Hans de Goede [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=a135b02a-a4e6-4abe-940c-a93bf0ea807a@kernel.org \
--to=hansg@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=opensource@inspiredexperts.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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