public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Shawn Guo <shawn.guo@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 1/1] arm64: dt: poplar: add optee node
Date: Fri, 18 Jan 2019 09:02:32 +0800	[thread overview]
Message-ID: <20190118010230.GB9575@dragon> (raw)
In-Reply-To: <1547735860-5298-1-git-send-email-igor.opaniuk@linaro.org>

Hi Igor,

On Thu, Jan 17, 2019 at 04:37:40PM +0200, Igor Opaniuk wrote:
> As Poplar supports running TF-A with OP-TEE as BL32
> payload, add op-tee node in DT, which enables usage of
> OP-TEE driver (which provides an interface for requesting services
> from OP-TEE).
> 
> Signed-off-by: Igor Opaniuk <igor.opaniuk@linaro.org>

I'm fine with the change.  But rather than pushing changes to u-boot,
can you please push it to kernel repository, which is the DTS upstream
right now?  We sync DTS changes from kernel when needed, and only
maintains u-boot specific changes in hi3798cv200-u-boot.dtsi.

Shawn

> ---
>  arch/arm/dts/hi3798cv200-poplar.dts | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/arch/arm/dts/hi3798cv200-poplar.dts b/arch/arm/dts/hi3798cv200-poplar.dts
> index 964326e..6bc2a23 100644
> --- a/arch/arm/dts/hi3798cv200-poplar.dts
> +++ b/arch/arm/dts/hi3798cv200-poplar.dts
> @@ -28,6 +28,13 @@
>  		reg = <0x0 0x0 0x0 0x80000000>;
>  	};
>  
> +	firmware {
> +		optee {
> +			compatible = "linaro,optee-tz";
> +			method = "smc";
> +		};
> +	};
> +
>  	leds {
>  		compatible = "gpio-leds";
>  
> -- 
> 2.7.4
> 

  reply	other threads:[~2019-01-18  1:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 14:37 [U-Boot] [PATCH v1 1/1] arm64: dt: poplar: add optee node Igor Opaniuk
2019-01-18  1:02 ` Shawn Guo [this message]
2019-01-18 17:38 ` Simon Glass
2019-01-27  3:52 ` [U-Boot] [U-Boot,v1,1/1] " Tom Rini

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=20190118010230.GB9575@dragon \
    --to=shawn.guo@linaro.org \
    --cc=u-boot@lists.denx.de \
    /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