Switch internal registers address to 0xF1 on Armada 370/XP
Get series with b4
b4 am 20130522233108.01cb51f0@skateVersions newest first
- v1 Latest0 of 9 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 9 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/9] Switch internal registers address to 0xF1 on Armada 370/XP
Dear Arnd Bergmann,
Quoted 11 lines · Arnd Bergmann
Quoted 7 lines
So you're proposing to add two
Kconfigoptions, one to have the UART at0xd0012000and the other one to have the UART at0xf1012000. The user would have to know whether he is going to boot with an old bootloader or new bootloader, and select the appropriate option. This means that themvebu_defconfigwould no longer be able to have earlyprintk enabled by default, otherwise the resulting kernel may not boot for some people, but maybe it's a reasonable tradeoff.Yes. It may also be reasonable to use the CP15 hack for
DEBUG_LL, but I would not like to see that information getting used anywhere in the kernel outside ofDEBUG_LL. That should really come from the DT.
Ok.
Quoted 7 lines
Quoted 7 lines
Conclusion: you can't classify on one side boards that are at
0xd0and boards that are at0xf1. It depends on which bootloader each particular instance of those boards will be using. Will it be a bootloader that complies with the "old" protocol (CP15 bit cleared and registers at0xd0) or the "new" protocol (CP15 bit set and registers at0xf1).
Quoted 7 lines
Quoted 3 lines
So we can't encode into the boards Device Tree whether the registers are at
0xd0or0xf1, because it's not a board-related information, but a bootloader-related information.The new boot loaders will of course know that they are remapping the registers, so they are also able to put the correct information into the DT.
The thing that I believe you don't realize is that those new bootloaders are already shipping *today*. And they are not putting whatever "correct" information into the DT you believe they should be putting.
So what do we do, today, with those new bootloaders, that are not the future, but the present. Again, they do *not* add any information in the DT that allows us to know that they have remapped the registers to 0xf1.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com