From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
gregkh@linuxfoundation.org, broonie@kernel.org,
srinivas.kandagatla@linaro.org,
Bard liao <yung-chuan.liao@linux.intel.com>,
Rander Wang <rander.wang@linux.intel.com>
Subject: Re: [PATCH v2 1/2] soundwire: bus: add enumerated Slave device to device list
Date: Sat, 19 Sep 2020 16:43:30 +0530 [thread overview]
Message-ID: <20200919111330.GV2968@vkoul-mobl> (raw)
In-Reply-To: <eb02ba7f-5f80-cfde-9225-064d185fd64d@linux.intel.com>
On 18-09-20, 08:54, Pierre-Louis Bossart wrote:
>
>
> On 9/18/20 7:05 AM, Vinod Koul wrote:
> > On 17-09-20, 11:00, Pierre-Louis Bossart wrote:
> > > From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> > >
> > > Currently Slave devices are only added on startup, either from Device
> > > Tree or ACPI entries. However Slave devices that are physically
> > > present on the bus, but not described in platform firmware, will never
> > > be added to the device list. The user/integrator can only know the
> > > list of devices by looking a dynamic debug logs.
> > >
> > > This patch suggests adding a Slave device eveb there is no matching DT or
> > > ACPI entry, so that we can see this in sysfs entry.
> > >
> > > Initial code from Srinivas. Comments, fixes for ACPI probe and edits
> > > of commit message by Pierre.
> >
> > You should add yours as Co-developed. That is the standard tag for these
> > things
>
> ok, I've never used this tag before but it seems appropriate indeed, thanks
> for the suggestion.
>
> Should I add your Co-developed tag to the second patch as well then?
Sure
--
~Vinod
next prev parent reply other threads:[~2020-09-19 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 16:00 [PATCH v2 0/2] soundwire: sysfs: expose device number and status Pierre-Louis Bossart
2020-09-17 16:00 ` [PATCH v2 1/2] soundwire: bus: add enumerated Slave device to device list Pierre-Louis Bossart
2020-09-18 12:05 ` Vinod Koul
2020-09-18 13:54 ` Pierre-Louis Bossart
2020-09-19 11:13 ` Vinod Koul [this message]
2020-09-17 16:00 ` [PATCH v2 2/2] soundwire: sysfs: add slave status and device number before probe Pierre-Louis Bossart
2020-09-17 16:36 ` Greg KH
2020-09-18 12:16 ` Vinod Koul
2020-09-18 14:21 ` Pierre-Louis Bossart
2020-09-19 11:19 ` Vinod Koul
2020-09-21 14:34 ` Pierre-Louis Bossart
2020-09-23 10:03 ` Vinod Koul
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=20200919111330.GV2968@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.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;
as well as URLs for NNTP newsgroup(s).