From: Pratyush Yadav <pratyush@kernel.org>
To: tkuw584924@gmail.com
Cc: u-boot@lists.denx.de, jagan@amarulasolutions.com,
vigneshr@ti.com, tudor.ambarus@linaro.org, d-gole@ti.com,
pratyush@kernel.org, Bacem.Daassi@infineon.com,
Takahiro Kuwano <Takahiro.Kuwano@infineon.com>
Subject: Re: [PATCH v2 1/6] mtd: ubi: Do not zero out EC and VID on ECC-ed NOR flashes
Date: Mon, 29 Apr 2024 16:17:44 +0200 [thread overview]
Message-ID: <mafs0v840b6d3.fsf@kernel.org> (raw)
In-Reply-To: <b92b89d130f8075cebf74bc02eb6efe41afc6d75.1714020303.git.Takahiro.Kuwano@infineon.com> (tkuw's message of "Thu, 25 Apr 2024 13:52:11 +0900")
On Thu, Apr 25 2024, tkuw584924@gmail.com wrote:
> From: Takahiro Kuwano <Takahiro.Kuwano@infineon.com>
I wonder how authorship should work for such patches. Patches 1, 2, and
6 in this series are very close to what my patches did for Linux. So I
wonder who should get authorship in this case: the person porting the
patch or the person who wrote the original one. Same for patch 5 but
that is still a little more changed from its Linux counterpart.
>
> For NOR flashes EC and VID are zeroed out before an erase is issued to
> make sure UBI does not mistakenly treat the PEB as used and associate it
> with an LEB.
>
> But on some flashes, like the Infineon Semper NOR flash family,
> multi-pass page programming is not allowed on the default ECC scheme.
> This means zeroing out these magic numbers will result in the flash
> throwing a page programming error.
>
> Do not zero out EC and VID for such flashes. A writesize > 1 is an
> indication of an ECC-ed flash.
>
> This patch replicates the following upstream linux commit:
> f669e74be820 ("ubi: Do not zero out EC and VID on ECC-ed NOR flashes")
>
> Acked-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> Signed-off-by: Takahiro Kuwano <Takahiro.Kuwano@infineon.com>
Apart from my comment above,
Acked-by: Pratyush Yadav <pratyush@kernel.org>
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2024-04-29 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 4:52 [PATCH v2 0/6] mtd: Make sure UBIFS does not do multi-pass page programming on flashes that don't support it tkuw584924
2024-04-25 4:52 ` [PATCH v2 1/6] mtd: ubi: Do not zero out EC and VID on ECC-ed NOR flashes tkuw584924
2024-04-29 14:17 ` Pratyush Yadav [this message]
2024-04-29 14:44 ` Tudor Ambarus
2024-04-25 4:52 ` [PATCH v2 2/6] mtd: spi-nor: Allow flashes to specify MTD writesize tkuw584924
2024-04-25 4:52 ` [PATCH v2 3/6] mtd: spi-nor: Check nor->info before setting macronix_octal_fixups tkuw584924
2024-04-25 6:17 ` Tudor Ambarus
2024-04-25 4:52 ` [PATCH v2 4/6] mtd: spi-nor: Replace default_init() hook with late_init() tkuw584924
2024-04-25 6:13 ` Tudor Ambarus
2024-04-25 4:52 ` [PATCH v2 5/6] mtd: spi-nor: Call spi_nor_post_sfdp_fixups() only after spi_nor_parse_sfdp() tkuw584924
2024-04-25 6:16 ` Tudor Ambarus
2024-04-25 4:52 ` [PATCH v2 6/6] mtd: spi-nor: Set ECC unit size to MTD writesize in Infineon SEMPER flashes tkuw584924
2024-04-25 6:14 ` Tudor Ambarus
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=mafs0v840b6d3.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=Bacem.Daassi@infineon.com \
--cc=Takahiro.Kuwano@infineon.com \
--cc=d-gole@ti.com \
--cc=jagan@amarulasolutions.com \
--cc=tkuw584924@gmail.com \
--cc=tudor.ambarus@linaro.org \
--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.