From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Vinod Koul <vkoul@kernel.org>
Cc: gregkh@linuxfoundation.org, alsa-devel@alsa-project.org,
yung-chuan.liao@linux.intel.com, linux-kernel@vger.kernel.org,
sanyog.r.kale@intel.com
Subject: Re: [PATCH] soundwire: debugfs: use controller id instead of link_id
Date: Thu, 21 Jan 2021 09:12:07 -0600 [thread overview]
Message-ID: <33fe8455-01b4-f867-4974-a3e867c930f0@linux.intel.com> (raw)
In-Reply-To: <1fad2388-27d0-7014-818d-1272fa70ed9b@linaro.org>
On 1/21/21 6:03 AM, Srinivas Kandagatla wrote:
>
>
> On 19/01/2021 19:09, Pierre-Louis Bossart wrote:
>>
>>> currently we have
>>> /sys/kernel/debug/soundwire/master-*
>>>
>>> Are you suggesting that we have something like this:
>>>
>>> /sys/kernel/debug/soundwire/xyz-controller/master-<LINK-ID> ??
>>
>> Yes this is what I was thinking about.
>
> Vinod/Pierre,
>
> One Question here,
>
> Why is link_id part of "struct sdw_bus", should it not be part of
> "struct sdw_master_device " ?
>
> Given that "There is one Link per each Master"
it's true that link == master == bus at the concept level.
but we have an existing code base with different structures and we can't
break too many things at once.
In the existing flow, the 'bus' is created and setup first, the
sdw_bus_master_add() routine takes a 'bus' argument, and the link_id is
already set. This routine only creates a device and in the rest of the
code we keep using the 'bus' pointer, so there's no real short-term
scope for moving the information into the 'sdw_master_device' structure
- that would be a lot of surgery when nothing is really broken.
next prev parent reply other threads:[~2021-01-21 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 16:25 [PATCH] soundwire: debugfs: use controller id instead of link_id Srinivas Kandagatla
2021-01-19 14:52 ` Vinod Koul
2021-01-19 15:54 ` Pierre-Louis Bossart
2021-01-19 17:17 ` Srinivas Kandagatla
2021-01-19 19:09 ` Pierre-Louis Bossart
2021-01-21 12:03 ` Srinivas Kandagatla
2021-01-21 15:12 ` Pierre-Louis Bossart [this message]
2021-01-21 17:23 ` Srinivas Kandagatla
2021-01-21 18:22 ` Pierre-Louis Bossart
2021-02-01 10:14 ` Vinod Koul
2021-02-01 16:10 ` Pierre-Louis Bossart
2021-02-02 4:18 ` Vinod Koul
2021-02-02 16:43 ` Pierre-Louis Bossart
2021-02-03 11:14 ` Vinod Koul
2021-02-06 10:22 ` 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=33fe8455-01b4-f867-4974-a3e867c930f0@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).