From: Jon Humphreys <j-humphreys@ti.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: <u-boot@lists.denx.de>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Kamlesh Gurudasani <kamlesh@ti.com>,
Manorit Chawdhry <m-chawdhry@ti.com>, Judith Mendez <jm@ti.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
Devarsh Thakkar <devarsht@ti.com>,
"Simon Glass" <sjg@chromium.org>, Nikhil M Jain <n-jain1@ti.com>,
"Neha Malcom Francis" <n-francis@ti.com>,
Andrew Davis <afd@ti.com>, Maxime Ripard <mripard@kernel.org>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
"Roger Quadros" <rogerq@kernel.org>, Bryan Brattlof <bb@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
Robert Nelson <robertcnelson@gmail.com>,
Nishanth Menon <nm@ti.com>, Tom Rini <trini@konsulko.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v2 02/16] board: am64x: Define capsule update firmware info
Date: Tue, 9 Apr 2024 16:11:43 -0500 [thread overview]
Message-ID: <86wmp6z1f4.fsf@udb0321960.dhcp.ti.com> (raw)
In-Reply-To: <185bd37a-9e1d-4daf-8bd6-57ce598e95fc@gmx.de>
Heinrich Schuchardt <xypron.glpk@gmx.de> writes:
> On 4/9/24 00:31, Jonathan Humphreys wrote:
>> Define the firmwares updatable via EFI capsule update.
>
> Nits:
>
> %s/firmwares/firmware/ (firmware is uncountable).
>
>>
>> Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com>
>> ---
>> board/ti/am64x/evm.c | 33 +++++++++++++++++++++++++++++++++
>> 1 file changed, 33 insertions(+)
>>
>> diff --git a/board/ti/am64x/evm.c b/board/ti/am64x/evm.c
>> index b8de69da06c..876c5c25d42 100644
>> --- a/board/ti/am64x/evm.c
>> +++ b/board/ti/am64x/evm.c
>> @@ -7,6 +7,7 @@
>> *
>> */
>>
>> +#include <efi_loader.h>
>> #include <asm/io.h>
>> #include <dm/uclass.h>
>> #include <k3-ddrss.h>
>> @@ -27,6 +28,38 @@
>>
>> DECLARE_GLOBAL_DATA_PTR;
>>
>> +#if IS_ENABLED(CONFIG_EFI_HAVE_CAPSULE_SUPPORT)
>> +struct efi_fw_image fw_images[] = {
>> + {
>> + .image_type_id = K3_TIBOOT3_IMAGE_GUID,
>> + .fw_name = u"K3_TIBOOT3",
>> + .image_index = 1,
>> + },
>> + {
>> + .image_type_id = K3_SPL_IMAGE_GUID,
>> + .fw_name = u"K3_SPL",
>> + .image_index = 2,
>> + },
>> + {
>> + .image_type_id = K3_UBOOT_IMAGE_GUID,
>> + .fw_name = u"K3_UBOOT",
>> + .image_index = 3,
>> + }
>> +};
>> +
>> +struct efi_capsule_update_info update_info = {
>> + .dfu_string = "sf 0:0=tiboot3.bin raw 0 100000;tispl.bin raw 100000 200000;u-boot.img raw 300000 400000",
>
> Is TI using other addresses than Phytec?
>
> doc/board/phytec/phycore-am64x.rst:
>
> fatload mmc 1 ${loadaddr} tiboot3.bin
> sf update $loadaddr 0x0 $filesize
> fatload mmc 1 ${loadaddr} tispl.bin
> sf update $loadaddr 0x80000 $filesize
> fatload mmc 1 ${loadaddr} u-boot.img
> sf update $loadaddr 0x280000 $filesize
>
This patch has the correct offsets for am64x, so I guess phycore defined
the offsets differently.
> Please, add documentation in doc/board/ for all boards in the series
> specifying the location of the firmware in flash memory and how to
> update it(cf. section OSPI in doc/board/ti/am65x_evm.rst).
>
Yes, I will add patches to document OSPI layouts where missing.
>> + .num_images = ARRAY_SIZE(fw_images),
>> + .images = fw_images,
>> +};
>
> The series has been assigned to me in Patchwork.
>
> But changes should be tested and reviewed by the respective board
> maintainers (Vignesh, Tom for AM64x) as I have no access to TI boards.
>
> Best regards
>
> Heinrich
>
>> +
>> +void set_dfu_alt_info(char *interface, char *devstr)
>> +{
>> + env_set("dfu_alt_info", update_info.dfu_string);
>> +}
>> +
>> +#endif /* EFI_HAVE_CAPSULE_SUPPORT */
>> +
>> int board_init(void)
>> {
>> return 0;
next prev parent reply other threads:[~2024-04-09 21:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 22:31 [PATCH v2 00/16] EFI: ti: Enable EFI capsule updates Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 01/16] board: Define GUIDs for firmware images Jonathan Humphreys
2024-04-09 3:55 ` Heinrich Schuchardt
2024-04-09 21:05 ` Jon Humphreys
2024-04-10 8:30 ` Heinrich Schuchardt
2024-04-10 9:29 ` Ilias Apalodimas
2024-04-12 21:58 ` Jon Humphreys
2024-04-17 10:10 ` Caleb Connolly
2024-04-08 22:31 ` [PATCH v2 02/16] board: am64x: Define capsule update firmware info Jonathan Humphreys
2024-04-09 4:31 ` Heinrich Schuchardt
2024-04-09 21:11 ` Jon Humphreys [this message]
2024-04-10 0:44 ` Tom Rini
2024-04-12 10:42 ` Ilias Apalodimas
2024-04-08 22:31 ` [PATCH v2 03/16] configs: am64x: Enable EFI capsule update Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 04/16] board: j721e: Define capsule update firmware info Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 05/16] configs: j721e: Enable EFI capsule update Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 06/16] board: beagleplay: Define capsule update firmware info Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 07/16] configs: beagleplay: Enable DFU for MMC Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 08/16] configs: beagleplay: Enable EFI capsule update Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 09/16] board: am62px: Define capsule update firmware info Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 10/16] configs: am62px: Enable EFI capsule update Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 11/16] configs: am62x: Enable serial flash DFU Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 12/16] arm: dts: k3-am625-sk-u-boot: Add sysreset-controller node Jonathan Humphreys
2024-04-11 7:54 ` Mattijs Korpershoek
2024-04-11 20:30 ` Jon Humphreys
2024-04-16 9:59 ` Mattijs Korpershoek
2024-04-08 22:31 ` [PATCH v2 13/16] board: am62x: Define capsule update firmware info Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 14/16] configs: am62x: Enable EFI capsule update Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 15/16] board: beagleboneai64: Define capsule update firmware info Jonathan Humphreys
2024-04-08 22:31 ` [PATCH v2 16/16] configs: beagleboneai64: Enable EFI capsule update Jonathan Humphreys
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=86wmp6z1f4.fsf@udb0321960.dhcp.ti.com \
--to=j-humphreys@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=christian.gmeiner@gmail.com \
--cc=devarsht@ti.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jm@ti.com \
--cc=kamlesh@ti.com \
--cc=m-chawdhry@ti.com \
--cc=mkorpershoek@baylibre.com \
--cc=mripard@kernel.org \
--cc=n-francis@ti.com \
--cc=n-jain1@ti.com \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=xypron.glpk@gmx.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