linux-kernel - Re: [PATCH V3 2/2] firmware: arm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 28 Feb 2020 16:18:20 +0000
From:   Sudeep Holla <sudeep.holla@....com>
To:     peng.fan@....com
Cc:     robh+dt@...nel.org, mark.rutland@....com, robh@...nel.org,
        viresh.kumar@...aro.org, f.fainelli@...il.com, linux-imx@....com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, andre.przywara@....com,
        Sudeep Holla <sudeep.holla@....com>
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@....com wrote:
> From: Peng Fan <peng.fan@....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.

-- 
Regards,
Sudeep