From: Sergey Lebedev <lsa.uz@pm.me>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: bard.liao@intel.com, broonie@kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
oder_chiou@realtek.com, perex@perex.cz, shumingf@realtek.com,
tiwai@suse.com, vkoul@kernel.org,
yung-chuan.liao@linux.intel.com, zlzzm2014@outlook.com
Subject: Re: [PATCH v3 2/2] soundwire: dmi-quirks: drop the ghost RT1320 on the Surface Pro 11 (Intel)
Date: Fri, 04 Sep 2026 15:10:32 +0000 [thread overview]
Message-ID: <20260904151020.44426-1-lsa.uz@pm.me> (raw)
In-Reply-To: <592f3b8b-03a2-47b9-b275-b691cbd42d79@linux.dev>
Pierre-Louis,
Point taken on the length, and thank you for the MIPI WG history — that is
the part I had no way to find, and it settles what I was asking. I will
leave NEWLY_ATTACHED and HAS_BEEN_RESET alone.
On bisect: the status register is read before the condition is evaluated,
so no version of that test can change the value — bisecting the driver
would read the same thing throughout. What differs is the machine, two
months apart, and I cannot recreate July to walk between them. So it stays
unexplained, and by your account it does not need to be: only
NEEDS_INITIALIZATION matters, and first_hw_init OR the bit is what the
driver now does.
Sergey
next prev parent reply other threads:[~2026-09-04 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 15:15 [PATCH v3 0/2] ASoC: fix audio on the Microsoft Surface Pro 11 (Intel) Sergey Lebedev
2026-08-30 15:15 ` [PATCH v3 1/2] ASoC: rt1320: run the initialisation preset on the first hardware init Sergey Lebedev
2026-08-30 15:15 ` [PATCH v3 2/2] soundwire: dmi-quirks: drop the ghost RT1320 on the Surface Pro 11 (Intel) Sergey Lebedev
2026-08-30 21:12 ` Sergey Lebedev
2026-09-04 7:51 ` Pierre-Louis Bossart
2026-09-04 12:36 ` Sergey Lebedev
2026-09-04 14:09 ` Pierre-Louis Bossart
2026-09-04 15:10 ` Sergey Lebedev [this message]
2026-08-30 17:47 ` [PATCH v3 0/2] ASoC: fix audio on the Microsoft " Sergey Lebedev
2026-09-13 21:11 ` Sergey Lebedev
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=20260904151020.44426-1-lsa.uz@pm.me \
--to=lsa.uz@pm.me \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.dev \
--cc=shumingf@realtek.com \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.com \
--cc=zlzzm2014@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.