From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, linux-sound@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
kai.vehmanen@linux.intel.com, ranjani.sridharan@linux.intel.com,
seppo.ingalsuo@linux.intel.com
Subject: Re: [PATCH] ASoC: SOF: ipc4-topology: Add support for NHLT with 16-bit only DMIC blob
Date: Wed, 29 May 2024 16:49:01 +0300 [thread overview]
Message-ID: <acd6b6f2-710f-43c2-8666-77ac64dee6fa@linux.intel.com> (raw)
In-Reply-To: <cec50849-66ac-4557-856c-a6a423c118f6@sirena.org.uk>
On 29/05/2024 16:36, Mark Brown wrote:
>> Well, it is adding support for something which has never been consider
>> as a valid configuration (16bit only DMIC blob in NHLT table of a laptop
>> [1]).
>> I have added to fixes tag to carry this patch along with the patch that
>> implemented support for preferring 32bit configuration in firmware (the
>> [1] would never worked, so that is unrelated).
>
> Fixes tags are so widely abused that I don't generally pay a huge amount
> of attention to them, the pattern of new features claiming to fix the
> commit where something was introduced is very common.
Understood.
> In any case, if you're going to send a series for 6.10 I guess I'll
> leave it for now.
Should I include this patch to the series for 6.10 or wait until this
patch is available somewhere that I can base my series on?
--
Péter
next prev parent reply other threads:[~2024-05-29 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 7:56 [PATCH] ASoC: SOF: ipc4-topology: Add support for NHLT with 16-bit only DMIC blob Peter Ujfalusi
2024-05-29 11:19 ` Péter Ujfalusi
2024-05-29 11:48 ` Mark Brown
2024-05-29 11:57 ` Péter Ujfalusi
2024-05-29 12:17 ` Mark Brown
2024-05-29 12:32 ` Péter Ujfalusi
2024-05-29 13:36 ` Mark Brown
2024-05-29 13:49 ` Péter Ujfalusi [this message]
2024-05-29 13:52 ` Mark Brown
2024-05-30 15:21 ` 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=acd6b6f2-710f-43c2-8666-77ac64dee6fa@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=seppo.ingalsuo@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