[U-Boot] [PATCHv4 3/3] ARM64: poplar: hi3798cv200: u-boot support for Poplar 96Boards
Jorge Ramirez
jorge.ramirez-ortiz at linaro.org
Wed May 10 09:33:35 UTC 2017
On 05/10/2017 04:30 AM, Tom Rini wrote:
>> hey Tom, I am not sure how to move this forward really so let me
>> clarify where I think we stand:
>>
>> 1. The linux kernel does not need the clock property in the uart
>> nodes (only u-boot does: serial_pl01x.c needs fixing).
>> 2. ehci is not present in the linux kernel poplar dts yet but it
>> will be eventually.
>>
>> with this in mind, what is blocking the acceptance of the patchset?
>>
>> I can do v5 using the linux kernel dts as is and creating a
>> hi3798cv200-u-boot.dtsi that simply adds the nodes above (this time
>> no #include required:) )
>>
>> Then when ehci is added to the kernel, the ehci node can be removed
>> from u-boot.dtsi
>> And when uboot updates its pl01x.c serial driver, the uart0 node
>> can be removed and the u-boot.dtsi filed completely deleted.
> Can you take a stab at updating the pl01x driver? Thanks!
updating pl01x is not a big deal I dont think; however this will mean
requiring a platform specific clock driver to just use the pl01x - which
will take me some time to get into uboot for my platform (and the same
might happen to other users).
- if the issue for accepting the Poplar patchset is with the dts
modification I can revert to just not using OF for pl01x like other
platforms do.
- if the issue is that we wish to enforce each new platform to commit a
clock driver then I just need to plan for it (to be honest I didn't
envision this to be the case when all I need is to enable a uart)
maintaining full compatibility with the kernel's dts comes at a price so
just making sure that this is the direction we want to take (not just a
one off where I am the lucky one :) )
More information about the U-Boot
mailing list