From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: yung-chuan.liao@linux.intel.com, sanyog.r.kale@intel.com,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soundwire: bus: add enumerated slave to device list
Date: Thu, 10 Sep 2020 09:02:36 -0500 [thread overview]
Message-ID: <f3880470-cdc4-7b84-97a1-303f9a95d3f4@linux.intel.com> (raw)
In-Reply-To: <20200910085621.GS77521@vkoul-mobl>
>>> May be we could make the enumerated devices discovery bit more verbose!
>>
>> Maybe adding a device number sysfs entry would help, e.g. reporting
>> NotAttched or a value in [0,11] would tell you if the device is actually
>> present.
>
> Agreed, I cooked this patch to report verbose device status, let me know
> if you are okay with this. I think this would be useful regardless of
> current discussion.
>
> On Db845c I see:
>
> root@linaro-alip:/sys/bus/soundwire/devices# cat sdw:0:217:2010:0:1/status
> Attached
> root@linaro-alip:/sys/bus/soundwire/devices# cat sdw:0:217:2010:0:2/status
> Attached
looks like we are all aligned on the idea, I have a similar patch to at
https://github.com/thesofproject/linux/pull/2426
The difference is that the sysfs status and device_number is added even
without a driver probe and when there's no firmware description. sysfs
is currently only added after the driver probe, which wouldn't work for
the case Srinivas was trying to deal with.
but the way you dealt the status below is better than the switch case I
used, so will merge this into my code.
Srinivas' patch needs a fix for ACPI platforms, won't probe otherwise
since we don't have an of_node. If that's alright with everyone I can
submit a patchset that gathers the 3 contributions.
>
> diff --git a/drivers/soundwire/sysfs_slave.c b/drivers/soundwire/sysfs_slave.c
> index f510071b0add..3b2765f10024 100644
> --- a/drivers/soundwire/sysfs_slave.c
> +++ b/drivers/soundwire/sysfs_slave.c
> @@ -97,8 +97,27 @@ static ssize_t modalias_show(struct device *dev,
> }
> static DEVICE_ATTR_RO(modalias);
>
> +#define SDW_SLAVE_MAX (SDW_SLAVE_RESERVED + 1)
> +
> +static const char *const slave_status[SDW_SLAVE_MAX] = {
> + [SDW_SLAVE_UNATTACHED] = "UNATTACHED",
> + [SDW_SLAVE_ATTACHED] = "Attached",
> + [SDW_SLAVE_ALERT] = "Alert",
> + [SDW_SLAVE_RESERVED] = "Reserved",
> +};
> +
> +static ssize_t status_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct sdw_slave *slave = dev_to_sdw_dev(dev);
> +
> + return sprintf(buf, "%s\n", slave_status[slave->status]);
> +}
> +static DEVICE_ATTR_RO(status);
> +
> static struct attribute *slave_attrs[] = {
> &dev_attr_modalias.attr,
> + &dev_attr_status.attr,
> NULL,
> };
> ATTRIBUTE_GROUPS(slave);
>
next prev parent reply other threads:[~2020-09-10 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:27 Srinivas Kandagatla
2020-09-09 13:37 ` Pierre-Louis Bossart
2020-09-09 14:09 ` Srinivas Kandagatla
2020-09-09 14:39 ` Pierre-Louis Bossart
2020-09-09 15:54 ` Srinivas Kandagatla
2020-09-09 17:00 ` Pierre-Louis Bossart
2020-09-10 8:56 ` Vinod Koul
2020-09-10 14:02 ` Pierre-Louis Bossart [this message]
2020-09-11 5:38 ` 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=f3880470-cdc4-7b84-97a1-303f9a95d3f4@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--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 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®