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

On Sat, Feb 29, 2020 at 02:07:30AM +0000, Peng Fan wrote:

quoted

Hi Sudeep,

quoted

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

On Wed, Feb 26, 2020 at 03:12:51PM +0800, peng.fan@nxp.com wrote:

quoted

From: Peng Fan <peng.fan@nxp.com>

Take arm,smc-id as the 1st arg, and protocol id as the 2nd arg
when issuing SMC/HVC. Since we need protocol id, so add this
parameter

And why do we need protocol id here ? I couldn't find it out myself.
I would like to know why/what/how is it used in the firmware(smc/hvc
handler). I hope you are not mixing the need for multiple channel
with protocol id ? One can find out id from the command itself, no
need to pass it and hence asking here for more details.

When each protocol needs its own shmem area, we need let firmware know
which shmem area to parse the message from. Without protocol id,
firmware not know which shmem area should use. Hope this is clear.

Not all platforms need to have a separate shmem for each protocol. Make it it
separate transport.

I added that in case somebody needs it, but actually my platform not need it.
I'll remove the protocol id change in v4. If others need it in future, they
could add then.

Thanks,
Peng.

--
Regards,
Sudeep

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.infr
adead.org%2Fmailman%2Flistinfo%2Flinux-arm-kernel&data=02%7C01
%7Cpeng.fan%40nxp.com%7Ca9c9201db90749d46cfd08d7be9be1a2%7C686
ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637187449022127405&a
mp;sdata=mwxo5a%2F4jW5ram7%2BRyHpjJ6N9ngPn5SoT4L4uq1tJ44%3D&a
mp;reserved=0

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel