From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>, Vinod Koul <vkoul@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
hui.wang@canonical.com, srinivas.kandagatla@linaro.org,
sanyog.r.kale@intel.com,
Bard Liao <yung-chuan.liao@linux.intel.com>,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH] soundwire: intel: move to auxiliary bus
Date: Tue, 23 Mar 2021 12:29:48 -0500 [thread overview]
Message-ID: <aa9cfc49-913e-b3ba-1d92-2fab55bf4fa7@linux.intel.com> (raw)
In-Reply-To: <YFma1ClahDe2bZhR@kroah.com>
Thanks Greg and Vinod for the reviews
>>> -static int intel_master_probe(struct platform_device *pdev)
>>> +static int intel_link_probe(struct auxiliary_device *auxdev, const struct auxiliary_device_id *id)
>>> {
>>> - struct device *dev = &pdev->dev;
>>> + struct device *dev = &auxdev->dev;
>>> + struct sdw_intel_link_dev *ldev = auxiliary_dev_to_sdw_intel_link_dev(auxdev);
>>
>> Do we need another abstractions for resources here, why not aux dev
>> creation set the resources required and we skip this step...
Not sure what resources you are referring to?
this is just a container_of() and the documented way of extending the
auxbus (see
https://www.kernel.org/doc/html/latest/driver-api/auxiliary_bus.html#example-usage)
struct sdw_intel_link_dev {
struct auxiliary_device auxdev;
struct sdw_intel_link_res link_res;
};
#define auxiliary_dev_to_sdw_intel_link_dev(auxiliary_dev) \
container_of(auxiliary_dev, struct sdw_intel_link_dev, auxdev)
>>> struct sdw_intel *sdw;
>>> struct sdw_cdns *cdns;
>>> struct sdw_bus *bus;
>>> @@ -1346,14 +1347,14 @@ static int intel_master_probe(struct platform_device *pdev)
>>> cdns = &sdw->cdns;
>>> bus = &cdns->bus;
>>>
>>> - sdw->instance = pdev->id;
>>> - sdw->link_res = dev_get_platdata(dev);
>>> + sdw->instance = auxdev->id;
>>
>> so auxdev has id and still we pass id as argument :( Not sure if folks
>> can fix this now
>
> That's odd, yeah, it should be fixed.
I think we are talking about different things?
this is defined in mod_devicetable.h:
struct auxiliary_device_id {
char name[AUXILIARY_NAME_SIZE];
kernel_ulong_t driver_data;
};
and used for the driver probe:
ret = auxdrv->probe(auxdev, auxiliary_match_id(auxdrv->id_table, auxdev));
but there is a separate id:
struct auxiliary_device {
struct device dev;
const char *name;
u32 id;
};
which is set during the device initialization in intel_init.c
/* we don't use an IDA since we already have a link ID */
auxdev->id = link_id;
In the auxiliary bus design, the parent has to take care of managing
this id, be it with an IDA or as we do here with a physical link ID that
is unique.
in short, I don't see how I could change the code given the differences
in concepts?
next prev parent reply other threads:[~2021-03-23 17:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 0:43 [PATCH] soundwire: intel: move to auxiliary bus Bard Liao
2021-03-23 0:43 ` Bard Liao
2021-03-23 6:48 ` Vinod Koul
2021-03-23 6:48 ` Vinod Koul
2021-03-23 7:37 ` Greg KH
2021-03-23 7:37 ` Greg KH
2021-03-23 17:29 ` Pierre-Louis Bossart [this message]
2021-03-24 10:50 ` Vinod Koul
2021-03-24 10:50 ` Vinod Koul
2021-03-24 15:03 ` Pierre-Louis Bossart
2021-03-23 7:37 ` Greg KH
2021-03-23 7:37 ` Greg KH
2021-03-23 18:04 ` Pierre-Louis Bossart
2021-03-23 18:04 ` Pierre-Louis Bossart
2021-03-23 18:32 ` Greg KH
2021-03-23 18:32 ` Greg KH
2021-03-23 19:14 ` Pierre-Louis Bossart
2021-03-24 9:30 ` Greg KH
2021-03-24 14:55 ` Pierre-Louis Bossart
2021-03-24 15:36 ` Greg KH
2021-03-26 16:24 ` Pierre-Louis Bossart
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=aa9cfc49-913e-b3ba-1d92-2fab55bf4fa7@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rander.wang@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.