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 14:57:02 +0300	[thread overview]
Message-ID: <53897d0f-1796-4823-9090-a51320c655a4@linux.intel.com> (raw)
In-Reply-To: <3a7fa9d4-dd14-4b29-b977-3ba9c5b4ade7@sirena.org.uk>



On 29/05/2024 14:48, Mark Brown wrote:
> On Wed, May 29, 2024 at 02:19:37PM +0300, Péter Ujfalusi wrote:
>> On 16/05/2024 10:56, Peter Ujfalusi wrote:
> 
>>> The ACPI NHLT table always had 32-bit DMIC blob even if 16-bit was also
>>> present and taken as a 'rule' which obviously got broken and there is at
>>> least one device on the market which ships with only 16-bit DMIC
>>> configuration blob.
>>> This corner case has never been supported and it is going to need topology
>>> updates for DMIC copier to support multiple formats.
> 
>> Please ignore this patch, I will send it again along with few more patch
>> building on this to close the gaps with the logic of selecting the NHLT
>> blob.
> 
> 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.

-- 
Péter

  reply	other threads:[~2024-05-29 11:56 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 [this message]
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
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=53897d0f-1796-4823-9090-a51320c655a4@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