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
On 28 March 2013 21:59, Mike Turquette mturque...@linaro.org 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
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
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,
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
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
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
On Thu, Mar 28, 2013 at 2:33 AM, Thomas Gleixner t...@linutronix.de 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
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
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
10 matches
Mail list logo
