Linux Sound subsystem development
 help / color / mirror / Atom feed
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 15:32:24 +0300	[thread overview]
Message-ID: <80498cd3-609b-4ec0-aedc-3ef6d4bde408@linux.intel.com> (raw)
In-Reply-To: <cc7fc8b7-d470-4330-8cb5-6ba85065c74d@sirena.org.uk>



On 29/05/2024 15:17, Mark Brown wrote:
> On Wed, May 29, 2024 at 02:57:02PM +0300, Péter Ujfalusi wrote:
>> On 29/05/2024 14:48, Mark Brown wrote:
> 
>>> Sorry, it's already been applied and published with more stuff in CI now
>>> based on it.
> 
>> Right, I don't see it in for-next, for-6.10 or for-linus. This patch
>> should be sent for 6.10 and I can prepare and send the rest (4 more
>> patches) to close the remaining holes regarding to NHLT blob selection
>> logic.
> 
> If something is a bug fix it shouldn't have a subject saying "Add
> support", that is very obvioulsy a new feature.  Have these systems ever
> worked?

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).

The mentioned additional patches would future proof this whole DMIC blob
lookup by extending it beyond the bytes per sample.
These are future proofing and a would be nice fixes for the -rc, but if
not than 6.11 is OK.

In short, yes it worked well but we were presented with  unimaginable
vendor creativity.

[1] https://github.com/thesofproject/linux/issues/4973

-- 
Péter

  reply	other threads:[~2024-05-29 12:32 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 [this message]
2024-05-29 13:36           ` Mark Brown
2024-05-29 13:49             ` Péter Ujfalusi
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=80498cd3-609b-4ec0-aedc-3ef6d4bde408@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