On Wed, Jul 5, 2017 at 11:32 PM, Sudeep Holla <sudeep.holla@xxxxxxx> wrote:
>
> I have posted the SCMI patches now[1],
>
I wish I was CC'ed on that. Now LKML seems too busy to forward it.
> please let me know how to get
> both SCPI and SCMI working together with different doorbell bits on the
> same channel.
>
You say in the cover letter :
"Let me begin admitting that we are introducing yet another protocol to
achieve same things as many existing protocols like ARM SCPI, TI SCI,
QCOM RPM, Nvidia Tegra BPMP, and so on"
So SCMI is supposed to replace SCPI, SCI, RPM and BPMP or SCMI is
to be used for future platforms.
If SCPI and SCMI achieve the same, why have them both active simultaneously?
Assuming there really is some sane excuse :-
SCPI and SCMI are two separate client working over an MHU channel.
So, as is the case with users relying on a common resource, you need a
shim arbitrator that serialises access to the resource.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
