From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: ohad@wizery.com, bjorn.andersson@linaro.org
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 3/3] sample: rpmsg: Print out RPMSG device name extension
Date: Mon, 15 Jun 2020 15:38:59 -0600 [thread overview]
Message-ID: <20200615213859.443152-4-mathieu.poirier@linaro.org> (raw)
In-Reply-To: <20200615213859.443152-1-mathieu.poirier@linaro.org>
Use the new rpmsg_device_get_name_extension() API to print the
RPMSG name extension if used by a RPMSG device name.
Suggested-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
---
samples/rpmsg/rpmsg_client_sample.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/samples/rpmsg/rpmsg_client_sample.c b/samples/rpmsg/rpmsg_client_sample.c
index ae5081662283..2c5dc65ed844 100644
--- a/samples/rpmsg/rpmsg_client_sample.c
+++ b/samples/rpmsg/rpmsg_client_sample.c
@@ -51,8 +51,13 @@ static int rpmsg_sample_cb(struct rpmsg_device *rpdev, void *data, int len,
static int rpmsg_sample_probe(struct rpmsg_device *rpdev)
{
int ret;
+ const char *extension;
struct instance_data *idata;
+ extension = rpmsg_device_get_name_extension(rpdev, 1);
+ if (!IS_ERR_OR_NULL(extension))
+ dev_info(&rpdev->dev, "extension: %s\n", extension);
+
dev_info(&rpdev->dev, "new channel: 0x%x -> 0x%x!\n",
rpdev->src, rpdev->dst);
--
2.25.1
prev parent reply other threads:[~2020-06-15 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 21:38 [PATCH v7 0/3] rpmsg: core: Add support for name extension Mathieu Poirier
2020-06-15 21:38 ` [PATCH v7 1/3] rpmsg: core: Add wildcard match for name service Mathieu Poirier
2020-06-15 21:38 ` [PATCH v7 2/3] rpmsg: core: Add support to retrieve name extension Mathieu Poirier
2020-06-15 21:38 ` Mathieu Poirier [this message]
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=20200615213859.443152-4-mathieu.poirier@linaro.org \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).