Re: [PATCH 4/7] clk: mvebu: cp110: introduce a new binding

2017-05-23 Thread Rob Herring
On Fri, May 19, 2017 at 05:55:22PM +0200, Gregory CLEMENT wrote: > The initial intent when the binding of the cp110 system controller was to > have one flat node. The idea being that what is currently a clock-only > driver in drivers would become a MFD driver, exposing the clock, GPIO and >

Re: [PATCH 4/7] clk: mvebu: cp110: introduce a new binding

2017-05-23 Thread Rob Herring
On Fri, May 19, 2017 at 05:55:22PM +0200, Gregory CLEMENT wrote: > The initial intent when the binding of the cp110 system controller was to > have one flat node. The idea being that what is currently a clock-only > driver in drivers would become a MFD driver, exposing the clock, GPIO and >

[PATCH 4/7] clk: mvebu: cp110: introduce a new binding

2017-05-19 Thread Gregory CLEMENT
The initial intent when the binding of the cp110 system controller was to have one flat node. The idea being that what is currently a clock-only driver in drivers would become a MFD driver, exposing the clock, GPIO and pinctrl functionality. However, after taking a step back, this would lead to a

[PATCH 4/7] clk: mvebu: cp110: introduce a new binding

2017-05-19 Thread Gregory CLEMENT
The initial intent when the binding of the cp110 system controller was to have one flat node. The idea being that what is currently a clock-only driver in drivers would become a MFD driver, exposing the clock, GPIO and pinctrl functionality. However, after taking a step back, this would lead to a