Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Zhang Yi <zhangyi@everest-semi.com>,
	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 v14 6/6] soundwire: intel_auxdevice: Add es9356 to wake_capable_list
Date: Thu, 14 May 2026 20:40:35 +0530	[thread overview]
Message-ID: <agXl6wp-LCw_2vRa@vaman> (raw)
In-Reply-To: <agUh5D5LFxanFSHc@sirena.co.uk>

On 14-05-26, 10:14, Mark Brown wrote:
> On Wed, May 13, 2026 at 09:09:27PM +0530, Vinod Koul wrote:
> > On 13-05-26, 11:15, Zhang Yi wrote:
> > > Add es9356 to the wake_capable_list
> > > because it can generate jack events whilst the bus is stopped
> > 
> > Does this need to go thru ASoC tree, I can pick it up..
> 
> There's no dependency.

Thanks, I will pick this up

-- 
~Vinod

      reply	other threads:[~2026-05-14 15:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13  3:15 [PATCH v14 0/6] Add es9356 focused SoundWire CODEC Zhang Yi
2026-05-13  3:15 ` [PATCH v14 1/6] ASoC: sdw_utils: add soc_sdw_es9356 Zhang Yi
2026-05-13  3:15 ` [PATCH v14 2/6] ASoC: sdw_utils: add ES9356 in codec_info_list Zhang Yi
2026-05-13  3:15 ` [PATCH v14 3/6] ASoC: es9356-sdca: Add ES9356 SDCA driver Zhang Yi
2026-05-14  7:11   ` Mark Brown
2026-05-13  3:15 ` [PATCH v14 4/6] ASoC: Intel: soc-acpi: arl: Add es9356 support Zhang Yi
2026-05-13  3:15 ` [PATCH v14 5/6] ASoC: Intel: sof_sdw: add " Zhang Yi
2026-05-13  3:15 ` [PATCH v14 6/6] soundwire: intel_auxdevice: Add es9356 to wake_capable_list Zhang Yi
2026-05-13 15:39   ` Vinod Koul
2026-05-14  1:14     ` Mark Brown
2026-05-14 15:10       ` Vinod Koul [this message]

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=agXl6wp-LCw_2vRa@vaman \
    --to=vkoul@kernel.org \
    --cc=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