All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	pierre-louis.bossart@linux.dev, bard.liao@intel.com
Subject: Re: [PATCH 0/3] soundwire: send multi sections in one BPT stream
Date: Wed, 12 Nov 2025 10:42:58 +0530	[thread overview]
Message-ID: <aRQXWpLqDm8EduYN@vaman> (raw)
In-Reply-To: <20251021094355.132943-1-yung-chuan.liao@linux.intel.com>

On 21-10-25, 17:43, Bard Liao wrote:
> Currently we send a BRA message with a start address with continuous
> registers in a BPT stream. However, a codec may need to write different
> register sections shortly. It makes more sense to send different
> register sections in a BPT stream and no need to close/open the BPT
> stream repeatedly.
> 
> This series depends on the "ASoC/soundwire: add fake BPT frame to align
> Intel DMA buffer size" series. Sending it now to get more review time.

I have applied it on top of above series, pls check why it is not
applying in :
error: patch failed: drivers/soundwire/intel_ace2x.c:156
error: drivers/soundwire/intel_ace2x.c: patch does not apply

-- 
~Vinod

  parent reply	other threads:[~2025-11-12  5:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21  9:43 [PATCH 0/3] soundwire: send multi sections in one BPT stream Bard Liao
2025-10-21  9:43 ` [PATCH 1/3] soundwire: introduce BPT section Bard Liao
2025-10-21  9:43 ` [PATCH 2/3] soundwire: pass sdw_bpt_section to cdns BPT helpers Bard Liao
2025-10-21  9:43 ` [PATCH 3/3] soundwire: intel_ace2x: handle multi BPT sections Bard Liao
2025-11-12  5:12 ` Vinod Koul [this message]
2025-11-12  6:13   ` [PATCH 0/3] soundwire: send multi sections in one BPT stream Liao, Bard
2025-11-12  8:46     ` Vinod Koul
2025-11-12  8:45 ` Vinod Koul

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=aRQXWpLqDm8EduYN@vaman \
    --to=vkoul@kernel.org \
    --cc=bard.liao@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.