On Wed, Apr 13, 2016 at 07:30:15AM +0200, Stefan Roese wrote: > On 12.04.2016 21:27, Mark Brown wrote: > >Writing something in the DT won't magically configure anything in the > >hardware which is (as I said) the bit I'm missing. > The MBus driver (drivers/bus/mvebu-mbus.c) takes care of the MBus > window mapping. This is done, if the board dts files has one (or > multiple) entries for the SPI device(s) added to the 'ranges' > property of the 'soc' node. I'm still unclear how mapping the windows in results in connecting the windows to the SPI block. It also seems like we need to document what the meaning of the reg properties of the device is, it's all very well saying that there's a generic MBus binding but we still need to say how the device will interpret the MBus windows that it has (assuming they are configured to specific hardware functions transparently).
Attachment:
signature.asc
Description: PGP signature
