u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: "Sahil Malhotra (OSS)" <sahil.malhotra@oss.nxp.com>
Cc: "ZHIZHIKIN Andrey" <andrey.zhizhikin@leica-geosystems.com>,
	"Clément Faure" <clement.faure@nxp.com>,
	"Gaurav Jain" <gaurav.jain@nxp.com>,
	"Pankaj Gupta" <pankaj.gupta@nxp.com>,
	"Priyanka Jain" <priyanka.jain@nxp.com>,
	u-boot@lists.denx.de, "Varun Sethi" <V.Sethi@nxp.com>,
	"Ye Li" <ye.li@nxp.com>
Subject: Re: [PATCH 1/2] fsl-layerscape: add dtb overlay feature
Date: Mon, 20 Dec 2021 13:52:37 +0100	[thread overview]
Message-ID: <537512dc76cbd87695d93bf7ea419a07@walle.cc> (raw)
In-Reply-To: <DB7PR04MB532247464D9AADF3E4924AFD82719@DB7PR04MB5322.eurprd04.prod.outlook.com>

Hi Sahil,

Am 2021-12-10 07:33, schrieb Sahil Malhotra (OSS):
>> DT nodes can be statically disabled if we know that they are held by 
>> HAB and
>> are not released to NS World.
>> 
>> OP-TEE does set the status itself via dt_enable_secure_status(), which
>> should present the properly configured FDT when U-Boot takes over.
> Yes, OP-TEE set the status by dt_enable_secure_status() in DTB overlay
> which gets merged with DTB provided for Linux bootup and then Linux
> boots with merged DTB.
> But u-boot uses the DTB embedded in its image. How can we modify that
> DTB or merge DTB overlay passed by OP-TEE with uboot DTB ?

But then u-boot has the "wrong" dtb. What is the reason, there is an
overlay instead of a whole dtb? what if the overlay doesn't match
the dtb?

-michael

  parent reply	other threads:[~2021-12-20 12:52 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  6:23 [PATCH 1/2] fsl-layerscape: add dtb overlay feature Sahil Malhotra
2021-11-17  6:23 ` [PATCH 2/2] configs: enabled DTB overlay feature for LS SoCs Sahil Malhotra
2021-11-17  7:53 ` [PATCH 1/2] fsl-layerscape: add dtb overlay feature Michael Walle
2021-11-17 18:11   ` Sahil Malhotra (OSS)
2021-11-17 18:20     ` Michael Walle
2021-11-29 11:55       ` Sahil Malhotra (OSS)
2021-11-29 17:47         ` Michael Walle
2021-12-08  6:12           ` Sahil Malhotra (OSS)
2021-12-08 10:13             ` ZHIZHIKIN Andrey
2021-12-10  6:33               ` Sahil Malhotra (OSS)
2021-12-17  6:19                 ` Sahil Malhotra (OSS)
2021-12-17  7:27                   ` Michael Walle
2021-12-20 12:52                 ` Michael Walle [this message]
2021-12-23  8:46                   ` [EXT] " Sahil Malhotra (OSS)
2021-12-23  9:34                     ` Michael Walle
2021-12-10  7:38           ` François Ozog
  -- strict thread matches above, loose matches on Subject: below --
2022-01-06  6:09 Sahil Malhotra (OSS)
2022-01-06  7:40 ` Michael Walle
2022-02-04 11:27   ` Sahil Malhotra (OSS)
2022-02-24 10:59     ` Sahil Malhotra (OSS)
2022-02-24 12:33       ` Michael Walle
2021-11-16 10:16 Sahil Malhotra
2021-11-16  8:34 Sahil Malhotra
2021-11-16  8:30 Sahil Malhotra
2021-11-16  6:49 Sahil Malhotra
2021-11-16  6:46 Sahil Malhotra
2021-11-16  6:37 Sahil Malhotra

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=537512dc76cbd87695d93bf7ea419a07@walle.cc \
    --to=michael@walle.cc \
    --cc=V.Sethi@nxp.com \
    --cc=andrey.zhizhikin@leica-geosystems.com \
    --cc=clement.faure@nxp.com \
    --cc=gaurav.jain@nxp.com \
    --cc=pankaj.gupta@nxp.com \
    --cc=priyanka.jain@nxp.com \
    --cc=sahil.malhotra@oss.nxp.com \
    --cc=u-boot@lists.denx.de \
    --cc=ye.li@nxp.com \
    /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).