Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Sören Brinkmann
On Mon, 2014-03-03 at 11:38AM -0800, Stephen Boyd wrote: > On 03/03/14 11:13, Sören Brinkmann wrote: > > On Mon, 2014-03-03 at 08:07PM +0100, Gerhard Sittig wrote: > >> On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: > >>> It would be nice if we could use the logic provided in the mux,

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Stephen Boyd
On 03/03/14 11:13, Sören Brinkmann wrote: > On Mon, 2014-03-03 at 08:07PM +0100, Gerhard Sittig wrote: >> On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: >>> It would be nice if we could use the logic provided in the mux, div etc >>> primitives independently of how the HW is accessed

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Sören Brinkmann
On Mon, 2014-03-03 at 08:07PM +0100, Gerhard Sittig wrote: > On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: > > > > It would be nice if we could use the logic provided in the mux, div etc > > primitives independently of how the HW is accessed and what is > > necessary to shift and

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Gerhard Sittig
On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: > > It would be nice if we could use the logic provided in the mux, div etc > primitives independently of how the HW is accessed and what is > necessary to shift and mask those register values around, right? I > mean, at then end we want

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Sören Brinkmann
On Sun, 2014-03-02 at 09:29PM +0100, Gerhard Sittig wrote: > On Fri, Feb 28, 2014 at 15:34 -0800, Soren Brinkmann wrote: > > > > [ MMIO registers assumed for clock control modules, but I2C > > communication may be involved in other hardware, individual for > > a (set of) clock(s) and not for an

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Sören Brinkmann
On Sun, 2014-03-02 at 09:29PM +0100, Gerhard Sittig wrote: On Fri, Feb 28, 2014 at 15:34 -0800, Soren Brinkmann wrote: [ MMIO registers assumed for clock control modules, but I2C communication may be involved in other hardware, individual for a (set of) clock(s) and not for an

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Gerhard Sittig
On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: It would be nice if we could use the logic provided in the mux, div etc primitives independently of how the HW is accessed and what is necessary to shift and mask those register values around, right? I mean, at then end we want to

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Sören Brinkmann
On Mon, 2014-03-03 at 08:07PM +0100, Gerhard Sittig wrote: On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: It would be nice if we could use the logic provided in the mux, div etc primitives independently of how the HW is accessed and what is necessary to shift and mask those

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Stephen Boyd
On 03/03/14 11:13, Sören Brinkmann wrote: On Mon, 2014-03-03 at 08:07PM +0100, Gerhard Sittig wrote: On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: It would be nice if we could use the logic provided in the mux, div etc primitives independently of how the HW is accessed and what

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-03 Thread Sören Brinkmann
On Mon, 2014-03-03 at 11:38AM -0800, Stephen Boyd wrote: On 03/03/14 11:13, Sören Brinkmann wrote: On Mon, 2014-03-03 at 08:07PM +0100, Gerhard Sittig wrote: On Mon, Mar 03, 2014 at 09:35 -0800, Sören Brinkmann wrote: It would be nice if we could use the logic provided in the mux, div etc

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-02 Thread Gerhard Sittig
On Fri, Feb 28, 2014 at 15:34 -0800, Soren Brinkmann wrote: > > [ MMIO registers assumed for clock control modules, but I2C > communication may be involved in other hardware, individual for > a (set of) clock(s) and not for an architecture or platform ] > > Does anybody have a good idea how we

Re: [PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-03-02 Thread Gerhard Sittig
On Fri, Feb 28, 2014 at 15:34 -0800, Soren Brinkmann wrote: [ MMIO registers assumed for clock control modules, but I2C communication may be involved in other hardware, individual for a (set of) clock(s) and not for an architecture or platform ] Does anybody have a good idea how we could

[PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-02-28 Thread Soren Brinkmann
Hi, I recently ran into a problem which seems to become common. I was trying to write a driver for the TI CDCE913, a programmable clock synthesizer on the I2C bus. Internally that device consists of a PLL and a bunch of muxes, gates and dividers that eventually end up in three clock outputs.

[PATCH RFC 0/3] clk: CCF clock primitives + custom IO accessors

2014-02-28 Thread Soren Brinkmann
Hi, I recently ran into a problem which seems to become common. I was trying to write a driver for the TI CDCE913, a programmable clock synthesizer on the I2C bus. Internally that device consists of a PLL and a bunch of muxes, gates and dividers that eventually end up in three clock outputs.