From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org,
"devicetree-discuss list" <devicetree-discuss@ozlabs.org>
Subject: physmap_of and partitions (mtd concat support)
Date: Mon, 23 Mar 2009 11:51:10 +0100 [thread overview]
Message-ID: <200903231151.10373.sr@denx.de> (raw)
I just noticed that physmap_of can't handle multiple devices of different type
described in one device node. For example the Intel P30 48F4400 (64MByte)
consists internally of 2 non-identical NOR chips. So a "simple"
flash@0,0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "cfi-flash";
reg = <0 0 0x04000000>;
bank-width = <2>;
device-width = <2>;
partition@0 {
label = "test-part";
reg = <0 0x04000000>;
};
}
is not working. It will "detect" 2 identical 32MByte chips which is wrong.
Adding a 2nd flash node solves this problem:
flash@0,0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "cfi-flash";
reg = <0 0 0x02000000>;
bank-width = <2>;
device-width = <2>;
partition@0 {
label = "test-part1";
reg = <0 0x02000000>;
};
}
flash@1,0 {
#address-cells = <1>;
#size-cells = <1>;
compatible = "cfi-flash";
reg = <0 0x02000000 0x02000000>;
bank-width = <2>;
device-width = <2>;
partition@0 {
label = "test-part2";
reg = <0 0x02000000>;
};
}
This way both chips are detected correctly.
Now the real problem: How should I describe a partition in the device tree
spanning over both devices (concat)?. The current physmap_of driver doesn't
handle concat at all (physmap.c does). I already have some ideas on how to
implement this concat support in physmap_of. But ideas about a device-tree
syntax for such partitions are very welcome.
Thanks.
Best regards,
Stefan
next reply other threads:[~2009-03-23 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 10:51 Stefan Roese [this message]
2009-03-23 15:37 ` physmap_of and partitions (mtd concat support) Grant Likely
2009-03-24 9:07 ` Stefan Roese
2009-03-24 14:57 ` Grant Likely
2009-03-24 15:39 ` Stefan Roese
2009-03-24 16:28 ` Grant Likely
2009-03-25 9:35 ` Stefan Roese
2009-03-25 13:28 ` Grant Likely
2009-03-25 14:14 ` Stefan Roese
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=200903231151.10373.sr@denx.de \
--to=sr@denx.de \
--cc=devicetree-discuss@ozlabs.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).