How do ARM platform initialize DDR?
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Regards,
York
Hi York,
There is no generic driver. AFAIK. Having worked on both mpc85xx and ARM
I can tell you about samsung 5250. There are 2 uboots (one spl and other main). In case of sd/mmc boot the internal rom copies the spl uboot to iRAM and the spl boot loader initialises the DDR3.
you can check for board/samsung/smdk5250/dmc_init_ddr3.c
-Regards
mj
Quoted 20 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Regards,
York
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Signature · 1 line
-mj
Dear MJ,
Thanks for your reply.
I don't see the file in my copy. Probably it is not merged yet? Anyway, you just confirmed what I found so far. Do you use static setting in dmc_init_ddr3.c? I mean does it adapt to different DDR speeds and modules (if applicable)?
In my mind, I am thinking to restructure arch/powerpc/cpu/mpc8xxx/ddr/ to driver/ddr/fsl/ so the same driver can be shared as far as the DDR IP is the same (or similar).
York
Quoted 36 lines · MJ embd
Hi York,
There is no generic driver. AFAIK. Having worked on both mpc85xx and ARM
I can tell you about samsung 5250. There are 2 uboots (one spl and other main). In case of sd/mmc boot the internal rom copies the spl uboot to iRAM and the spl boot loader initialises the DDR3.
you can check for
board/samsung/smdk5250/dmc_init_ddr3.c-Regards
mjQuoted 20 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Regards,
York
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
yes, I am using uboot for arndale board.
The code is written by samsung only and it is not static.
The best option would be to have an eth / serial driver kind of arch which all soc vendors can share. But ddr is scattered, in absence of that, your point seems valid for fsl specific.
-mj
Quoted 57 lines · York Sun
Dear MJ,
Thanks for your reply.
I don't see the file in my copy. Probably it is not merged yet? Anyway, you just confirmed what I found so far. Do you use static setting in
dmc_init_ddr3.c? I mean does it adapt to different DDR speeds and modules (if applicable)?In my mind, I am thinking to restructure
arch/powerpc/cpu/mpc8xxx/ddr/to driver/ddr/fsl/ so the same driver can be shared as far as the DDR IP is the same (or similar).York
Quoted 37 lines · MJ embd
Hi York,
There is no generic driver. AFAIK. Having worked on both mpc85xx and ARM
I can tell you about samsung 5250. There are 2 uboots (one spl and other main).
In case of sd/mmc boot the internal rom copies the spl uboot to iRAM and the spl boot loader initialises the DDR3.you can check for
board/samsung/smdk5250/dmc_init_ddr3.c-Regards
mjQuoted 20 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Regards,
York
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Signature · 1 line
-mj
Adding Vipin to the thread as he has better knowledge on this than me. Vipin can you please add your comments here as well..
As far as I can remember for the ARM based SPEAr SoCs on which we worked in the past:
- At the moment the DDR initialization code for various ARM SoCs in u-boot is scattered across ARCH directories:
See examples of SPEAr (based on ARM926ejs) [1] and OMAP4 (ARmv7) [2] DDR drivers.
- There is no unified driver model in place for DDR driver similar to what is available for eth/serial drivers and we need to formulate a DDR model (something using the suggested framework in [3]) so that the same DDR driver can be shared across PPC and ARM SoCs.
References:
[1] SPEAr DDR drivers for Denali MPMC -
[2] OMAP4 Elpida DDR drivers -
[3] UDM-cores.txt -
Regards,
Bhupesh
Quoted 84 lines
-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of MJ embd
Sent: Tuesday, September 17, 2013 10:37 PM
To: sun york-R58495
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] How do ARM platform initialize DDR?yes, I am using uboot for arndale board.
The code is written by samsung only and it is not static.The best option would be to have an eth / serial driver kind of arch which all soc vendors can share. But ddr is scattered, in absence of that, your point seems valid for fsl specific.
-mj
Quoted 9 lines · York Sun
Dear MJ,
Thanks for your reply.
I don't see the file in my copy. Probably it is not merged yet? Anyway, you just confirmed what I found so far. Do you use static setting in
dmc_init_ddr3.c? I mean does it adapt to different DDR speeds and modules (if applicable)?Quoted 49 lines
In my mind, I am thinking to restructure
arch/powerpc/cpu/mpc8xxx/ddr/to driver/ddr/fsl/ so the same driver can be shared as far as the DDR IP is the same (or similar).York
Quoted 38 lines · MJ embd
Hi York,
There is no generic driver. AFAIK. Having worked on both mpc85xx and ARM
I can tell you about samsung 5250. There are 2 uboots (one spl and other main).
In case of sd/mmc boot the internal rom copies the spl uboot to iRAM and the spl boot loader initialises the DDR3.you can check for
board/samsung/smdk5250/dmc_init_ddr3.c-Regards
mjQuoted 20 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Regards,
York
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot--
-mj
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Quoted 10 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Thinking back, as a rule of thumb, PowerPC has SPD I2C data available, usually. That's not the rule for ARM. One of a few choices happen:
1) ROM sets up DDR.
2) U-Boot/SPL sets up the DDR controller.
The problem is that the DDR controller is usually vendor-specific. Perhaps the flip-side here is that there's not so much a generic DDR driver for mpc85xx but simply one vendor for mpc85xx. Taking arch/powerpc/cpu/mpc85xx/ddr-gen3.c as what you're talking about, arch/arm/cpu/armv7/omap-common/emif-common.c would be an ARM-world example (the 'EMIF' is found on a large variety of TI parts, not just "omap" ones).
Quoted 9 lines
Regards,
York
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130919/137f83e6/attachment.pgp>
Quoted 13 lines · Tom Rini
Quoted 10 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Quoted 6 lines
Thinking back, as a rule of thumb, PowerPC has SPD I2C data available, usually. That's not the rule for ARM. One of a few choices happen:
1) ROM sets up DDR.
2) U-Boot/SPL sets up the DDR controller.
So for ARM platforms, the majority don't have the flexibility of using different DIMMs and/or clocks?
Quoted 7 lines
The problem is that the DDR controller is usually vendor-specific. Perhaps the flip-side here is that there's not so much a generic DDR driver for mpc85xx but simply one vendor for mpc85xx. Taking
arch/powerpc/cpu/mpc85xx/ddr-gen3.cas what you're talking about,arch/arm/cpu/armv7/omap-common/emif-common.cwould be an ARM-world example (the 'EMIF' is found on a large variety of TI parts, not just "omap" ones).
Does it make sense to share the Freescale DDR driver across ARM and Powerpc? Or does it make more sense to selectively copy the mpc8xxx DDR driver to Freescale ARM subfolder to start with. If the similarity sustains then we merge them into common driver. If not, we maintain two separated drivers.
For those who is not familiar with, Freescale is extending products to ARM cores. I am expecting peripherals stay relatively close, so many driver can be reused.
York
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 15 lines · York Sun
Quoted 14 lines · Tom Rini
Quoted 11 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Quoted 8 lines
Quoted 5 lines
Thinking back, as a rule of thumb, PowerPC has SPD I2C data available, usually. That's not the rule for ARM. One of a few choices happen: 1) ROM sets up DDR. 2) U-Boot/SPL sets up the DDR controller.
So for ARM platforms, the majority don't have the flexibility of using different DIMMs and/or clocks?
It's a different world. Again, thinking back to the PowerPC boards I've seen, they had "regular" DDR sockets. Most ARM boards don't. You can design your board with whatever, and I know in prototyping folks make do swapping chips in and out (and if you look at the omap code, you can see where we have code to calculate the timing values and print them, or use provided hard-coded values).
Quoted 15 lines
Quoted 8 lines
The problem is that the DDR controller is usually vendor-specific. Perhaps the flip-side here is that there's not so much a generic DDR driver for mpc85xx but simply one vendor for mpc85xx. Taking
arch/powerpc/cpu/mpc85xx/ddr-gen3.cas what you're talking about,arch/arm/cpu/armv7/omap-common/emif-common.cwould be an ARM-world example (the 'EMIF' is found on a large variety of TI parts, not just "omap" ones).Does it make sense to share the Freescale DDR driver across ARM and Powerpc? Or does it make more sense to selectively copy the mpc8xxx DDR driver to Freescale ARM subfolder to start with. If the similarity sustains then we merge them into common driver. If not, we maintain two separated drivers.
Quoted 3 lines
For those who is not familiar with, Freescale is extending products to ARM cores. I am expecting peripherals stay relatively close, so many driver can be reused.
I've been wondering when this would start to be visible. If we are able to share the DDR controller code between mpc85xx and the ARM stuff you're talking about, we'll have to sort out someplace within drivers/ to place it, to avoid #include nightmares I suspect. Other drivers should be easier to share at least :)
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSO22RAAoJENk4IS6UOR1WhJYQALM/XAMzPMMH4WJD8PkO7DqJ HB3WI2oopdm096Bfe8ZT2MPpuEm6OuIb/5HjacED0XxfCHT59NVxIo5tI51IEbqH 74k3LtvTMgADqVw092H3LsFFIJWPd0MsWCDian+NuAp8g03PK9eDOgczQujYflm/ cs6En1hYp+QolbxdHxpQ0HKwNxzA+bkT6JGzF2ziutp8P+wTHh5ypjtFCwF8h4cG IrGAhePYPHXZzCZYGRPWD0CXthcizXCuRCpykflEGpUsTOR0Cd/2UT0jBFh3aUCU jalrVG/LjhUWqO+IEzAhOtML4Z84oFLQQ5EBmwAOnt+ql6sxk2+L8kxEMWUzaE23 EppRrT7HDHI/Uc7ogeJP5JNjiYGmmp0dLhqIK3vIJ8pAyenj8TcOW2q0Y7eCrItN UPJNrYGLKXHC1f5OpfMSJG33lNRJY2oSI+D2ELENMtXBiC9y3nb8Lqar7GjJ6VQq BJcEbCNUT1IVqvCP/OsYKhtssqHdKYmjfSd9oOHonhwmZTqEyVh08/U1LIfIiYfa 7lody/RNVvnbUKjlojiBR6upJbfGC6YJSDQUzy02zf4gPNF01Q1rXO5fT6vfIa1z YVM5yV4MJ8F0Phma2uOk25NLgRmDcXeL4LCvpOOQUi3+ymMqMarmZwRdThARsBKh 1tFCkl3LA01CtGdZCzBI
=INiu
-----END PGP SIGNATURE-----
Dear York Sun,
Quoted 3 lines · In message <[email protected]> you wrote:
So for ARM platforms, the majority don't have the flexibility of using different DIMMs and/or clocks?
The majority of ARM systems are embedded designs which never use any kind of DIMM, but raw soldered-on RAM chips.
Quoted 3 lines
Does it make sense to share the Freescale DDR driver across ARM and Powerpc? Or does it make more sense to selectively copy the mpc8xxx DDR driver to Freescale ARM subfolder to start with. If the similarity
You are probably in a beter position to answer that than us - how many ARM systems are there around that use the same memory controller as the MPC8xxx?
Quoted 3 lines
For those who is not familiar with, Freescale is extending products to ARM cores. I am expecting peripherals stay relatively close, so many driver can be reused.
Well, I'm not sure which exact products you might have in mind here, but from what we've seen so far with the i.MX2x (and mxs), i.MX3x, iMX5x and i.MX6 systems, there are commnon IP blocks like the FEC, but so far I haven't seen this with the memory controller.
And I haven't seen any single FSL ARM board in our lab yet that was using any kind ot DIMM or such.
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "In Christianity neither morality nor religion come into contact with reality at any point." - Friedrich Nietzsche
Quoted 9 lines · Wolfgang Denk
Dear York Sun,
Quoted 3 lines · In message <[email protected]> you wrote:
So for ARM platforms, the majority don't have the flexibility of using different DIMMs and/or clocks?
The majority of ARM systems are embedded designs which never use any kind of DIMM, but raw soldered-on RAM chips.
That explains a lot.
Quoted 8 lines
Quoted 4 lines
Does it make sense to share the Freescale DDR driver across ARM and Powerpc? Or does it make more sense to selectively copy the mpc8xxx DDR driver to Freescale ARM subfolder to start with. If the similarity
You are probably in a beter position to answer that than us - how many ARM systems are there around that use the same memory controller as the MPC8xxx?
Zero as far as I know. But this is changing and this is why I brought it up. I don't want to maintain two set of drivers if not necessary.
Quoted 9 lines
Quoted 4 lines
For those who is not familiar with, Freescale is extending products to ARM cores. I am expecting peripherals stay relatively close, so many driver can be reused.
Well, I'm not sure which exact products you might have in mind here, but from what we've seen so far with the i.MX2x (and mxs), i.MX3x, iMX5x and i.MX6 systems, there are commnon IP blocks like the FEC, but so far I haven't seen this with the memory controller.
I hope I am not revealing a secret. :)
It has been announced that new SoCs are coming. It is still too early. But I am preparing software for it.
Quoted 4 lines
And I haven't seen any single FSL ARM board in our lab yet that was using any kind ot DIMM or such.
Thanks for confirmation. I will let you know once I learn what the board will look like (not very soon).
York
Quoted 25 lines · Tom Rini
Quoted 15 lines · York Sun
Quoted 14 lines · Tom Rini
Quoted 11 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Quoted 8 lines
Quoted 5 lines
Thinking back, as a rule of thumb, PowerPC has SPD I2C data available, usually. That's not the rule for ARM. One of a few choices happen: 1) ROM sets up DDR. 2) U-Boot/SPL sets up the DDR controller.
So for ARM platforms, the majority don't have the flexibility of using different DIMMs and/or clocks?
Quoted 6 lines
It's a different world. Again, thinking back to the PowerPC boards I've seen, they had "regular" DDR sockets. Most ARM boards don't. You can design your board with whatever, and I know in prototyping folks make do swapping chips in and out (and if you look at the omap code, you can see where we have code to calculate the timing values and print them, or use provided hard-coded values).
Understood. We may have boards with DIMM slots. I do see value of a fully functional DDR driver here.
Quoted 20 lines
Quoted 16 lines
Quoted 9 lines
The problem is that the DDR controller is usually vendor-specific. Perhaps the flip-side here is that there's not so much a generic DDR driver for mpc85xx but simply one vendor for mpc85xx. Taking
arch/powerpc/cpu/mpc85xx/ddr-gen3.cas what you're talking about,arch/arm/cpu/armv7/omap-common/emif-common.cwould be an ARM-world example (the 'EMIF' is found on a large variety of TI parts, not just "omap" ones).Does it make sense to share the Freescale DDR driver across ARM and Powerpc? Or does it make more sense to selectively copy the mpc8xxx DDR driver to Freescale ARM subfolder to start with. If the similarity sustains then we merge them into common driver. If not, we maintain two separated drivers.
Quoted 3 lines
For those who is not familiar with, Freescale is extending products to ARM cores. I am expecting peripherals stay relatively close, so many driver can be reused.
Quoted 6 lines
I've been wondering when this would start to be visible. If we are able to share the DDR controller code between mpc85xx and the ARM stuff you're talking about, we'll have to sort out someplace within
drivers/to place it, to avoid #include nightmares I suspect. Other drivers should be easier to share at least :)
I did a quick and dirty hack yesterday to move DDR driver to drivers/ddr/fsl. I had to change many #include <asm/????>.
York
Hi York,
I was thinking about your problem and this could be a solution mpc85xx uses a family of ddr controllers.
I believe they would be migrated to LayerScape,
Freescale has also i.mx4/5/6 series and coming i.mx8, that series uses/might use another ddr controller
Option1
As you suggested which looks a worthy option.
ddr/fsl/contoller1/ --- for 85xx
ddr/fsl/contoller2/ --- for I.mx
in your board config file, you might want to use
CONFIG_DDR_CONTROLLER_MPC85xx
or CONFIG_DDR_CONTROLLER_IMX
PS: I see no direct relation between ddr controller and core, also freescale is going core agnostic so I think the ddr controller be moved from cpu folder to driver/ddr folder.
-Regards
mj
Quoted 75 lines · York Sun
Quoted 25 lines · Tom Rini
Quoted 15 lines · York Sun
Quoted 14 lines · Tom Rini
Quoted 11 lines · York Sun
Albert,
Pardon me if this is a dumb question. I have been working on powerpc platforms in the past. Now we (the developers I work with) are exploring ARM cores. I am searching how memory is initialized and found different solutions. Some platforms have memory ready before u-boot even starts, some simply write to a set of registers. I understand many platforms don't share the IP of DDR controller. I am wondering if there is generic DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Quoted 8 lines
Quoted 5 lines
Thinking back, as a rule of thumb, PowerPC has SPD I2C data available, usually. That's not the rule for ARM. One of a few choices happen: 1) ROM sets up DDR. 2) U-Boot/SPL sets up the DDR controller.
So for ARM platforms, the majority don't have the flexibility of using different DIMMs and/or clocks?
Quoted 6 lines
It's a different world. Again, thinking back to the PowerPC boards I've seen, they had "regular" DDR sockets. Most ARM boards don't. You can design your board with whatever, and I know in prototyping folks make do swapping chips in and out (and if you look at the omap code, you can see where we have code to calculate the timing values and print them, or use provided hard-coded values).
Understood. We may have boards with DIMM slots. I do see value of a fully functional DDR driver here.
Quoted 20 lines
Quoted 16 lines
Quoted 9 lines
The problem is that the DDR controller is usually vendor-specific. Perhaps the flip-side here is that there's not so much a generic DDR driver for mpc85xx but simply one vendor for mpc85xx. Taking
arch/powerpc/cpu/mpc85xx/ddr-gen3.cas what you're talking about,arch/arm/cpu/armv7/omap-common/emif-common.cwould be an ARM-world example (the 'EMIF' is found on a large variety of TI parts, not just "omap" ones).Does it make sense to share the Freescale DDR driver across ARM and Powerpc? Or does it make more sense to selectively copy the mpc8xxx DDR driver to Freescale ARM subfolder to start with. If the similarity sustains then we merge them into common driver. If not, we maintain two separated drivers.
Quoted 3 lines
For those who is not familiar with, Freescale is extending products to ARM cores. I am expecting peripherals stay relatively close, so many driver can be reused.
Quoted 6 lines
I've been wondering when this would start to be visible. If we are able to share the DDR controller code between mpc85xx and the ARM stuff you're talking about, we'll have to sort out someplace within
drivers/to place it, to avoid #include nightmares I suspect. Other drivers should be easier to share at least :)I did a quick and dirty hack yesterday to move DDR driver to
drivers/ddr/fsl. I had to change many #include <asm/????>.York
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Signature · 1 line
-mj
Quoted 3 lines · York Sun
I am wondering if there is generic
DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.
Sadly, no such thing exists. There is no generic DDR controller for ARM. I'm working on DDR controller support for our ARM chips, and it's nowhere near as elegant as Freescale's PowerPC parts. In our case, we have firmware running in the chip that does DDR initialization and then loads u-boot.bin from a SPI flash into DDR, and then it boots the main processor.
Quoted 4 lines · Tom Rini
Thinking back, as a rule of thumb, PowerPC has SPD I2C data available, usually. That's not the rule for ARM. One of a few choices happen:
Even if you do have SPD on your ARM chip, that's still no guarantee that you can program the DDR controller properly. On our chips, we have to have a table of 300+ for each frequency that we support, and the SPD only lets us tweak a few registers to account for different size DIMMs.
Dear Timur,
Quoted 8 lines · In message <CAOZdJXVDf7Z7Ya8p4nkybp1wJ1cnMTs736cEtRNp_9yQYgQ68A@mail.gmail.com>…
Quoted 3 lines · York Sun
I am wondering if there is generic
DDR driver used by many ARM platforms, like the one we have for powerpc/mpc85xx SoCs.Sadly, no such thing exists. There is no generic DDR controller for ARM. I'm working on DDR controller support for our ARM chips, and it's nowhere near as elegant as Freescale's PowerPC parts. In our
MPC85xx is just one family of processors. And I don't think you really want to claim that all Freescale's PowerPC processors use the same memory controller? Try and compare the memory controllers (and the required initialization sequences) for just a selection of MPC8xx, MPC82xx, MPC83xx, MPC85xx.
And even if some parts use the same IP block, usually the register interfaces to it are sufficiently different to make common code a challenge at least (compare MPC5121 and MPC5125).
Yes, some of the later modes share more common IP blocks, but PowerPC is in no way better than ARM in this respect - the difference is only, that there are way more different ARM SoCs than there ver have been PPC ones, so the problems become more visible.
Best regards,
Wolfgang Denk
Signature · 4 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de A man is not complete until he is married -- then he is finished.
[U-Boot] When to create a SoC directory for ARM
In reply to Wolfgang DenkDear Wolfgang,
I failed to find the guideline, here is my question. Pardon me if this is a dump question as I am still new to ARM.
As David Feng post his patch set to add ARMv8 support, I am trying to enable it for Freescale implementation. Let's name it as LS2 for this discussion. I am thinking to reuse as much as possible for existing codes, which include copying some header files from powerpc partially. I noticed the SoC field in boards.cfg file and I am wondering how to use it effectively. I want to put LS2 specific headers to arch/arm/include/asm/arch-ls2. Do I need to copy all files from arch/arm/include/asm/arch-armv8/? There aren't many but I see mmu.h is included in start.S. I have been searching case like this in ARMv7 but didn't see shared header file (maybe I missed it). Please advise.
Regards,
York
[U-Boot] When to create a SoC directory for ARM
Quoted 5 lines · York Sun
Dear Wolfgang,
I failed to find the guideline, here is my question. Pardon me if this is a dump question as I am still new to ARM.
Quoted 10 lines
As David Feng post his patch set to add ARMv8 support, I am trying to enable it for Freescale implementation. Let's name it as LS2 for this discussion. I am thinking to reuse as much as possible for existing codes, which include copying some header files from powerpc partially. I noticed the SoC field in boards.cfg file and I am wondering how to use it effectively. I want to put LS2 specific headers to
arch/arm/include/asm/arch-ls2. Do I need to copy all files fromarch/arm/include/asm/arch-armv8/? There aren't many but I seemmu.his included instart.S. I have been searching case like this in ARMv7 but didn't see shared header file (maybe I missed it). Please advise.
LS2 is (or perhaps more accurately, contains) an implementation of ARMv8, so you should be using arch-armv8 rather than copying it.
-Scott
[U-Boot] When to create a SoC directory for ARM
Quoted 17 lines · Scott Wood
Quoted 5 lines · York Sun
Dear Wolfgang,
I failed to find the guideline, here is my question. Pardon me if this is a dump question as I am still new to ARM.
Quoted 10 lines
As David Feng post his patch set to add ARMv8 support, I am trying to enable it for Freescale implementation. Let's name it as LS2 for this discussion. I am thinking to reuse as much as possible for existing codes, which include copying some header files from powerpc partially. I noticed the SoC field in boards.cfg file and I am wondering how to use it effectively. I want to put LS2 specific headers to
arch/arm/include/asm/arch-ls2. Do I need to copy all files fromarch/arm/include/asm/arch-armv8/? There aren't many but I seemmu.his included instart.S. I have been searching case like this in ARMv7 but didn't see shared header file (maybe I missed it). Please advise.
Quoted 2 lines
LS2 is (or perhaps more accurately, contains) an implementation of ARMv8, so you should be using arch-armv8 rather than copying it.
True. But I guess LS2 won't be the only "LS" Freescale is going to make. Where is the best place to put the header file for chassis related registers, like CCSR we have for mpc8xxx. I am thinking the best place is arch/arm/include/asm/ls2 (or a better name). Like other ARMv7 variants, I am thinking to put ls2 under arch/arm/cpu/armv8/ as well, to host LS-specific code.
York
[U-Boot] When to create a SoC directory for ARM
Quoted 19 lines · On Wed, 2013-09-25 at 20:04 -0500, sun york-R58495 wrote:
Quoted 17 lines · Scott Wood
Quoted 15 lines · York Sun
Dear Wolfgang,
I failed to find the guideline, here is my question. Pardon me if this is a dump question as I am still new to ARM.
As David Feng post his patch set to add ARMv8 support, I am trying to enable it for Freescale implementation. Let's name it as LS2 for this discussion. I am thinking to reuse as much as possible for existing codes, which include copying some header files from powerpc partially. I noticed the SoC field in boards.cfg file and I am wondering how to use it effectively. I want to put LS2 specific headers to
arch/arm/include/asm/arch-ls2. Do I need to copy all files fromarch/arm/include/asm/arch-armv8/? There aren't many but I seemmu.his included instart.S. I have been searching case like this in ARMv7 but didn't see shared header file (maybe I missed it). Please advise.
Quoted 6 lines
Quoted 2 lines
LS2 is (or perhaps more accurately, contains) an implementation of ARMv8, so you should be using arch-armv8 rather than copying it.
True. But I guess LS2 won't be the only "LS" Freescale is going to make. Where is the best place to put the header file for chassis related registers, like CCSR we have for mpc8xxx.
Anything that isn't deeply tied to the ARM architecture should probably just go in include/.
Quoted 4 lines
I am thinking the
best place isarch/arm/include/asm/ls2(or a better name). Like other ARMv7 variants, I am thinking to put ls2 underarch/arm/cpu/armv8/as well, to host LS-specific code.
Likewise, if it's specifically tied to armv8 it should go in arch/arm/include/asm/arch-armv8, but I'm not sure what would be tied to both armv8 and ls2. Most likely anything LS-specific that needs to go under arch/arm/ should go somewhere like arch/arm/include/asm/ls/ (similar to arch/arm/include/asm/imx-common).
-Scott
[U-Boot] When to create a SoC directory for ARM
In reply to York SunDear York,
Quoted 5 lines · In message <[email protected]> you wrote:
As David Feng post his patch set to add ARMv8 support, I am trying to enable it for Freescale implementation. Let's name it as LS2 for this discussion. I am thinking to reuse as much as possible for existing codes, which include copying some header files from powerpc partially. I
Please do NOT copy files. If these are shared, then move them to a common location and make all code reference this.
Quoted 4 lines
noticed the SoC field in boards.cfg file and I am wondering how to use it effectively. I want to put LS2 specific headers to
arch/arm/include/asm/arch-ls2. Do I need to copy all files fromarch/arm/include/asm/arch-armv8/? There aren't many but I seemmu.his
Same here: never ever create copies of existing files. Movce them to a common location and make all code reference this single copy.
Best regards,
Wolfgang Denk
Signature · 4 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de 8 Catfish = 1 Octo-puss