Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Loic Pallardy <loic.pallardy@st.com>, Suman Anna <s-anna@ti.com>
Cc: ohad@wizery.com, lee.jones@linaro.org,
	linux-remoteproc@vger.kernel.org, kernel@stlinux.com,
	patrice.chotard@st.com
Subject: Re: [PATCH v2 1/1] rpmsg: virtio_rpmsg_bus: fix channel creation
Date: Mon, 9 Jan 2017 15:45:56 -0800	[thread overview]
Message-ID: <20170109234556.GY10531@minitux> (raw)
In-Reply-To: <20161230195624.GF10531@minitux>

On Fri 30 Dec 11:56 PST 2016, Bjorn Andersson wrote:

> On Tue 27 Dec 14:36 PST 2016, Suman Anna wrote:
> 
> > Hi Loic,
> > 
> > On 12/15/2016 11:09 PM, Bjorn Andersson wrote:
> > > On Thu 15 Dec 06:49 PST 2016, Loic Pallardy wrote:
> > > 
> > >> Since commit 4dffed5b3ac796b ("rpmsg: Name rpmsg devices based on
> > >> channel id"), it is no more possible for a firmware to register twice
> > >> a service (on different endpoints). rpmsg_register_device function
> > >> is failing when calling device_add for the second time as second
> > >> device has the same name as first one already register.
> > >> It is because name is based only on service name and so is not more
> > >> unique. Previously name was unique thanks to the use of rpmsg_dev_index.
> > >>
> > >> This patch adds destination and source endpoint numbers device name to
> > >> create an unique identifier.
> > >>
> > >> Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
> > > 
> > > Looks good, thanks.
> > 
> > Thanks for the patch, I have ran into the exact same issue as well.
> > 
> > > 
> > > Regards,
> > > Bjorn
> > > 
> > >> ---
> > >> v2: Update commit header with commit ID generating regression
> > >> Fix rpmsg_core instead of virtio_rpmsg
> > >>
> > >>  drivers/rpmsg/rpmsg_core.c | 4 ++--
> > >>  1 file changed, 2 insertions(+), 2 deletions(-)
> > >>
> > >> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
> > >> index a79cb5a..18c73e0 100644
> > >> --- a/drivers/rpmsg/rpmsg_core.c
> > >> +++ b/drivers/rpmsg/rpmsg_core.c
> > >> @@ -453,8 +453,8 @@ int rpmsg_register_device(struct rpmsg_device *rpdev)
> > >>  	struct device *dev = &rpdev->dev;
> > >>  	int ret;
> > >>  
> > >> -	dev_set_name(&rpdev->dev, "%s:%s",
> > >> -		     dev_name(dev->parent), rpdev->id.name);
> > >> +	dev_set_name(&rpdev->dev, "%s.%d.%d.%s", dev_name(dev->parent),
> > >> +		     rpdev->src, rpdev->dst, rpdev->id.name);
> > 
> > This is fine, though I would have preferred the numbers at the end after
> > the string literals (%s.%s.%d.%d instead of %s.%d.%d.%s)
> > 
> 
> When using the Qualcomm SMD backend only the name is used to identify
> channels, so I set src & dst to RPMSG_ADDR_ANY. Moving the numbers to
> the end makes this slightly better looking and one could potentially
> trim those without changing the structure of the name.
> 
> 
> Loic, I took the liberty of changing the order and have updated my
> for-next [1] with the following patches:
> 
> a0c10687ec95 Revert "remoteproc: Merge table_ptr and cached_table pointers"
> c81c0e0710f0 remoteproc: fix vdev reference management
> 63447646ac65 rpmsg: virtio_rpmsg_bus: fix channel creation
> 
> 
> I will let them sit there a few days to get some additional build and
> boot test and hope you can give them a spin as well; before I send them
> to Linus.
> 
> [1] https://github.com/andersson/remoteproc/commits/for-next
> 

Loic, did you have a chance to give this a test run? I would appreciate
your feedback before I send this off to Linus.

(The fixed version is part of linux-next as well)

Regards,
Bjorn

  reply	other threads:[~2017-01-09 23:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 14:49 [PATCH v2 1/1] rpmsg: virtio_rpmsg_bus: fix channel creation Loic Pallardy
2016-12-16  5:09 ` Bjorn Andersson
2016-12-27 22:36   ` Suman Anna
2016-12-30 19:56     ` Bjorn Andersson
2017-01-09 23:45       ` Bjorn Andersson [this message]
2017-01-10  0:47         ` Suman Anna
2017-01-11 19:57           ` Bjorn Andersson
2017-01-10  8:18         ` Loic PALLARDY
2017-01-11 22:08           ` Bjorn Andersson
2016-12-16 10:39 ` [STLinux Kernel] " Peter Griffin
2017-01-10  7:51 ` Lee Jones
2017-01-10  8:05   ` Marek Novak

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=20170109234556.GY10531@minitux \
    --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 \
    --cc=patrice.chotard@st.com \
    --cc=s-anna@ti.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