From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Jonathan Humphreys <j-humphreys@ti.com>,
Roger Quadros <rogerq@kernel.org>,
Jonathan Humphreys <j-humphreys@ti.com>,
Martyn Welch <martyn.welch@collabora.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Sjoerd Simons <sjoerd@collabora.com>,
Tom Rini <trini@konsulko.com>,
vigneshr@ti.com
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH] configs: am62x_evm_*: Set DFU buffer size to 256k
Date: Thu, 16 Jan 2025 09:38:43 +0100 [thread overview]
Message-ID: <87r053886k.fsf@baylibre.com> (raw)
In-Reply-To: <20241220215334.372542-1-j-humphreys@ti.com>
Hi John,
Thank you for the patch.
On ven., déc. 20, 2024 at 15:53, Jonathan Humphreys <j-humphreys@ti.com> wrote:
> OSPI flash writing was broken on am62x SKs as the OSPI flash device has a
> 256k sector size but was set to 20k. This breaks OSPI flash writes because
> the current implementation of the SF DFU backend requires that the DFU data
> buffer size be the same as the sector erase size, and the USB DFU config
> fragment (for both A53 and R5) reduced the size of the DFU data buffer,
> presumably so that it can fit into SPL's much smaller heap.
>
> Change the SYS_DFU_DATA_BUF_SIZE to the erase sector size, which still fits
> within the post-relocation heap size in SPL.
>
> Fixes: dfc2dff5a844 ("configs: am62x_evm_*: Enable USB and DFU support")
>
> Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> ---
> configs/am62x_a53_usbdfu.config | 2 +-
> configs/am62x_r5_usbdfu.config | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/configs/am62x_a53_usbdfu.config b/configs/am62x_a53_usbdfu.config
> index 0d3c6df1e73..812f99ee70b 100644
> --- a/configs/am62x_a53_usbdfu.config
> +++ b/configs/am62x_a53_usbdfu.config
> @@ -10,7 +10,7 @@ CONFIG_SYSCON=y
> CONFIG_SPL_SYSCON=y
> CONFIG_DFU_MMC=y
> CONFIG_DFU_RAM=y
> -CONFIG_SYS_DFU_DATA_BUF_SIZE=0x5000
> +CONFIG_SYS_DFU_DATA_BUF_SIZE=0x40000
> CONFIG_SYS_DFU_MAX_FILE_SIZE=0x800000
> CONFIG_USB=y
> CONFIG_DM_USB_GADGET=y
> diff --git a/configs/am62x_r5_usbdfu.config b/configs/am62x_r5_usbdfu.config
> index 772bb2ab935..efaae504c1a 100644
> --- a/configs/am62x_r5_usbdfu.config
> +++ b/configs/am62x_r5_usbdfu.config
> @@ -1,7 +1,7 @@
> CONFIG_SPL_ENV_SUPPORT=y
> CONFIG_SYSCON=y
> CONFIG_SPL_SYSCON=y
> -CONFIG_SYS_DFU_DATA_BUF_SIZE=0x5000
> +CONFIG_SYS_DFU_DATA_BUF_SIZE=0x40000
> CONFIG_MISC=y
> CONFIG_USB=y
> CONFIG_DM_USB_GADGET=y
> --
> 2.34.1
next prev parent reply other threads:[~2025-01-16 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 21:53 [PATCH] configs: am62x_evm_*: Set DFU buffer size to 256k Jonathan Humphreys
2025-01-04 17:05 ` Roger Quadros
2025-01-16 8:38 ` Mattijs Korpershoek [this message]
2025-01-21 17:34 ` 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=87r053886k.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=j-humphreys@ti.com \
--cc=martyn.welch@collabora.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=sjoerd@collabora.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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 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.