mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Karelin <a.karelin@ideco.ru>
To: Srinivas Kandagatla <srini@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Andrey Karelin <a.karelin@ideco.ru>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: [PATCH 0/2] ASoC: codecs: propagate sdw_write() errors from bus_config callbacks
Date: Fri, 16 Oct 2026 19:33:34 +0500	[thread overview]
Message-ID: <20261016143341.417876-1-a.karelin@ideco.ru> (raw)

wsa881x_bus_config() and wcd_bus_config() (shared by the WCD938x and
WCD939x SoundWire drivers) program the clock divider for the next bank
with sdw_write() but ignore its result and always return 0, so a failed
write is never reported to sdw_notify_config(). The other SoundWire
codec drivers that implement bus_config already return the error.

Both patches simply return the result of sdw_write().

Andrey Karelin (2):
  ASoC: codecs: wsa881x: propagate sdw_write() error from bus_config
  ASoC: codecs: wcd-common: propagate sdw_write() error from bus_config

 sound/soc/codecs/wcd-common.c | 4 +---
 sound/soc/codecs/wsa881x.c    | 6 ++----
 2 files changed, 3 insertions(+), 7 deletions(-)


base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907
-- 
2.56.0



             reply	other threads:[~2026-10-16 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 14:33 Andrey Karelin [this message]
2026-10-16 14:33 ` [PATCH 1/2] ASoC: codecs: wsa881x: propagate sdw_write() error from bus_config Andrey Karelin
2026-10-16 14:33 ` [PATCH 2/2] ASoC: codecs: wcd-common: " Andrey Karelin

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=20261016143341.417876-1-a.karelin@ideco.ru \
    --to=a.karelin@ideco.ru \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=neil.armstrong@linaro.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=srini@kernel.org \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®