From: Sudeep Holla <sudeep.holla@arm•com>
To: peng.fan@nxp•com
Cc: mark.rutland@arm•com, robh@kernel•org, f.fainelli@gmail•com,
devicetree@vger•kernel.org, viresh.kumar@linaro•org,
Sudeep Holla <sudeep.holla@arm•com>,
linux-kernel@vger•kernel.org, robh+dt@kernel•org,
linux-imx@nxp•com, andre.przywara@arm•com,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH V3 2/2] firmware: arm_scmi: add smc/hvc transport
Date: Fri, 28 Feb 2020 16:18:20 +0000 [thread overview]
Message-ID: <20200228161820.GA17229@bogus> (raw)
In-Reply-To: <1582701171-26842-3-git-send-email-peng.fan@nxp.com>
On Wed, Feb 26, 2020 at 03:12:51PM +0800, peng.fan@nxp•com wrote:
> 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.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-28 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 7:12 [PATCH V3 0/2] firmware: arm_scmi: add smc/hvc transports support peng.fan
2020-02-26 7:12 ` [PATCH V3 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport peng.fan
2020-02-26 7:12 ` [PATCH V3 2/2] firmware: arm_scmi: " peng.fan
2020-02-28 16:18 ` Sudeep Holla [this message]
2020-02-29 2:07 ` Peng Fan
2020-03-02 11:21 ` Sudeep Holla
2020-03-02 13:40 ` Peng Fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200228161820.GA17229@bogus \
--to=sudeep.holla@arm$(echo .)com \
--cc=andre.przywara@arm$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=f.fainelli@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=peng.fan@nxp$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
--cc=robh@kernel$(echo .)org \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox