From: Florian Fainelli <f.fainelli@gmail.com>
To: peng.fan@nxp.com, sudeep.holla@arm.com, robh+dt@kernel.org
Cc: viresh.kumar@linaro.org, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V5 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport
Date: Sun, 8 Mar 2020 09:43:44 -0700 [thread overview]
Message-ID: <28538d48-ef20-49f1-2882-9e5592c1352c@gmail.com> (raw)
In-Reply-To: <1583673879-20714-2-git-send-email-peng.fan@nxp.com>
On 3/8/2020 6:24 AM, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> SCMI could use SMC/HVC as tranports. Since there is no
> standardized id, we need to use vendor specific id. So
> add into devicetree binding doc.
>
> Also add arm,scmi-smc compatible string for smc/hvc transport
>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2020-03-08 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 13:24 [PATCH V5 0/2] firmware: arm_scmi: add smc/hvc transports support peng.fan
2020-03-08 13:24 ` [PATCH V5 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport peng.fan
2020-03-08 16:43 ` Florian Fainelli [this message]
2020-03-08 13:24 ` [PATCH V5 2/2] firmware: arm_scmi: " peng.fan
2020-03-20 8:27 ` [PATCH V5 0/2] firmware: arm_scmi: add smc/hvc transports support Peng Fan
2020-03-20 8:37 ` Sudeep Holla
2020-03-20 8:40 ` Peng Fan
2020-03-27 16:32 ` Sudeep Holla
2020-03-30 14:05 ` Sudeep Holla
2020-04-15 10:58 ` [PATCH V5 2/2] firmware: arm_scmi: add smc/hvc transport Etienne Carriere
2020-04-15 13:16 ` Sudeep Holla
2020-04-15 14:15 ` Etienne Carriere
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=28538d48-ef20-49f1-2882-9e5592c1352c@gmail.com \
--to=f.fainelli@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).