On Wed, Jul 8, 2015 at 4:53 AM, Simon Glass <s...@chromium.org> wrote:
> This binding differs from that of Linux. Update it and change existing
> users.
>
> Signed-off-by: Simon Glass <s...@chromium.org>
I'm confused by this. Isn't devicet...@vger.kernel.org the place to discuss
device tree bindings? This is sent only to the U-Boot list, does this mean
that there will now be *two* ontologies for DT bindings? That sounds like
a recepie for ... something not good.
> +- clock-frequency:
> + Input clock frequency for UART.
This is the real trick is it not?
Is the real commit blurb for this patch something like:
"we want a simple way to look up the clock frequency for our serial
ports during early boot, and following clocks = <&...> phandles
is too much trouble and might imply having to implement a whole
clock framework in U-Boot so we just see a lot of trouble, instead
provide a default frequency here"
I suggest in that case, instead do this:
- boot-frequency:
input clock frequency at boot time, to be used by boot loaders
and other early access.
This would be good for early Linux stuff as well I believe and I
do not think it's very controversial.
Yours,
Linus Walleij
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
