All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: peng.fan@nxp.com
Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	f.fainelli@gmail.com, viresh.kumar@linaro.org,
	linux-kernel@vger.kernel.org, robh+dt@kernel.org,
	linux-imx@nxp.com, sudeep.holla@arm.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V4 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport
Date: Wed, 4 Mar 2020 10:31:41 -0600	[thread overview]
Message-ID: <20200304163141.GA16460@bogus> (raw)
In-Reply-To: <1583201219-15839-2-git-send-email-peng.fan@nxp.com>

On Tue,  3 Mar 2020 10:06:58 +0800, 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
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  Documentation/devicetree/bindings/arm/arm,scmi.txt | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

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

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: peng.fan@nxp.com
Cc: sudeep.holla@arm.com, robh+dt@kernel.org,
	viresh.kumar@linaro.org, f.fainelli@gmail.com, linux-imx@nxp.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V4 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport
Date: Wed, 4 Mar 2020 10:31:41 -0600	[thread overview]
Message-ID: <20200304163141.GA16460@bogus> (raw)
In-Reply-To: <1583201219-15839-2-git-send-email-peng.fan@nxp.com>

On Tue,  3 Mar 2020 10:06:58 +0800, 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
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  Documentation/devicetree/bindings/arm/arm,scmi.txt | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2020-03-04 16:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03  2:06 [PATCH V4 0/2] firmware: arm_scmi: add smc/hvc transports support peng.fan
2020-03-03  2:06 ` peng.fan
2020-03-03  2:06 ` [PATCH V4 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transport peng.fan
2020-03-03  2:06   ` peng.fan
2020-03-04 16:31   ` Rob Herring [this message]
2020-03-04 16:31     ` Rob Herring
2020-03-03  2:06 ` [PATCH V4 2/2] firmware: arm_scmi: " peng.fan
2020-03-03  2:06   ` peng.fan
2020-03-04 10:40   ` Sudeep Holla
2020-03-04 10:40     ` Sudeep Holla
2020-03-04 12:49     ` Peng Fan
2020-03-04 12:49       ` Peng Fan
2020-03-04 14:16       ` Peng Fan
2020-03-04 14:16         ` Peng Fan
2020-03-04 17:03         ` Sudeep Holla
2020-03-04 17:03           ` Sudeep Holla
2020-03-05 11:25           ` Peng Fan
2020-03-05 11:25             ` Peng Fan
2020-03-05 16:06             ` Sudeep Holla
2020-03-05 16:06               ` Sudeep Holla
2020-03-05 17:27               ` Florian Fainelli
2020-03-05 17:27                 ` Florian Fainelli
2020-03-06  8:07                 ` Peng Fan
2020-03-06  8:07                   ` Peng Fan
2020-03-06 14:23                   ` Sudeep Holla
2020-03-06 14:23                     ` Sudeep Holla
2020-03-06 18:08                     ` Florian Fainelli
2020-03-06 18:08                       ` Florian Fainelli

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=20200304163141.GA16460@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.