From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Maurizio Casciano <mauriziocasciano7@gmail.com>
Cc: <liam.r.girdwood@linux.intel.com>,
<peter.ujfalusi@linux.intel.com>,
<yung-chuan.liao@linux.intel.com>, <kai.vehmanen@linux.intel.com>,
<pierre-louis.bossart@linux.dev>, <perex@perex.cz>,
<tiwai@suse.com>, <jekhor@gmail.com>,
<linux-kernel@vger.kernel.org>, <broonie@kernel.org>,
<linux-sound@vger.kernel.org>
Subject: Re: [PATCH v6 0/2] ASoC: Intel: Add Yoga Book RT5677 support
Date: Wed, 2 Sep 2026 10:25:49 +0200 [thread overview]
Message-ID: <83d7a9ee-e164-4f02-b83c-31be3fe43fdc@intel.com> (raw)
In-Reply-To: <cover.1788286335.git.mauriziocasciano7@gmail.com>
On 9/1/2026 9:04 PM, Maurizio Casciano wrote:
> Hi,
>
> This series adds the Cherry Trail machine driver and machine-table entry
> needed by the Lenovo Yoga Book YB1-X91F/L with its RT5677 codec and
> TS3A227E headset detector.
>
> Only the SOF path is enabled. Legacy SST is deliberately not advertised
> because it has not been validated on this hardware.
Before I move on to the review, this is contrary to what Yauhen claimed
in v2 [1]. So, are we just rolling the dice here? If you have tested
both, it's OK to have both supported. Changing in the middle of review
does not increase credibility.
[1]: https://lore.kernel.org/all/aaYRd2Irw8bOpDL0@jekhomev/
next prev parent reply other threads:[~2026-09-02 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 19:04 [PATCH v6 0/2] ASoC: Intel: Add Yoga Book RT5677 support Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 1/2] ASoC: Intel: Add Cherry Trail RT5677 machine driver Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 2/2] ASoC: Intel: cht: Add Yoga Book RT5677 machine entry Maurizio Casciano
2026-09-02 8:25 ` Cezary Rojewski [this message]
2026-09-02 8:46 ` [PATCH v6 0/2] ASoC: Intel: Add Yoga Book RT5677 support Maurizio Casciano
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=83d7a9ee-e164-4f02-b83c-31be3fe43fdc@intel.com \
--to=cezary.rojewski@intel.com \
--cc=broonie@kernel.org \
--cc=jekhor@gmail.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mauriziocasciano7@gmail.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@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 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.