From: Greg KH <gregkh@linuxfoundation.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
linux-kernel@vger.kernel.org,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
vkoul@kernel.org, broonie@kernel.org,
srinivas.kandagatla@linaro.org, jank@cadence.com,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: Re: [alsa-devel] [RFC PATCH 0/2] soundwire: add master_device/driver support
Date: Fri, 14 Feb 2020 08:49:19 -0800 [thread overview]
Message-ID: <20200214164919.GB4016987@kroah.com> (raw)
In-Reply-To: <20200201042011.5781-1-pierre-louis.bossart@linux.intel.com>
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 <gregkh@linuxfoundation.org>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, vkoul@kernel.org,
jank@cadence.com, srinivas.kandagatla@linaro.org,
slawomir.blauciak@intel.com,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [RFC PATCH 0/2] soundwire: add master_device/driver support
Date: Fri, 14 Feb 2020 08:49:19 -0800 [thread overview]
Message-ID: <20200214164919.GB4016987@kroah.com> (raw)
In-Reply-To: <20200201042011.5781-1-pierre-louis.bossart@linux.intel.com>
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 <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2020-02-14 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 4:20 [alsa-devel] [RFC PATCH 0/2] soundwire: add master_device/driver support Pierre-Louis Bossart
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 ` 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-01 4:20 ` Pierre-Louis Bossart
2020-02-14 16:49 ` Greg KH [this message]
2020-02-14 16:49 ` [RFC PATCH 0/2] soundwire: add master_device/driver support Greg KH
2020-02-14 23:34 ` [alsa-devel] " Pierre-Louis Bossart
2020-02-14 23:34 ` Pierre-Louis Bossart
2020-02-15 0:05 ` Greg KH
2020-02-15 0:05 ` Greg KH
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=20200214164919.GB4016987@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
--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.