From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/4] mtd: nand: Add special fixup kernel partitions for Denali
Date: Wed, 25 Nov 2020 06:20:07 +0100 [thread overview]
Message-ID: <20201125052011.20660-1-s.hauer@pengutronix.de> (raw)
In the Denali NAND driver the partitions device node to fixup
for the kernel changed over time. This used to be a direct subnode
of the controller node, but Kernel v5.2 introduced an additional
subnode between the controller node and the partitions node.
Until then the binding complies with the current generic NAND
binding which has subnodes for each NAND chip under the controller
node.
We'll likely see that more often in the future. For now solve this
at driver level, but we might want to solve that in mtd code some
day.
Sascha
Sascha Hauer (4):
mtd: Remove set but not used of_path
of: partitions: export of_fixup_partitions
mtd: Add hook to fix up kernel partitions
mtd: nand: denali: cope with kernel device trees without chip subnodes
drivers/mtd/core.c | 31 +++++++++++++++--
drivers/mtd/nand/nand_denali_dt.c | 57 +++++++++++++++++++++++++++++++
drivers/of/partition.c | 37 +++++++++++---------
include/linux/mtd/mtd.h | 3 +-
include/of.h | 6 ++++
5 files changed, 115 insertions(+), 19 deletions(-)
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2020-11-25 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 5:20 Sascha Hauer [this message]
2020-11-25 5:20 ` [PATCH 1/4] mtd: Remove set but not used of_path Sascha Hauer
2020-11-25 5:20 ` [PATCH 2/4] of: partitions: export of_fixup_partitions Sascha Hauer
2020-11-25 5:20 ` [PATCH 3/4] mtd: Add hook to fix up kernel partitions Sascha Hauer
2020-11-25 5:20 ` [PATCH 4/4] mtd: nand: denali: cope with kernel device trees without chip subnodes Sascha Hauer
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=20201125052011.20660-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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