From: Hermes Wu via B4 Relay <devnull+Hermes.wu.ite.com.tw@kernel.org>
To: Hermes Wu <Hermes.Wu@ite.com.tw>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Hermes Wu <Hermes.wu@ite.com.tw>
Subject: [PATCH v2 0/2] media: i2c: it6625: fix MCU reset and host control timing
Date: Wed, 07 Oct 2026 18:31:51 +0800 [thread overview]
Message-ID: <20261007-upstream-it6625-reset-delay-v2-0-c5d6b2522bbe@ite.com.tw> (raw)
The IT6625/IT6626 are driven through an on-chip MCU. The driver does not
give the MCU enough time in two places: after releasing reset in probe,
and when waiting for the MCU to acknowledge a host control request.
Both can cause spurious failures.
Patch 1 waits 1s after reset release before the chip-ID read.
Patch 2 raises the host control request timeout from 25 ms to 250 ms.
Signed-off-by: Hermes Wu <Hermes.wu@ite.com.tw>
---
Changes in v2:
- Patch 1: increase the post-reset wait from 700 ms to 1s.
- Patch 2: new, raise the host control request timeout to 250 ms.
- Link to v1: https://lore.kernel.org/r/20261006-upstream-it6625-reset-delay-v1-1-e4cb3c74e6d3@ite.com.tw
---
Hermes Wu (2):
media: i2c: it6625: wait 1s after reset release
media: i2c: it6625: allow 250 ms for host control requests to complete
drivers/media/i2c/it6625.c | 23 +++++++++++++++++------
1 file changed, 17 insertions(+), 6 deletions(-)
---
base-commit: 89a3d2a2237e017cdbefcb036db71ce74e67faf5
change-id: 20261006-upstream-it6625-reset-delay-3239507c5f09
Best regards,
--
Hermes Wu <Hermes.wu@ite.com.tw>
next reply other threads:[~2026-10-07 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 10:31 Hermes Wu via B4 Relay [this message]
2026-10-07 10:31 ` [PATCH v2 1/2] media: i2c: it6625: wait 1s after reset release Hermes Wu via B4 Relay
2026-10-07 10:31 ` [PATCH v2 2/2] media: i2c: it6625: allow 250 ms for host control requests to complete Hermes Wu via B4 Relay
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=20261007-upstream-it6625-reset-delay-v2-0-c5d6b2522bbe@ite.com.tw \
--to=devnull+hermes.wu.ite.com.tw@kernel.org \
--cc=Hermes.Wu@ite.com.tw \
--cc=hverkuil+cisco@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®