netdev - mvebu: Can we make the orion-mdio clock a requirement?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 21 Jul 2014 16:06:15 -0300
From:	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
To:	netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Cc:	Jason Cooper <jason@...edaemon.net>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Gregory Clement <gregory.clement@...e-electrons.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Andrew Lunn <andrew@...n.ch>, netdev@...r.kernel.org
Subject: mvebu: Can we make the orion-mdio clock a requirement?

Helly everyone,

Currently the mvmdio driver does not require a clock to be declared,
and instead this is optional.

However (almost) all the platforms that currently use it, i.e. the
Armada, Kirkwood and Dove SoCs, require some clock to be enabled before
the MDIO registers can be accessed.

The Orion5x SoC doesn't declare any clock for neither the ethernet node,
nor the MDIO node. Is that correct?

Do you think we could make the clock a required property in the mvmdio
devicetree node? How would that behave in the non-DT case?

Thanks,
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html