From: Roger Quadros <rogerq@kernel.org>
To: dario.binacchi@amarulasolutions.com,
michael@amarulasolutions.com, hs@denx.de,
enrico.leto@siemens.com
Cc: trini@konsulko.com, praneeth@ti.com, nm@ti.com, vigneshr@ti.com,
u-boot@lists.denx.de
Subject: Re: [PATCH v2 0/2] mtd: nand: omap_gpmc: Fix NAND for AM335x
Date: Thu, 11 Jan 2024 15:06:22 +0200 [thread overview]
Message-ID: <5d79b1c8-4dc8-44d3-bfe7-4514f41c7102@kernel.org> (raw)
In-Reply-To: <20231211114600.4414-1-rogerq@kernel.org>
Hi,
On 11/12/2023 13:45, Roger Quadros wrote:
> Hi,
>
> These patches fix NAND and ELM for AM335x and related legacy platforms
> that use HW BCH and ELM modules.
>
> All CI tests pass: https://github.com/u-boot/u-boot/pull/453
>
> Changelog:
>
> v2:
> - added __maybe_unused to omap_calculate_ecc_bch. fixes CI tests
> - Added Tested-by Tags
> - Explained about omap_elm single sector support in commit log
>
> cheers,
> -roger
>
> Roger Quadros (2):
> mtd: nand: omap_gpmc: Fix NAND in SPL for AM335x
> mtd: rawnand: omap_elm: Fix elm_init definition
>
> drivers/mtd/nand/raw/omap_elm.c | 4 +-
> drivers/mtd/nand/raw/omap_elm.h | 6 --
> drivers/mtd/nand/raw/omap_gpmc.c | 95 ++++++++++----------------------
> 3 files changed, 31 insertions(+), 74 deletions(-)
>
>
> base-commit: 2f0282922b2c458eea7f85c500a948a587437b63
If no objections can this be Acked and picked up please?
Without these NAND is broken on some TI platforms.
Thanks!
--
cheers,
-roger
next prev parent reply other threads:[~2024-01-11 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 11:45 [PATCH v2 0/2] mtd: nand: omap_gpmc: Fix NAND for AM335x Roger Quadros
2023-12-11 11:45 ` [PATCH v2 1/2] mtd: nand: omap_gpmc: Fix NAND in SPL " Roger Quadros
2023-12-11 11:46 ` [PATCH v2 2/2] mtd: rawnand: omap_elm: Fix elm_init definition Roger Quadros
2024-01-11 13:06 ` Roger Quadros [this message]
2024-01-11 13:13 ` [PATCH v2 0/2] mtd: nand: omap_gpmc: Fix NAND for AM335x Michael Nazzareno Trimarchi
2024-01-15 9:43 ` Dario Binacchi
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=5d79b1c8-4dc8-44d3-bfe7-4514f41c7102@kernel.org \
--to=rogerq@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=enrico.leto@siemens.com \
--cc=hs@denx.de \
--cc=michael@amarulasolutions.com \
--cc=nm@ti.com \
--cc=praneeth@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox