Alsa-Devel Archive on
 help / color / Atom feed
From: Greg KH <>
To: Pierre-Louis Bossart <>
	Ranjani Sridharan <>,,,,,,
	Bard liao <>,
	Rander Wang <>
Subject: Re: [alsa-devel] [RFC PATCH 0/2] soundwire: add master_device/driver support
Date: Fri, 14 Feb 2020 08:49:19 -0800
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jan 31, 2020 at 10:20:09PM -0600, Pierre-Louis Bossart wrote:
> The SoundWire master representation needs to evolve to take into account:
> a) a May 2019 recommendation from Greg KH to remove platform devices
> b) the need on Intel platforms to support hardware startup only once
> the power rail dependencies are settled. The SoundWire master is not
> an independent IP at all.
> c) the need to deal with external wakes handled by the PCI subsystem
> in specific low-power modes
> In case it wasn't clear, the SoundWire subsystem is currently unusable
> with v5.5 on devices hitting the shelves very soon (race conditions,
> power management, suspend/resume, etc). v5.6 will only provide
> interface changes and no functional improvement. We've circled on the
> same concepts since September 2019, and I hope this direction is now
> aligned with the suggestions from Vinod Koul and that we can target
> v5.7 as the 'SoundWire just works(tm)' version.
> This series is provided as an RFC since it depends on patches already
> for review.

Both of these look sane to me, nice work!

Reviewed-by: Greg Kroah-Hartman <>
Alsa-devel mailing list

  parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01  4:20 Pierre-Louis Bossart
2020-02-01  4:20 ` [alsa-devel] [RFC PATCH 1/2] soundwire: bus_type: " Pierre-Louis Bossart
2020-02-01  4:20 ` [alsa-devel] [RFC PATCH 2/2] soundwire: intel: transition to sdw_master_device/driver support Pierre-Louis Bossart
2020-02-14 16:49 ` Greg KH [this message]
2020-02-14 23:34   ` [alsa-devel] [RFC PATCH 0/2] soundwire: add master_device/driver support Pierre-Louis Bossart
2020-02-15  0:05     ` Greg KH

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Alsa-Devel Archive on

Archives are clonable:
	git clone --mirror alsa-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 alsa-devel alsa-devel/ \
	public-inbox-index alsa-devel

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone