From: Maciej Strozek <mstrozek@opensource.cirrus.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mark Brown <broonie@kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: SDCA: Add quirk for incorrect function types for 3 systems
Date: Mon, 01 Sep 2025 14:28:48 +0000 [thread overview]
Message-ID: <3643b07326567604a6ba5b59ece84903dffcd3e5.camel@opensource.cirrus.com> (raw)
In-Reply-To: <87tt1m5kvl.wl-tiwai@suse.de>
W dniu pon, 01.09.2025 o godzinie 16∶05 +0200, użytkownik Takashi Iwai
napisał:
> On Mon, 01 Sep 2025 09:57:46 +0200,
> Maciej Strozek wrote:
> >
> > Certain systems have CS42L43 DisCo that claims to conform to
> > version 0.6.28
> > but uses the function types from the 1.0 spec. Add a quirk as a
> > workaround.
> >
> > Signed-off-by: Maciej Strozek <mstrozek@opensource.cirrus.com>
>
> It's a fix for the report below, right?
> https://github.com/thesofproject/linux/issues/5515
> Then please put it to Link tag. Also at best give Fixes tag if you
> can give some hint for the stable backports.
>
That's correct, will put the Link in v2, thanks.
Not sure however if Fixes tag is appropriate (not fixing a bug in a
kernel commit but in the ACPI after all) - maybe a "Cc:
stable@vger.kernel.org" is going to be enough?
>
> thanks,
>
> Takashi
--
Regards,
Maciej
next prev parent reply other threads:[~2025-09-01 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 7:57 [PATCH] ASoC: SDCA: Add quirk for incorrect function types for 3 systems Maciej Strozek
2025-09-01 13:55 ` Pierre-Louis Bossart
2025-09-01 14:05 ` Takashi Iwai
2025-09-01 14:28 ` Maciej Strozek [this message]
2025-09-01 14:47 ` Takashi Iwai
2025-09-02 11:51 ` 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=3643b07326567604a6ba5b59ece84903dffcd3e5.camel@opensource.cirrus.com \
--to=mstrozek@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=tiwai@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).