From: Francesco Dolcini <francesco@dolcini.it>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, Marek Vasut <marex@denx.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
u-boot@lists.denx.de,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] mtd: parsers: ofpart: add workaround for #size-cells 0
Date: Mon, 23 Jan 2023 11:35:37 +0100 [thread overview]
Message-ID: <Y85i+R79AWvAUAj7@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20230123112808.6340a016@xps-13>
On Mon, Jan 23, 2023 at 11:28:08AM +0100, Miquel Raynal wrote:
> francesco@dolcini.it wrote on Fri, 13 Jan 2023 19:45:56 +0100:
>
> > From: Francesco Dolcini <francesco.dolcini@toradex.com>
> >
> > Add a mechanism to handle the case in which partitions are present as
> > direct child of the nand controller node and #size-cells is set to <0>.
> >
> > This could happen if the nand-controller node in the DTS is supposed to
> > have #size-cells set to 0, but for some historical reason/bug it was set
> > to 1 in the past, and the firmware (e.g. U-Boot) is adding the partition
> > as direct children of the nand-controller defaulting to #size-cells
> > being to 1.
> >
> > This prevents a real boot failure on colibri-imx7 that happened during v6.1
> > development cycles.
> >
> > Link: https://lore.kernel.org/all/Y4dgBTGNWpM6SQXI@francesco-nb.int.toradex.com/
> > Link: https://lore.kernel.org/all/20221202071900.1143950-1-francesco@dolcini.it/
> > Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> > Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> >
> > Miquel, Marek: I do not expect this patch to be backported to stable, however
> > I would expect that we do not backport nand-controller dts cleanups neither.
>
> Okay.
[snip]
> > + pr_warn("%s: ofpart partition %pOF (%pOF) #size-cells is wrongly set to <0>, assuming <1> for parsing partitions.\n",
> > + master->name, pp,
> > + mtd_node);
>
> Why mtd_node on a new line?
For some historical reason most of this file is like that, so I did the
same for consistency (to be honest when I did it I though it was _all_
like that).
> Otherwise looks good to me.
I can send a v2 with this changed.
Francesco
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-01-23 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 18:45 [PATCH v2] mtd: parsers: ofpart: add workaround for #size-cells 0 Francesco Dolcini
2023-01-23 10:28 ` Miquel Raynal
2023-01-23 10:35 ` Francesco Dolcini [this message]
2023-01-23 10:52 ` Miquel Raynal
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=Y85i+R79AWvAUAj7@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=francesco.dolcini@toradex.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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