[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c675ea60-5bfa-2475-8878-c589b8d20b32@linux.intel.com>
Date: Mon, 6 May 2019 09:42:35 -0500
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: alsa-devel@...a-project.org, tiwai@...e.de,
linux-kernel@...r.kernel.org, liam.r.girdwood@...ux.intel.com,
vkoul@...nel.org, broonie@...nel.org,
srinivas.kandagatla@...aro.org, jank@...ence.com, joe@...ches.com,
Sanyog Kale <sanyog.r.kale@...el.com>
Subject: Re: [alsa-devel] [RFC PATCH 2/7] soundwire: add Slave sysfs support
>> +static struct attribute_group sdw_slave_dev_attr_group = {
>> + .attrs = slave_dev_attrs,
>> +};
>> +
>> +const struct attribute_group *sdw_slave_dev_attr_groups[] = {
>> + &sdw_slave_dev_attr_group,
>> + NULL
>> +};
>
> ATTRIBUTE_GROUP()?
yes.
>
>
>> +
>> +int sdw_sysfs_slave_init(struct sdw_slave *slave)
>> +{
>> + struct sdw_slave_sysfs *sysfs;
>> + unsigned int src_dpns, sink_dpns, i, j;
>> + int err;
>> +
>> + if (slave->sysfs) {
>> + dev_err(&slave->dev, "SDW Slave sysfs is already initialized\n");
>> + err = -EIO;
>> + goto err_ret;
>> + }
>> +
>> + sysfs = kzalloc(sizeof(*sysfs), GFP_KERNEL);
>
> Same question as patch 1, why a new device?
yes it's the same open. In this case, the slave devices are defined at a
different level so it's also confusing to create a device to represent
the slave properties. The code works but I am not sure the initial
directions are correct.
Powered by blists - more mailing lists