From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [PATCH 11/20] dm: serial: Update binding for PL01x serial UART Date: Wed, 15 Jul 2015 11:00:59 +0200 Message-ID: References: <1436324032-17931-1-git-send-email-sjg@chromium.org> <1436324032-17931-12-git-send-email-sjg@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <1436324032-17931-12-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Simon Glass , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" Cc: U-Boot Mailing List , Stephen Warren , Stephen Warren , Joe Hershberger , Masahiro Yamada , Masahiro Yamada , Marek Vasut , Tom Rini , Albert Aribaud , Vikas Manocha , Pavel Herrmann List-Id: devicetree@vger.kernel.org On Wed, Jul 8, 2015 at 4:53 AM, Simon Glass wrote: > This binding differs from that of Linux. Update it and change existing > users. > > Signed-off-by: Simon Glass I'm confused by this. Isn't devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Date: Wed, 15 Jul 2015 11:00:59 +0200 Subject: [U-Boot] [PATCH 11/20] dm: serial: Update binding for PL01x serial UART In-Reply-To: <1436324032-17931-12-git-send-email-sjg@chromium.org> References: <1436324032-17931-1-git-send-email-sjg@chromium.org> <1436324032-17931-12-git-send-email-sjg@chromium.org> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Jul 8, 2015 at 4:53 AM, Simon Glass wrote: > This binding differs from that of Linux. Update it and change existing > users. > > Signed-off-by: Simon Glass I'm confused by this. Isn't devicetree at 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