All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: peng.fan@nxp.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	f.fainelli@gmail.com, viresh.kumar@linaro.org,
	linux-kernel@vger.kernel.org, andre.przywara@arm.com,
	linux-imx@nxp.com, sudeep.holla@arm.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transports
Date: Thu, 6 Feb 2020 14:59:47 -0700	[thread overview]
Message-ID: <20200206215947.GA21514@bogus> (raw)
In-Reply-To: <1580994086-17850-2-git-send-email-peng.fan@nxp.com>

On Thu, Feb 06, 2020 at 09:01:25PM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> SCMI could use SMC/HVC as tranports, so add into devicetree
> binding doc.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  Documentation/devicetree/bindings/arm/arm,scmi.txt | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/arm/arm,scmi.txt b/Documentation/devicetree/bindings/arm/arm,scmi.txt
> index f493d69e6194..03cff8b55a93 100644
> --- a/Documentation/devicetree/bindings/arm/arm,scmi.txt
> +++ b/Documentation/devicetree/bindings/arm/arm,scmi.txt
> @@ -14,7 +14,7 @@ Required properties:
>  
>  The scmi node with the following properties shall be under the /firmware/ node.
>  
> -- compatible : shall be "arm,scmi"
> +- compatible : shall be "arm,scmi" or "arm,scmi-smc"
>  - mboxes: List of phandle and mailbox channel specifiers. It should contain
>  	  exactly one or two mailboxes, one for transmitting messages("tx")
>  	  and another optional for receiving the notifications("rx") if
> @@ -25,6 +25,8 @@ The scmi node with the following properties shall be under the /firmware/ node.
>  	  protocol identifier for a given sub-node.
>  - #size-cells : should be '0' as 'reg' property doesn't have any size
>  	  associated with it.
> +- arm,smc-id : SMC id required when using smc transports
> +- arm,hvc-id : HVC id required when using hvc transports

Don't the SMC ids get standardized?

>  
>  Optional properties:
>  
> -- 
> 2.16.4
> 

_______________________________________________
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, mark.rutland@arm.com,
	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,
	andre.przywara@arm.com
Subject: Re: [PATCH 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transports
Date: Thu, 6 Feb 2020 14:59:47 -0700	[thread overview]
Message-ID: <20200206215947.GA21514@bogus> (raw)
In-Reply-To: <1580994086-17850-2-git-send-email-peng.fan@nxp.com>

On Thu, Feb 06, 2020 at 09:01:25PM +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> SCMI could use SMC/HVC as tranports, so add into devicetree
> binding doc.
> 
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
>  Documentation/devicetree/bindings/arm/arm,scmi.txt | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/arm/arm,scmi.txt b/Documentation/devicetree/bindings/arm/arm,scmi.txt
> index f493d69e6194..03cff8b55a93 100644
> --- a/Documentation/devicetree/bindings/arm/arm,scmi.txt
> +++ b/Documentation/devicetree/bindings/arm/arm,scmi.txt
> @@ -14,7 +14,7 @@ Required properties:
>  
>  The scmi node with the following properties shall be under the /firmware/ node.
>  
> -- compatible : shall be "arm,scmi"
> +- compatible : shall be "arm,scmi" or "arm,scmi-smc"
>  - mboxes: List of phandle and mailbox channel specifiers. It should contain
>  	  exactly one or two mailboxes, one for transmitting messages("tx")
>  	  and another optional for receiving the notifications("rx") if
> @@ -25,6 +25,8 @@ The scmi node with the following properties shall be under the /firmware/ node.
>  	  protocol identifier for a given sub-node.
>  - #size-cells : should be '0' as 'reg' property doesn't have any size
>  	  associated with it.
> +- arm,smc-id : SMC id required when using smc transports
> +- arm,hvc-id : HVC id required when using hvc transports

Don't the SMC ids get standardized?

>  
>  Optional properties:
>  
> -- 
> 2.16.4
> 

  reply	other threads:[~2020-02-06 22:00 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 13:01 [PATCH 0/2] firmware: arm_scmi: add smc/hvc transports support peng.fan
2020-02-06 13:01 ` peng.fan
2020-02-06 13:01 ` [PATCH 1/2] dt-bindings: arm: arm,scmi: add smc/hvc transports peng.fan
2020-02-06 13:01   ` peng.fan
2020-02-06 21:59   ` Rob Herring [this message]
2020-02-06 21:59     ` Rob Herring
2020-02-07  8:10     ` Peng Fan
2020-02-07  8:10       ` Peng Fan
2020-02-07 10:56     ` Sudeep Holla
2020-02-07 10:56       ` Sudeep Holla
2020-02-07 10:08   ` Marc Zyngier
2020-02-07 10:08     ` Marc Zyngier
2020-02-07 10:47     ` Sudeep Holla
2020-02-07 10:47       ` Sudeep Holla
2020-02-07 10:55       ` Marc Zyngier
2020-02-07 10:55         ` Marc Zyngier
2020-02-07 11:00         ` Peng Fan
2020-02-07 11:00           ` Peng Fan
2020-02-07 11:09           ` Marc Zyngier
2020-02-07 11:09             ` Marc Zyngier
2020-02-07 11:32             ` Sudeep Holla
2020-02-07 11:32               ` Sudeep Holla
2020-02-07 11:46               ` Peng Fan
2020-02-07 11:46                 ` Peng Fan
2020-02-07 10:55       ` Peng Fan
2020-02-07 10:55         ` Peng Fan
2020-02-07 11:01         ` Marc Zyngier
2020-02-07 11:01           ` Marc Zyngier
2020-02-07 11:06         ` Sudeep Holla
2020-02-07 11:06           ` Sudeep Holla
2020-02-07 11:19           ` Peng Fan
2020-02-07 11:19             ` Peng Fan
2020-02-10  0:59   ` Peng Fan
2020-02-10  0:59     ` Peng Fan
2020-02-11 12:02     ` Sudeep Holla
2020-02-11 12:02       ` Sudeep Holla
2020-02-06 13:01 ` [PATCH 2/2] firmware: arm_scmi: " peng.fan
2020-02-06 13:01   ` 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=20200206215947.GA21514@bogus \
    --to=robh@kernel.org \
    --cc=andre.przywara@arm.com \
    --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=mark.rutland@arm.com \
    --cc=peng.fan@nxp.com \
    --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.