From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] rpmsg: core: export rpmsg bus type
Date: Fri, 2 Mar 2018 15:25:27 +0000 [thread overview]
Message-ID: <96ca6e59-071d-4eca-704f-8bb646f072dd@arm.com> (raw)
In-Reply-To: <20180302145531.20463-2-srinivas.kandagatla@linaro.org>
On 02/03/18 14:55, srinivas.kandagatla at linaro.org wrote:
> From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>
> Export rpmsg bus type so that iommu drivers iommu ops to
> rpmsg bus type.
>
> On Qualcomm SoCs ADSP exposes functions like audio and
> other which need iommu access, as these drivers are part
> of rpmsg bus, able to allocate memory from iommus is basic
> requirement. So expose this bus so that iommu drivers can
> add ops to this.
IOMMU drivers are built-in while rpmsg can be built as a module, so that
isn't always going to work.
Robin.
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> ---
> drivers/rpmsg/rpmsg_core.c | 3 ++-
> include/linux/rpmsg.h | 2 +-
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
> index 5a081762afcc..e84c71f8d6ab 100644
> --- a/drivers/rpmsg/rpmsg_core.c
> +++ b/drivers/rpmsg/rpmsg_core.c
> @@ -465,7 +465,7 @@ static int rpmsg_dev_remove(struct device *dev)
> return err;
> }
>
> -static struct bus_type rpmsg_bus = {
> +struct bus_type rpmsg_bus = {
> .name = "rpmsg",
> .match = rpmsg_dev_match,
> .dev_groups = rpmsg_dev_groups,
> @@ -473,6 +473,7 @@ static struct bus_type rpmsg_bus = {
> .probe = rpmsg_dev_probe,
> .remove = rpmsg_dev_remove,
> };
> +EXPORT_SYMBOL(rpmsg_bus);
>
> int rpmsg_register_device(struct rpmsg_device *rpdev)
> {
> diff --git a/include/linux/rpmsg.h b/include/linux/rpmsg.h
> index ca07366c4c33..869e5946b7df 100644
> --- a/include/linux/rpmsg.h
> +++ b/include/linux/rpmsg.h
> @@ -49,7 +49,7 @@ struct rpmsg_device;
> struct rpmsg_endpoint;
> struct rpmsg_device_ops;
> struct rpmsg_endpoint_ops;
> -
> +extern struct bus_type rpmsg_bus;
> /**
> * struct rpmsg_channel_info - channel info representation
> * @name: name of service
>
next prev parent reply other threads:[~2018-03-02 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 14:55 [PATCH 0/3] drivers: rpmsg: make rpmsg bus DMA capable srinivas.kandagatla at linaro.org
2018-03-02 14:55 ` [PATCH 1/3] rpmsg: core: export rpmsg bus type srinivas.kandagatla at linaro.org
2018-03-02 15:25 ` Robin Murphy [this message]
2018-03-02 14:55 ` [PATCH 2/3] rpmsg: core: make rpmsg bus DMA capable srinivas.kandagatla at linaro.org
2018-03-02 16:14 ` Robin Murphy
2018-03-02 16:40 ` Srinivas Kandagatla
2018-03-18 22:47 ` Bjorn Andersson
2018-03-02 14:55 ` [PATCH 3/3] iommu: armsmmu: set iommu ops for rpmsg bus srinivas.kandagatla at linaro.org
2018-03-02 16:59 ` Robin Murphy
2018-05-07 19:28 ` Bjorn Andersson
2018-05-11 18:24 ` Robin Murphy
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=96ca6e59-071d-4eca-704f-8bb646f072dd@arm.com \
--to=robin.murphy@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).