From: Mark Brown <broonie@kernel.org>
To: Zhang Yi <zhangyi@everest-semi.com>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
ckeepax@opensource.cirrus.com
Subject: Re: [PATCH v7 3/5] ASoC: es9356-sdca: Add ES9356 SDCA driver
Date: Fri, 10 Apr 2026 14:48:53 +0100 [thread overview]
Message-ID: <adj_xa-nA4KZ5Kkx@sirena.co.uk> (raw)
In-Reply-To: <20260410072441.6111-4-zhangyi@everest-semi.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On Fri, Apr 10, 2026 at 03:24:39PM +0800, Zhang Yi wrote:
> This is the codec driver for es9356-sdca.
> +static int es9356_sdw_update_status(struct sdw_slave *slave,
> + enum sdw_slave_status status)
> +{
> + struct es9356_sdw_priv *es9356 = dev_get_drvdata(&slave->dev);
> +
> + if (status == SDW_SLAVE_UNATTACHED)
> + es9356->hw_init = false;
Should this cancel the work associated with the jack, if the device
isn't on the bus any more we won't be able to update state? Might also
make sense for the device to be cache only...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-10 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 7:24 [PATCH v7 0/5] Add es9356 focused SoundWire CODEC Zhang Yi
2026-04-10 7:24 ` [PATCH v7 1/5] ASoC: sdw_utils: add soc_sdw_es9356 Zhang Yi
2026-04-10 7:24 ` [PATCH v7 2/5] ASoC: sdw_utils: add ES9356 in codec_info_list Zhang Yi
2026-04-10 7:24 ` [PATCH v7 3/5] ASoC: es9356-sdca: Add ES9356 SDCA driver Zhang Yi
2026-04-10 13:48 ` Mark Brown [this message]
2026-04-10 7:24 ` [PATCH v7 4/5] ASoC: Intel: soc-acpi: arl: Add es9356 support Zhang Yi
2026-04-10 7:24 ` [PATCH v7 5/5] ASoC: Intel: sof_sdw: add " Zhang Yi
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=adj_xa-nA4KZ5Kkx@sirena.co.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@linux.intel.com \
--cc=zhangyi@everest-semi.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