From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org, linux-mtd@lists.infradead.org
Cc: devicetree-discuss <devicetree-discuss@ozlabs.org>
Subject: [PATCH 0/4 v2] mtd: physmap_of: Add multiple regions and concatenation support
Date: Tue, 7 Apr 2009 10:36:10 +0200 [thread overview]
Message-ID: <200904071036.11184.sr@denx.de> (raw)
This patchset adds support to handle multiple non-identical chips in one
flash device tree node. It also adds concat support to physmap_of. This
makes it possible to support e.g. the Intel P30 48F4400 chip which
internally consists of 2 non-identical NOR chips on one die. Additionally
partitions now can span over multiple chips:
mtd: physmap_of: Add multiple regions and concatenation support
mtd/powerpc: Factor out MTD physmap bindings into mtd-physmap.txt
mtd/powerpc: Remove unused "device-width" property
mtd/powerpc: Describe multiple "reg" tuples usage
v2 addresses all comments from Grant Likely, including factoring out the
MTD dts bindings documentation into a separate file.
Thanks,
Stefan
reply other threads:[~2009-04-07 8:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200904071036.11184.sr@denx.de \
--to=sr@denx.de \
--cc=devicetree-discuss@ozlabs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).