> What do you mean "driver fails to load"? You control the driver, don't
> you?
It is a thin wrapper around the mvebu driver, which does all the real
work. So no, Chris does not really control what the core of the driver
does.
The existing binding documentation says:
* Marvell Armada 37xx SoC pin and gpio controller
Each Armada 37xx SoC come with two pin and gpio controller one for
the south bridge and the other for the north bridge.
Inside this set of register the gpio latch allows exposing some
configuration of the SoC and especially the clock frequency of the
xtal. Hence, this node is a represent as syscon allowing sharing
the register between multiple hardware block.
So the syscon is there to allow the clock driver to share the register
space.
Andrew
