From: "Shuming [范書銘]" <shumingf@realtek.com>
To: Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"Flove(HsinFu)" <flove@realtek.com>,
"Oder Chiou" <oder_chiou@realtek.com>,
"Jack Yu" <jack.yu@realtek.com>,
"Derek [方德義]" <derek.fang@realtek.com>
Subject: RE: [PATCH] ASoC: rt766: trigger JD when system reboots
Date: Wed, 7 Oct 2026 11:03:24 +0000 [thread overview]
Message-ID: <87341bc3edca474cad3c11607fd25b26@realtek.com> (raw)
In-Reply-To: <asYjO4n9fy8qC3kc@sirena.co.uk>
> On Wed, Oct 07, 2026 at 05:25:24PM +0800, shumingf@realtek.com wrote:
> > From: Shuming Fan <shumingf@realtek.com>
> >
> > The initial jack detection at boot time may be missed after a warm
> > reboot if the blind writes are not reloaded.
>
> How does this happen - this feels like it's masking the failure to resume
> properly after a warm reboot and there's more that needs to be set up in that
> case?
The blind write also includes a trigger command to trigger JD.
Therefore, this issue does not occur before merging the "ASoC: rt766: avoid re-initialize the blind write" patch.
The issue only occurs when the system does not detect that the jack is already plugged in during warm reboot.
If the user plugs or unplugs the jack afterward, the JD interrupt still works normally.
next prev parent reply other threads:[~2026-10-07 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 9:25 [PATCH] ASoC: rt766: trigger JD when system reboots shumingf
2026-10-07 10:47 ` Mark Brown
2026-10-07 11:03 ` Shuming [范書銘] [this message]
2026-10-07 15:26 ` Mark Brown
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=87341bc3edca474cad3c11607fd25b26@realtek.com \
--to=shumingf@realtek.com \
--cc=broonie@kernel.org \
--cc=derek.fang@realtek.com \
--cc=flove@realtek.com \
--cc=jack.yu@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.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