Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver

2015-10-22 Thread Michael Turquette
Quoting Scott Wood (2015-10-09 16:57:44) > On Thu, 2015-10-01 at 19:26 -0500, Scott Wood wrote: > > [Resending to updated e-mail address] > > > > On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote: > > > Hi Scott, > > > > > > Quoting Scott Wood (2015-06-18 19:49:10) > > > > The existing

Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver

2015-10-09 Thread Scott Wood
On Thu, 2015-10-01 at 19:26 -0500, Scott Wood wrote: > [Resending to updated e-mail address] > > On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote: > > Hi Scott, > > > > Quoting Scott Wood (2015-06-18 19:49:10) > > > The existing device tree bindings are error-prone and inflexible. > >

Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver

2015-10-01 Thread Scott Wood
[Resending to updated e-mail address] On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote: > Hi Scott, > > Quoting Scott Wood (2015-06-18 19:49:10) > > The existing device tree bindings are error-prone and inflexible. > > Correct the mistake by moving the knowledge into the driver, which

Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver

2015-10-01 Thread Scott Wood
On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote: > Hi Scott, > > Quoting Scott Wood (2015-06-18 19:49:10) > > The existing device tree bindings are error-prone and inflexible. > > Correct the mistake by moving the knowledge into the driver, which > > has more flexibility in describing

Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver

2015-08-15 Thread Scott Wood
On Tue, 2015-08-11 at 11:25 -0700, Michael Turquette wrote: Hi Scott, Quoting Scott Wood (2015-06-18 19:49:10) The existing device tree bindings are error-prone and inflexible. Correct the mistake by moving the knowledge into the driver, which has more flexibility in describing the

Re: [RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver

2015-08-11 Thread Michael Turquette
Hi Scott, Quoting Scott Wood (2015-06-18 19:49:10) The existing device tree bindings are error-prone and inflexible. Correct the mistake by moving the knowledge into the driver, which has more flexibility in describing the quirks of each chip. This leaves the device tree to its proper role

[RFC PATCH 0/8] clk: qoriq: Move chip-specific knowledge into driver

2015-06-18 Thread Scott Wood
The existing device tree bindings are error-prone and inflexible. Correct the mistake by moving the knowledge into the driver, which has more flexibility in describing the quirks of each chip. This leaves the device tree to its proper role of identifying a programming interface rather than