David Gibson wrote:
On Mon, Mar 16, 2009 at 10:32:18AM +0000, Martyn Welch wrote:
Support for the PPC9A VME Single Board Computer from GE Fanuc (PowerPC
MPC8641D).
This is the basic board support for GE Fanuc's PPC9A, a 6U single board
computer, based on Freescale's MPC8641D.
Uh.. sorry. Should have noticed these little nitpicks the first time
around.
No problem, just a few queries.
+ local...@fef05000 {
+ #address-cells = <2>;
+ #size-cells = <1>;
+ compatible = "fsl,mpc8641-localbus", "simple-bus";
+ reg = <0xfef05000 0x1000>;
+ interrupts = <19 2>;
+ interrupt-parent = <&mpic>;
+
+ ranges = <0 0 0xff000000 0x01000000 // 16MB Boot flash
+ 1 0 0xe8000000 0x08000000 // Paged Flash 0
+ 2 0 0xe0000000 0x08000000 // Paged Flash 1
+ 3 0 0xfc100000 0x00020000 // NVRAM
+ 4 0 0xfc000000 0x00008000 // FPGA
+ 5 0 0xfc008000 0x00008000 // AFIX FPGA
+ 6 0 0xfd000000 0x00800000 // IO FPGA (8-bit)
+ 7 0 0xfd800000 0x00800000>; // IO FPGA (32-bit)
+
+ /* fl...@0,0 is a mirror of part of the memory in fl...@1,0
+ fl...@0,0 {
+ compatible = "cfi-flash";
It would be nice to have the actual type of flash chips here, although
it's not essential.
Flash is a little tricky, it's paged. We haven't found a good way of dealing
with this yet and as a result we currently just support the first page, which
may not even match one full chip width. This is especially so for fl...@0,0,
which is mirrored via an FPGA, the exact region depends on some jumper settings
and is access is definitely read only via this region (this region is commented
out in the DTS and really there for completeness as we don't expect to ever use
it or enable it from Linux and is only there to all the firmware to boot). We
are currently using Spansion s29gl01gp parts, which have some tricky mechanisms
for sector protection (given that the parts are paged). As a result, providing
the specific chip won't be much use, if a specific driver is written for
spansion flash the spansion specific mechanisms are unlikely to work.
If you still want the specific chip, how about this:
compatible = "spansion, s29gl01gp", "cfi-flash";
[snip]
+ f...@4,0 {
+ compatible = "gef,fpga-regs";
I don't imagine this is the only set of FPGA based control regs GE
Fanuc will ever make, so this should be more precise. Including the
board type here is probably the way to go.
OK.
compatible = "gef,fpga-regs-ppc9a";
+ reg = <0x4 0x0 0x40>;
+ };
+
+ w...@4,2000 {
+ compatible = "gef,fpga-wdt";
And likewise here.
We only have one core that is used on all our sites current and planned boards
(as far as I know). How about (idea borrowed from virtex440-ml507.dts):
compatible = "gef,fpga-wdt-1.00";
+ reg = <0x4 0x2000 0x8>;
+ interrupts = <0x1a 0x4>;
+ interrupt-parent = <&gef_pic>;
+ };
+ /* Second watchdog available, driver currently supports one.
+ w...@4,2010 {
+ compatible = "gef,fpga-wdt";
+ reg = <0x4 0x2010 0x8>;
+ interrupts = <0x1b 0x4>;
+ interrupt-parent = <&gef_pic>;
+ };
+ */
+ gef_pic: p...@4,4000 {
+ #interrupt-cells = <1>;
+ interrupt-controller;
+ compatible = "gef,fpga-pic";
And possibly here, although in this case I imagine several boards
might have compatible FPGA PICs.
Yes, the same design is used on all the new boards I know about. As with the
watchdog, boards in the future may have different designs. Would this be
acceptable?:
compatible = "gef,fpga-pic-1.00";
+ i2c1: i...@3000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "fsl-i2c";
This should list include a compatible string specific to the
particular SoC model before the general name.
The documentation seems to suggest to use "fsl-i2c". Should it be like this?:
compatible = "fsl,mpc8641d-i2c", fsl-i2c";
Martyn
--
Martyn Welch MEng MPhil MIET (Principal Software Engineer) T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd, |Registered in England and Wales
Tove Valley Business Park, Towcester, |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB VAT:GB 729849476
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
