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 v2 1/3] ASoC: SOF: ipc4-topology: Correct the minimum host DMA buffer size
Date: Mon, 20 Oct 2025 11:00:42 +0300 [thread overview]
Message-ID: <c22ce363-4ba9-4b6b-b3e2-a3b2d23dbdd9@linux.intel.com> (raw)
In-Reply-To: <de8f8b56-ef5d-4d58-92ec-38280badcfb0@sirena.org.uk>
On 20/10/2025 04:41, Mark Brown wrote:
> On Thu, Oct 02, 2025 at 03:53:20PM +0300, Peter Ujfalusi wrote:
>> The firmware has changed the minimum host buffer size from 2 periods to
>> 4 periods (1 period is 1ms) which was missed by the kernel side.
>>
>> Adjust the SOF_IPC4_MIN_DMA_BUFFER_SIZE to 4 ms to align with firmware.
>
> This doesn't apply as a fix, please check and resend.
I think you have already taken this patch, it is in 6.18-rc1:
a7fe5ff832d6 ("ASoC: SOF: ipc4-topology: Correct the minimum host DMA
buffer size")
--
Péter
next prev parent reply other threads:[~2025-10-20 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 12:53 [PATCH v2 0/3] ASoC: SOF: ipc4/Intel: Fix the host buffer constraint Peter Ujfalusi
2025-10-02 12:53 ` [PATCH v2 1/3] ASoC: SOF: ipc4-topology: Correct the minimum host DMA buffer size Peter Ujfalusi
2025-10-20 1:41 ` Mark Brown
2025-10-20 8:00 ` Péter Ujfalusi [this message]
2025-10-02 12:53 ` [PATCH v2 2/3] ASoC: SOF: ipc4-topology: Account for different ChainDMA host " Peter Ujfalusi
2025-10-02 12:53 ` [PATCH v2 3/3] ASoC: SOF: Intel: hda-pcm: Place the constraint on period time instead of buffer time Peter Ujfalusi
2025-10-02 13:08 ` [PATCH v2 0/3] ASoC: SOF: ipc4/Intel: Fix the host buffer constraint Mark Brown
2025-10-02 13:59 ` Péter Ujfalusi
2025-10-02 17:39 ` Mark Brown
2025-10-03 14:33 ` 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=c22ce363-4ba9-4b6b-b3e2-a3b2d23dbdd9@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