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,
	kai.vehmanen@linux.intel.com, ranjani.sridharan@linux.intel.com,
	yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
	stable@vger.kernel.org
Subject: Re: [PATCH 0/3] ASoC: SOF: ipc4/Intel: Fix the host buffer constraint
Date: Thu, 2 Oct 2025 15:46:30 +0300	[thread overview]
Message-ID: <f60fc257-36ed-4bd1-af1a-6fca4a91a532@linux.intel.com> (raw)
In-Reply-To: <88555c06-ccf5-4639-b13f-892149b5faa3@sirena.org.uk>



On 02/10/2025 15:25, Mark Brown wrote:
> On Thu, Oct 02, 2025 at 11:05:35AM +0300, Peter Ujfalusi wrote:
>> Hi,
>>
>> The size of the DSP host buffer was incorrectly defined as 2ms while
>> it is 4ms and the ChainDMA PCMs are using 5ms as host facing buffer.
> 
> None of the fixes tags in this series point to commits in my tree.

Hrm, they are upstream, I will check and resend, sorry

-- 
Péter


  reply	other threads:[~2025-10-02 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  8:05 [PATCH 0/3] ASoC: SOF: ipc4/Intel: Fix the host buffer constraint Peter Ujfalusi
2025-10-02  8:05 ` [PATCH 1/3] ASoC: SOF: ipc4-topology: Correct the minimum host DMA buffer size Peter Ujfalusi
2025-10-02  8:05 ` [PATCH 2/3] ASoC: SOF: ipc4-topology: Account for different ChainDMA host " Peter Ujfalusi
2025-10-02  8:05 ` [PATCH 3/3] ASoC: SOF: Intel: hda-pcm: Place the constraint on period time instead of buffer time Peter Ujfalusi
2025-10-02 12:25 ` [PATCH 0/3] ASoC: SOF: ipc4/Intel: Fix the host buffer constraint Mark Brown
2025-10-02 12:46   ` Péter Ujfalusi [this message]
2025-10-02 17:39 ` 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=f60fc257-36ed-4bd1-af1a-6fca4a91a532@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.dev \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --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