I recently came across an ar7 device which has the vlynq hardwired
authorFlorian Fainelli <florian@openwrt.org>
Mon, 25 May 2009 13:13:10 +0000 (13:13 +0000)
committerFlorian Fainelli <florian@openwrt.org>
Mon, 25 May 2009 13:13:10 +0000 (13:13 +0000)
commitaa508422a14c3d3de608e22ec4d94aa383aa1176
tree26fa97e257f3168ed01e0484c676ea35a2e6af1c
parent26853e56510e2aef8552eeff600adf4840db97f4
I recently came across an ar7 device which has the vlynq hardwired
so that the clocks are always generated by the remote device
instead of the local one.

Upon initialization the current version of vlynq driver disables
remote clock generation and causes the entire bus to hang on my
device.

This patch adds support for detecting which device (local or remote)
is responsible of clock generation and implements clock
initialization based on detection result.

Signed-off-by: Antti Seppala <a.seppala at gmail.com>
SVN-Revision: 16049
target/linux/ar7/files/drivers/vlynq/vlynq.c