public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@xilinx.com>, Simon Glass <sjg@chromium.org>
Cc: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>,
	Dzmitry Sankouski <dsankouski@gmail.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Nikhil M Jain <n-jain1@ti.com>
Subject: Re: [PATCH 0/2] dm: core: Add support for filling script_offset_f/script_size_f from DT
Date: Fri, 25 Aug 2023 09:17:13 +0200	[thread overview]
Message-ID: <1bae8050-990d-5aa2-ed02-a69dbe177cc3@amd.com> (raw)
In-Reply-To: <cover.1691069786.git.michal.simek@amd.com>



On 8/3/23 15:36, Michal Simek wrote:
> Hi,
> 
> The commit https://github.com/devicetree-org/dt-schema/pull/105 added
> support for reading memory location where bootscript should be loaded.
> This is follow up series on reading information from DT where boot script
> is placed in flash memory.
> 
> Patches are based on
> https://lore.kernel.org/r/b37aec1460d93727a9065766aa5f50fa356ae5aa.1690873880.git.michal.simek@amd.com
> and
> https://lore.kernel.org/r/b77352af92102dfad2e12a49a7680f5f64f8ee31.1690873880.git.michal.simek@amd.com
> 
> I didn't send pull request to dt-schema yet because I want to check logic
> around it and DT variable names bootscr-flash-offset and bootscr-flash-size
> are correct.
> 
> Also there should be follow up patch to remove CONFIG_BOOT_SCRIPT_OFFSET
> Kconfig symbol and remove variable script_size_f setup from config file.
> 
> Also keep in mind that this is pretty much just 1:1 conversion between DT
> and variable. Upstream code is using it for QSPI only and we are also using
> in for NAND devices too. But the same approach could be used for DISKs,
> EEPROMs or SD RAW. That's why I pretty much think that DT description
> should be done a little bit differently.
> For example:
> bootscr-location = <&nvmem offset size>;
> 
> Thanks,
> Michal
> 
> 
> Michal Simek (2):
>    dm: core: ofnode: Add ofnode_read_bootscript_flash()
>    xilinx: board: Add support to pick bootscr flash offset/size from DT
> 
>   arch/sandbox/dts/test.dts   |  2 ++
>   board/xilinx/common/board.c | 13 +++++++++++--
>   drivers/core/ofnode.c       | 34 ++++++++++++++++++++++++++++++++++
>   include/dm/ofnode.h         | 27 +++++++++++++++++++++++++++
>   test/dm/ofnode.c            |  9 +++++++--
>   5 files changed, 81 insertions(+), 4 deletions(-)
> 

Applied.
M

      parent reply	other threads:[~2023-08-25  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 13:36 [PATCH 0/2] dm: core: Add support for filling script_offset_f/script_size_f from DT Michal Simek
2023-08-03 13:36 ` [PATCH 1/2] dm: core: ofnode: Add ofnode_read_bootscript_flash() Michal Simek
2023-08-04  0:18   ` Simon Glass
2023-08-03 13:36 ` [PATCH 2/2] xilinx: board: Add support to pick bootscr flash offset/size from DT Michal Simek
2023-08-25  7:17 ` Michal Simek [this message]

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=1bae8050-990d-5aa2-ed02-a69dbe177cc3@amd.com \
    --to=michal.simek@amd.com \
    --cc=abdellatif.elkhlifi@arm.com \
    --cc=dsankouski@gmail.com \
    --cc=git@xilinx.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=n-jain1@ti.com \
    --cc=sjg@chromium.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