From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org, gregkh@linuxfoundation.org,
jank@cadence.com, srinivas.kandagatla@linaro.org,
rander.wang@linux.intel.com, ranjani.sridharan@linux.intel.com,
hui.wang@canonical.com, pierre-louis.bossart@linux.intel.com,
sanyog.r.kale@intel.com, slawomir.blauciak@intel.com,
mengdong.lin@intel.com, bard.liao@intel.com
Subject: Re: [PATCH v2 0/5] soundwire: bus_type: add sdw_master_device support
Date: Tue, 19 May 2020 12:49:58 +0530 [thread overview]
Message-ID: <20200519071958.GL374218@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20200518174322.31561-1-yung-chuan.liao@linux.intel.com>
On 19-05-20, 01:43, Bard Liao wrote:
> This series adds sdw master devices support.
>
> changes in v2:
> - Allocate sdw_master_device dynamically
> - Use unique bus id as master id
> - Keep checking parent devices
> - Enable runtime_pm on Master device
I tested on RB3 board and it looks good to me, Applied all now.
Thanks for the good cleanup :)
--
~Vinod
prev parent reply other threads:[~2020-05-19 7:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 17:43 Bard Liao
2020-05-18 17:43 ` [PATCH v2 1/5] soundwire: bus: rename sdw_bus_master_add/delete, add arguments Bard Liao
2020-05-18 17:43 ` [PATCH v2 2/5] soundwire: bus_type: introduce sdw_slave_type and sdw_master_type Bard Liao
2020-05-18 17:43 ` [PATCH v2 3/5] soundwire: bus: add unique bus id Bard Liao
2020-05-18 17:43 ` [PATCH v2 4/5] soundwire: bus_type: add sdw_master_device support Bard Liao
2020-05-18 17:43 ` [PATCH v2 5/5] soundwire: master: add runtime pm support Bard Liao
2020-05-19 6:47 ` [PATCH v2 0/5] soundwire: bus_type: add sdw_master_device support Jaroslav Kysela
2020-05-19 7:19 ` 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=20200519071958.GL374218@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--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 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®