I recently came across an ar7 device which has the vlynq hardwired so that the clocks...

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