Quoting Mark Brown (2015-01-18 05:41:24)
> On Sun, Jan 18, 2015 at 11:54:56AM +0100, Krzysztof Kozlowski wrote:
> > W dniu 18.01.2015 o 07:30, Tomasz Figa pisze:
>
> > >So, the question is, do we actually have hardware that _really_
> > >requires _actual_ preparation or all the clk_prepare_enable(
On Sun, Jan 18, 2015 at 11:54:56AM +0100, Krzysztof Kozlowski wrote:
> W dniu 18.01.2015 o 07:30, Tomasz Figa pisze:
> >So, the question is, do we actually have hardware that _really_
> >requires _actual_ preparation or all the clk_prepare_enable()s in I2C
> >drivers (at least in i2c-s3c2410) are
W dniu 18.01.2015 o 07:30, Tomasz Figa pisze:
Hi,
[CCing more people]
2015-01-16 23:39 GMT+09:00 Paul Osmialowski :
This enhancement of i2c API is designed to address following problem
caused by circular lock dependency:
-> #1 (prepare_lock){+.+.+.}:
[2.730502][] __lock_acquire+0x
Hi,
[CCing more people]
2015-01-16 23:39 GMT+09:00 Paul Osmialowski :
> This enhancement of i2c API is designed to address following problem
> caused by circular lock dependency:
>
> -> #1 (prepare_lock){+.+.+.}:
> [2.730502][] __lock_acquire+0x3c0/0x8a4
> [2.735970][] loc
This enhancement of i2c API is designed to address following problem
caused by circular lock dependency:
-> #1 (prepare_lock){+.+.+.}:
[2.730502][] __lock_acquire+0x3c0/0x8a4
[2.735970][] lock_acquire+0x6c/0x8c
[2.741090][] mutex_lock_nested+0x68/0x464
[2.74