lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 7 Jun 2013 13:51:31 +0800 From: Shawn Guo <shawn.guo@...aro.org> To: Mike Turquette <mturquette@...aro.org> CC: <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>, <devicetree-discuss@...ts.ozlabs.org> Subject: Re: [PATCH RFC 0/3] clk: dt: bindings for mux & divider clocks Mike, On Mon, Jun 03, 2013 at 10:53:07AM -0700, Mike Turquette wrote: > I am using this code while converting the OMAP4 clock data over to DT I see these basic clk bindings can be useful for platforms that have a relatively simple clock tree, but I'm a little surprised that you plan to move OMAP4 to it. I'm wondering how many nodes you will have to add to OMAP4 device tree. For imx6q example, it means ~200 nodes addition to device tree, which is obviously a bloating of device tree. Shawn > and some common boilerplate code can be factored out of several clock > drivers if this is merged. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists