All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Jacques Hiblot <jjhiblot@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v1 0/9] Add support for applications of overlays in SPL
Date: Fri, 29 Mar 2019 11:13:55 +0100	[thread overview]
Message-ID: <f88a3048-2a5d-63e8-a790-628a1ec1034c@ti.com> (raw)
In-Reply-To: <ebca1ef9-82da-f106-d9c7-c6646629d517@xilinx.com>


On 28/03/2019 14:54, Michal Simek wrote:
> On 25. 03. 19 9:08, Michal Simek wrote:
>> On 22. 03. 19 15:39, Jean-Jacques Hiblot wrote:
>>> The purpose of this series is to provide the SPL with ability to apply
>>> overlays for u-boot. this is only a RFC so far, to get a feedback on the
>>> approach.
>>>
>>> Our use-case is the support of the daughter boards of the AM65x EVM. In
>>> Linux, each board is supported by a unique overlay. The presence of the
>>> boards is detected at runtime, and some useful features (like USB) are
>>> implemented on those daughter boards. Instead of providing multiple dtbs
>>> and fall in a combinatorial pit, we propose to use DT overlays.
>> Not sure if you have it on these boards too but I expect you are able to
>> detect base board with this code board/ti/common/board_detect.c
>>
>> How do you detect these daughter cards? Is there additional I2C
>> connection to them and they have on board eeprom with any format for
>> detection?
Yes. There is EEPROM and GPIOs involved in the detection process.
>> Something similar what it is part of FMC standard/VITA 57.1 with using
>> FRU spec for daughter card description?
>> Anyway we are working on FRU parser exactly for this purpose.
>>
>> Do you also need to apply that overlays in SPL?
We need to apply in SPL so that u-boot has the right information in the DT.
>> Isn't it enough to apply them as the part of board_fdt_blob_setup()?
No it's possible to do that in board_fdt_blob_setup().
> I see v2 now but without answering my questions here.

Yes I had prepared the answer and forgot to push the send button.

in the V2 the biggest change is when the list of additional images is 
obtained from the board. It is now in spl_fit_get_image_name() and that 
makes its usable for other kind of binaries than just overlays.


JJ

>
> M
>

  reply	other threads:[~2019-03-29 10:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 14:39 [U-Boot] [RFC PATCH v1 0/9] Add support for applications of overlays in SPL Jean-Jacques Hiblot
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 1/9] dtbo: also generate dtbo from dtso Jean-Jacques Hiblot
2019-03-25  7:57   ` Michal Simek
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 2/9] Makefile.lib: include /__symbols__ in dtb if OF_LIBFDT_OVERLAY is enabled Jean-Jacques Hiblot
2019-03-25  7:33   ` Michal Simek
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 3/9] Makefile: Fix u-boot.itb generation when building outside the source tree Jean-Jacques Hiblot
2019-03-30 21:18   ` Simon Glass
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 4/9] Makefile: Pass the board name to the FIT generator scripts Jean-Jacques Hiblot
2019-03-30 21:18   ` Simon Glass
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 5/9] Makefile: use custom ITS to build u-boot.img if SPL_FIT_SOURCE or SPL_FIT_GENERATOR are set Jean-Jacques Hiblot
2019-03-30 21:18   ` Simon Glass
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 6/9] spl: fit: Allow calling spl_load_fit_image() to only get the image size Jean-Jacques Hiblot
2019-03-25  8:12   ` Michal Simek
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 7/9] spl: fit: Add support for applying DT overlay Jean-Jacques Hiblot
2019-03-25  8:18   ` Michal Simek
2019-03-25 11:40     ` Jean-Jacques Hiblot
2019-03-25 11:58       ` Michal Simek
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 8/9] sp: fit: Allow the board to dynamically select the DTB overlays it needs Jean-Jacques Hiblot
2019-03-25  9:44   ` Michal Simek
2019-03-22 14:39 ` [U-Boot] [RFC PATCH v1 9/9] !!! TEMP !!! For demonstration only !!! DRA76: Usage of overlays in SPL Jean-Jacques Hiblot
2019-03-25  8:08 ` [U-Boot] [RFC PATCH v1 0/9] Add support for applications " Michal Simek
2019-03-28 13:54   ` Michal Simek
2019-03-29 10:13     ` Jean-Jacques Hiblot [this message]
2019-03-29 10:26       ` Michal Simek
2019-03-29 12:50         ` Jean-Jacques Hiblot
2019-03-29 16:48           ` Michal Simek
2019-03-27  9:39 ` Lukasz Majewski
2019-03-27 17:41   ` Jean-Jacques Hiblot
2019-03-28  6:45     ` Lukasz Majewski

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=f88a3048-2a5d-63e8-a790-628a1ec1034c@ti.com \
    --to=jjhiblot@ti.com \
    --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 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.