| 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
| ||
|
Message-Id: <201312091648.13802.arnd@arndb.de> Date: Mon, 9 Dec 2013 16:48:13 +0100 From: Arnd Bergmann <arnd@...db.de> To: boris brezillon <b.brezillon@...rkiz.com> Cc: linux-arm-kernel@...ts.infradead.org, Russell King <linux@....linux.org.uk>, Nicolas Ferre <nicolas.ferre@...el.com>, Mike Turquette <mturquette@...aro.org>, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v4 3/6] ARM: at91/dt: define sama5d3 clocks On Monday 09 December 2013, boris brezillon wrote: > > You are adding "clock-names" properties in a lot of cases. Are you sure you > > are using the strings that are documented in the respective device bindings > > for each name? In a lot of cases, drivers just want an anonymous clock > > and we don't name them. > > I rechecked it, and almost all drivers call [devm_]clk_get with a > specific clock > name, and as a result we must specify the "clock-names" property. > The only exceptions I found are the spi and PIT (Periodic Interval > Timer) drivers, > and "clock-names" property is not defined in these nodes. Yes, I understood that the *drivers* use the names, but are they actually documented in the device bindings? If not, it might be better to change the drivers. Arnd -- 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