All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: Patrick DELAUNAY <patrick.delaunay@foss.st.com>
Cc: Patrice CHOTARD <patrice.chotard@foss.st.com>,
	<u-boot@lists.denx.de>,
	U-Boot STM32 <uboot-stm32@st-md-mailman.stormreply.com>,
	Marek Vasut <marex@denx.de>
Subject: Re: [Uboot-stm32] [PATCH] dfu: dfu_mtd: set max_buf_size to erasesize also for NOR devices
Date: Mon, 7 Jun 2021 10:39:46 +0200	[thread overview]
Message-ID: <20210607103946.5e235a20@ktm> (raw)
In-Reply-To: <0616d868-1939-e0dc-3d3a-8e4b150a95e9@foss.st.com>

[-- Attachment #1: Type: text/plain, Size: 2666 bytes --]

Hi Patrick,

> Thanks Patrice,
> 
> On 4/20/21 12:24 PM, Patrice CHOTARD wrote:
> > Hi Patrick
> >
> > On 3/4/21 5:47 PM, Patrick Delaunay wrote:  
> >> For NOR devices the logical DFU buffer size is the sector_size,
> >> as it is done in dfu_sf.c or in spi/sf_mtd.c
> >> (sf_mtd_info.erasesize = flash->sector_size)
> >>
> >> For NAND the DFU size was already limited to erasesize as
> >> has_pages = true.
> >>
> >> So the mtd dfu backend can use this erasesize for all the MTD
> >> devices, NOR and NAND with dfu->max_buf_size = mtd->erasesize
> >>
> >> This difference was initially copied from MTD command, where
> >> data is fully available in RAM without size limitation.
> >>
> >> This patch avoids to have many sector write in dfu_mtd.c at the end
> >> of the DFU transfer and avoids issues with USB timeout or WATCHDOG.
> >>
> >> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> >> ---
> >>
> >>   drivers/dfu/dfu_mtd.c | 5 +----
> >>   1 file changed, 1 insertion(+), 4 deletions(-)
> >>
> >> diff --git a/drivers/dfu/dfu_mtd.c b/drivers/dfu/dfu_mtd.c
> >> index ca67585a7e..7efb3cbd79 100644
> >> --- a/drivers/dfu/dfu_mtd.c
> >> +++ b/drivers/dfu/dfu_mtd.c
> >> @@ -252,7 +252,6 @@ int dfu_fill_entity_mtd(struct dfu_entity
> >> *dfu, char *devstr, char *s) {
> >>   	char *st;
> >>   	struct mtd_info *mtd;
> >> -	bool has_pages;
> >>   	int ret, part;
> >>   
> >>   	mtd = get_mtd_device_nm(devstr);
> >> @@ -262,9 +261,7 @@ int dfu_fill_entity_mtd(struct dfu_entity
> >> *dfu, char *devstr, char *s) 
> >>   	dfu->dev_type = DFU_DEV_MTD;
> >>   	dfu->data.mtd.info = mtd;
> >> -
> >> -	has_pages = mtd->type == MTD_NANDFLASH || mtd->type ==
> >> MTD_MLCNANDFLASH;
> >> -	dfu->max_buf_size = has_pages ? mtd->erasesize : 0;
> >> +	dfu->max_buf_size = mtd->erasesize;
> >>   
> >>   	st = strsep(&s, " ");
> >>   	if (!strcmp(st, "raw")) {
> >>  
> > Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
> >
> > Thanks
> >
> > Patrice  
> 
> 
> Lukasz, any remarks on your side?
> 
> 
> Can I take this patch in my first STM32 pull request for v2020.10 ?

Please pull it to your tree.

> 
> or a PR is already planed on your side ?
> 
> http://patchwork.ozlabs.org/project/uboot/patch/20210304174748.1.I1d824180669d63e22275f082e7ac0fe50c2b8646@changeid/
> 
> 
> Regards
> 
> Patrick
> 



Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-06-07  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 16:47 [PATCH] dfu: dfu_mtd: set max_buf_size to erasesize also for NOR devices Patrick Delaunay
2021-04-20 10:24 ` [Uboot-stm32] " Patrice CHOTARD
2021-06-04 16:59   ` Patrick DELAUNAY
2021-06-07  8:39     ` Lukasz Majewski [this message]
2021-06-18  8:10   ` Patrice CHOTARD

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=20210607103946.5e235a20@ktm \
    --to=lukma@denx.de \
    --cc=marex@denx.de \
    --cc=patrice.chotard@foss.st.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-stm32@st-md-mailman.stormreply.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.