Re: [PATCH 2/2] clk: allow reentrant calls into the clk framework

2013-04-02 Thread Ulf Hansson
On 28 March 2013 21:59, Mike Turquette wrote: > Reentrancy into the clock framework is necessary for clock operations > that result in nested calls to the clk api. A common example is a clock > that is prepared via an i2c transaction, such as a clock inside of a > discrete audio chip or a power m

[PATCH 2/2] clk: allow reentrant calls into the clk framework

2013-03-28 Thread Mike Turquette
Reentrancy into the clock framework is necessary for clock operations that result in nested calls to the clk api. A common example is a clock that is prepared via an i2c transaction, such as a clock inside of a discrete audio chip or a power management IC. The i2c subsystem itself will use the cl

Re: [PATCH 2/2] clk: allow reentrant calls into the clk framework

2013-03-28 Thread Mike Turquette
On Thu, Mar 28, 2013 at 2:33 AM, Thomas Gleixner wrote: > On Wed, 27 Mar 2013, Mike Turquette wrote: > >> Reentrancy into the clock framework is necessary for clock operations >> that result in nested calls to the clk api. A common example is a clock >> that is prepared via an i2c transaction, su

Re: [PATCH 2/2] clk: allow reentrant calls into the clk framework

2013-03-28 Thread Thomas Gleixner
On Wed, 27 Mar 2013, Mike Turquette wrote: > Reentrancy into the clock framework is necessary for clock operations > that result in nested calls to the clk api. A common example is a clock > that is prepared via an i2c transaction, such as a clock inside of a > discrete audio chip or a power mana

[PATCH 2/2] clk: allow reentrant calls into the clk framework

2013-03-27 Thread Mike Turquette
Reentrancy into the clock framework is necessary for clock operations that result in nested calls to the clk api. A common example is a clock that is prepared via an i2c transaction, such as a clock inside of a discrete audio chip or a power management IC. The i2c subsystem itself will use the cl