From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>
Cc: linux-remoteproc@vger.kernel.org,
Loic PALLARDY <loic.pallardy@st.com>,
Fabien DESSENNE <fabien.dessenne@st.com>,
Suman Anna <s-anna@ti.com>
Subject: Re: [RFC 5/6] remoteproc: Add posibility to probe a sub device.
Date: Wed, 13 Dec 2017 22:24:22 -0800 [thread overview]
Message-ID: <20171214062422.GT17344@builder> (raw)
In-Reply-To: <1511534202-12995-6-git-send-email-arnaud.pouliquen@st.com>
On Fri 24 Nov 06:36 PST 2017, Arnaud Pouliquen wrote:
> @@ -1343,6 +1344,11 @@ int rproc_add(struct rproc *rproc)
> return ret;
> }
>
> + /* add resource manager device */
> + ret = devm_of_platform_populate(dev->parent);
> + if (ret < 0)
> + return ret;
With the Qualcomm remoteprocs we describe the communication links as
sub-nodes of the remoteproc node to allow binding drivers to channels by
compatible, provide properties to the devices and expose remote services
in DT (e.g. for the purpose of implementing regulators, clocks and other
resources for the system).
I'm surprised this has not been brought up yet for rpmsg, but I assume
it will come at some point, e.g. that we would have something like:
remoteproc {
compatible = "acme,rproc";
vdev0 {
reg = <0>;
acme_clocks: clock-controller {
compatible = "acme,clock-controller";
#clock-cells = <1>;
};
};
};
So blindly creating platform_devices for any subnodes of the remoteproc
node doesn't work for the Qualcomm drivers and won't work if we ever
want to describe something else than a platform driver as a child of any
other remoteproc.
Regards,
Bjorn
next prev parent reply other threads:[~2017-12-14 6:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 14:36 [RFC 0/6] System resource management Arnaud Pouliquen
2017-11-24 14:36 ` [RFC 1/6] remoteproc: add early probed subdevices Arnaud Pouliquen
2017-12-14 6:11 ` Bjorn Andersson
2017-11-24 14:36 ` [RFC 2/6] dt-bindings: remoteproc: add system resource manager (SRM) Arnaud Pouliquen
2017-12-14 5:59 ` Bjorn Andersson
2017-12-21 17:46 ` Arnaud Pouliquen
2017-11-24 14:36 ` [RFC 3/6] remoteproc: add system resource manager core Arnaud Pouliquen
2017-12-14 6:15 ` Bjorn Andersson
2017-11-24 14:36 ` [RFC 4/6] remoteproc: add system resource manager device Arnaud Pouliquen
2017-11-24 14:36 ` [RFC 5/6] remoteproc: Add posibility to probe a sub device Arnaud Pouliquen
2017-12-14 6:24 ` Bjorn Andersson [this message]
2017-11-24 14:36 ` [RFC 6/6] remoteproc: sti: select srm Arnaud Pouliquen
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=20171214062422.GT17344@builder \
--to=bjorn.andersson@linaro.org \
--cc=arnaud.pouliquen@st.com \
--cc=fabien.dessenne@st.com \
--cc=linux-remoteproc@vger.kernel.org \
--cc=loic.pallardy@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;
as well as URLs for NNTP newsgroup(s).