[U-Boot] [PATCH v2 3/4] mmc: zynq: Determine base clock frequency via clock framework
stefan at herbrechtsmeier.net
Mon Jan 2 15:02:15 CET 2017
Am 02.01.2017 um 08:00 schrieb Michal Simek:
> On 27.12.2016 11:10, Stefan Herbrechtsmeier wrote:
>> Hi Michal,
>> Am 28.11.2016 um 08:42 schrieb Michal Simek:
>>> Hi, +Siva,
>>> Moving current zynq clk driver to driver model shouldn't be that hard
>>> because all should be in place. and then you can keep just that
>>> if defined(CONFIG_CLK) part above.
>> I have port the CLK driver to DM but therefore I have to rework it and
>> remove the clk cmd support. I will post a tested version next week.
> ok. I want to know the reason why this is necessary.
The zynq clock driver save all data even the static clock tree and
unused information in an dynamic array. This needs much memory and
complicates the strip down for the SPL.
The clock framework doesn't support the clock command nor supplies the
names of clocks. If you prefer I could add the clock command
implementation to the DM zynq driver or keep clock driver specific data
in the mach directory.
Should I move everything in one patch or should I first remove some
function, move the clock driver and add functionality back?
More information about the U-Boot