From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: loic pallardy <loic.pallardy@st.com>
Cc: ohad@wizery.com, lee.jones@linaro.org,
linux-remoteproc@vger.kernel.org, kernel@stlinux.com
Subject: Re: [PATCH 1/1] rpmsg: virtio_rpmsg_bus: fix channel creation
Date: Thu, 8 Dec 2016 22:00:28 -0800 [thread overview]
Message-ID: <20161209060028.GX30492@tuxbot> (raw)
In-Reply-To: <ae3b7df2-6fd0-1d48-0e37-bf56af7e637e@st.com>
On Wed 07 Dec 00:42 PST 2016, loic pallardy wrote:
> On 12/06/2016 06:40 PM, Bjorn Andersson wrote:
> >On Mon 05 Dec 00:32 PST 2016, loic pallardy wrote:
[..]
> >And as I said, we use the "id" when creating the device to match with
> >drivers, so I don't see how probing would work with it introduced.
> >
> Change has been introduce here:
> 4dffed5b3ac796bcaf040ca1f64e650f9263363e rpmsg: Name rpmsg devices based on
> channel id
>
> - dev_set_name(&rpdev->dev, "rpmsg%d", rpmsg_dev_index++);
> + dev_set_name(&rpdev->dev, "%s:%s",
> + dev_name(dev->parent), rpdev->id.name);
>
Ok, that makes much more sense.
> Before name was not explicit but unique.
> Now name is clear but not unique. If 2 identical services are announced on
> the same rpmsg link, second will failed.
> Instance number is needed to make it unique.
How about we just add rpdev->src and rpdev->dst in the name as well?
dev_set_name(&rpdev->dev, "%s.%d.%d.%s",
dev_name(dev->parent),
rpdev->src,
rpdev->dst,
rpdev->id.name);
As far as I can see this would be unique over all possible
configurations that we support.
Regards,
Bjorn
next prev parent reply other threads:[~2016-12-09 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 17:54 [PATCH 1/1] rpmsg: virtio_rpmsg_bus: fix channel creation Loic Pallardy
2016-11-29 9:20 ` Lee Jones
2016-12-02 23:19 ` Bjorn Andersson
2016-12-05 8:32 ` loic pallardy
2016-12-06 17:40 ` Bjorn Andersson
2016-12-07 8:42 ` loic pallardy
2016-12-09 6:00 ` Bjorn Andersson [this message]
2016-12-11 20:24 ` loic pallardy
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=20161209060028.GX30492@tuxbot \
--to=bjorn.andersson@linaro.org \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=ohad@wizery.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