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
--
To unsubscribe from this list: send the line "unsubscribe linux-remoteproc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
