Thread (14 messages) 14 messages, 4 authors, 2020-03-06

RE: [PATCH V4 2/2] firmware: arm_scmi: add smc/hvc transport

From: Peng Fan <peng.fan@nxp.com>
Date: 2020-03-06 08:07:25
Also in: linux-devicetree, lkml

Subject: Re: [PATCH V4 2/2] firmware: arm_scmi: add smc/hvc transport

On 3/5/20 8:06 AM, Sudeep Holla wrote:
quoted
On Thu, Mar 05, 2020 at 11:25:35AM +0000, Peng Fan wrote:

[...]
quoted
quoted
Yes, this may fix the issue. However I would like to know if we need
to support multiple channels/shared memory simultaneously. It is
fair requirement and may need some work which should be fine.
Do you have any suggestions? Currently I have not worked out an good
solution.
TBH, I haven't given it a much thought. I would like to know if people
are happy with just one SMC channel for SCMI or do they need more ?
If they need it, we can try to solve it. Otherwise, what you have will
suffice IMO.
On our platforms we have one channel/shared memory area/mailbox
instance for all standard SCMI protocols, and we have a separate
channel/shared memory area/mailbox driver instance for a proprietary one.
They happen to have difference throughput requirements, hence the split.

If I read Peng's submission correctly, it seems to me that the usage model
described before is still fine.
Thanks. 

Sudeep,

Then should I repost with the global mutex added?

Thanks,
Peng.

--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help