I recently came across an ar7 device which has the vlynq hardwired so that the clocks...
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)
commit3b92b4de00a6e22c473ae72eec5834072e3f0e89
treee4af1e11c01f521ba655e403f36310b0d255b332
parent04bca7b528c9697d604c4ab88464b9604fe84be3
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