Re: [PATCH v4 2/5] mfd: dt: ranges, #address-cells and #size-cells as optional properties

2017-01-04 Thread Lee Jones
On Tue, 20 Dec 2016, Andrew Jeffery wrote: > Whilst describing a device and not a bus, simple-mfd is modelled on > simple-bus where child nodes are iterated and registered as platform > devices. Some complex devices, e.g. the Aspeed LPC controller, can > benefit from address space mapping such

Re: [PATCH v4 2/5] mfd: dt: ranges, #address-cells and #size-cells as optional properties

2017-01-04 Thread Lee Jones
On Tue, 20 Dec 2016, Andrew Jeffery wrote: > Whilst describing a device and not a bus, simple-mfd is modelled on > simple-bus where child nodes are iterated and registered as platform > devices. Some complex devices, e.g. the Aspeed LPC controller, can > benefit from address space mapping such

[PATCH v4 2/5] mfd: dt: ranges, #address-cells and #size-cells as optional properties

2016-12-19 Thread Andrew Jeffery
Whilst describing a device and not a bus, simple-mfd is modelled on simple-bus where child nodes are iterated and registered as platform devices. Some complex devices, e.g. the Aspeed LPC controller, can benefit from address space mapping such that child nodes can use the regs property to describe

[PATCH v4 2/5] mfd: dt: ranges, #address-cells and #size-cells as optional properties

2016-12-19 Thread Andrew Jeffery
Whilst describing a device and not a bus, simple-mfd is modelled on simple-bus where child nodes are iterated and registered as platform devices. Some complex devices, e.g. the Aspeed LPC controller, can benefit from address space mapping such that child nodes can use the regs property to describe