From: Stephan Gerhold <stephan@gerhold.net>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: Loic Poulain <loic.poulain@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Aleksander Morgado <aleksander@aleksander.es>,
Sergey Ryazanov <ryazanov.s.a@gmail.com>,
Johannes Berg <johannes.berg@intel.com>,
Leon Romanovsky <leon@kernel.org>,
M Chetan Kumar <m.chetan.kumar@intel.com>,
linuxwwan@intel.com, Ohad Ben-Cohen <ohad@wizery.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
netdev@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Stephan Gerhold <stephan@gerhold.net>
Subject: [PATCH net-next v2 1/3] rpmsg: core: Add driver_data for rpmsg_device_id
Date: Fri, 18 Jun 2021 09:52:41 +0200 [thread overview]
Message-ID: <20210618075243.42046-2-stephan@gerhold.net> (raw)
In-Reply-To: <20210618075243.42046-1-stephan@gerhold.net>
Most device_id structs provide a driver_data field that can be used
by drivers to associate data more easily for a particular device ID.
Add the same for the rpmsg_device_id.
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
---
Changes in v2: None
---
drivers/rpmsg/rpmsg_core.c | 4 +++-
include/linux/mod_devicetable.h | 1 +
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
index e5daee4f9373..c1404d3dae2c 100644
--- a/drivers/rpmsg/rpmsg_core.c
+++ b/drivers/rpmsg/rpmsg_core.c
@@ -459,8 +459,10 @@ static int rpmsg_dev_match(struct device *dev, struct device_driver *drv)
if (ids)
for (i = 0; ids[i].name[0]; i++)
- if (rpmsg_id_match(rpdev, &ids[i]))
+ if (rpmsg_id_match(rpdev, &ids[i])) {
+ rpdev->id.driver_data = ids[i].driver_data;
return 1;
+ }
return of_driver_match_device(dev, drv);
}
diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
index 7d45b5f989b0..8e291cfdaf06 100644
--- a/include/linux/mod_devicetable.h
+++ b/include/linux/mod_devicetable.h
@@ -447,6 +447,7 @@ struct hv_vmbus_device_id {
struct rpmsg_device_id {
char name[RPMSG_NAME_SIZE];
+ kernel_ulong_t driver_data;
};
/* i2c */
--
2.32.0
next prev parent reply other threads:[~2021-06-18 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 7:52 [PATCH net-next v2 0/3] net: wwan: Add RPMSG WWAN CTRL driver Stephan Gerhold
2021-06-18 7:52 ` Stephan Gerhold [this message]
2021-06-18 7:52 ` [PATCH net-next v2 2/3] " Stephan Gerhold
2021-06-18 8:21 ` Aleksander Morgado
2021-06-18 10:13 ` Stephan Gerhold
2021-06-18 12:24 ` Aleksander Morgado
2021-06-18 7:52 ` [PATCH net-next v2 3/3] net: wwan: Allow WWAN drivers to provide blocking tx and poll function Stephan Gerhold
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=20210618075243.42046-2-stephan@gerhold.net \
--to=stephan@gerhold.net \
--cc=aleksander@aleksander.es \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=m.chetan.kumar@intel.com \
--cc=mathieu.poirier@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=phone-devel@vger.kernel.org \
--cc=ryazanov.s.a@gmail.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).