public inbox for linux-remoteproc@vger.kernel.org
 help / color / mirror / Atom feed
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 2/6] dt-bindings: remoteproc: add system resource manager (SRM)
Date: Wed, 13 Dec 2017 21:59:04 -0800	[thread overview]
Message-ID: <20171214055904.GQ17344@builder> (raw)
In-Reply-To: <1511534202-12995-3-git-send-email-arnaud.pouliquen@st.com>

On Fri 24 Nov 06:36 PST 2017, Arnaud Pouliquen wrote:

> +Example:
> +	system_resources {
> +		compatible = "rproc-srm-core";
> +
> +		mmc0: sdhci@09060000 {
> +			compatible = "rproc-srm-dev";
> +			pinctrl-names = "default", "idle";
> +			pinctrl-0 = <&pinctrl_mmc0>;
> +			pinctrl-1 = <&pinctrl_mmc1>;
> +			clock-names = "mmc", "icn";
> +			clocks = <&clk_s_c0_flexgen CLK_MMC_0>,
> +				 <&clk_s_c0_flexgen CLK_RX_ICN_HVA>;
> +			vdda-supply = <&vdda>;
> +		};
> +	};

>From a DT perspective these properties are all on the remoteproc. This
has the additional benefit of making the dynamic case much saner to
implement. I.e. if you have:

acme_rproc {
	compatible = "acme,rproc";

	clock-names = "ddr", "mmc";
	clocks = <&clocker DDR>, <&clocker MMC>;
};

Then you can declare statically in the acme,rproc that the "ddr" clock
should be enabled between boot and shutdown, or we can do this based on
resource table information, and you can easily acquire a handle to this
clock from a rpmsg device acting as dynamic controller of resources.

Regards,
Bjorn

  reply	other threads:[~2017-12-14  5:59 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 [this message]
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
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=20171214055904.GQ17344@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