Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-02-25 Thread Mike Turquette
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

Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-02-25 Thread Mike Turquette
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()s in I2C

Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-18 Thread Mark Brown
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

Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-18 Thread Krzysztof Kozlowski
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][]

Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-18 Thread Krzysztof Kozlowski
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 p.osmialo...@samsung.com: This enhancement of i2c API is designed to address following problem caused by circular lock dependency: - #1 (prepare_lock){+.+.+.}: [2.730502]

Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-18 Thread Mark Brown
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 just

Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-17 Thread Tomasz Figa
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][]

Re: [RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-17 Thread Tomasz Figa
Hi, [CCing more people] 2015-01-16 23:39 GMT+09:00 Paul Osmialowski p.osmialo...@samsung.com: This enhancement of i2c API is designed to address following problem caused by circular lock dependency: - #1 (prepare_lock){+.+.+.}: [2.730502][c0061e50] __lock_acquire+0x3c0/0x8a4 [

[RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-16 Thread 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][] lock_acquire+0x6c/0x8c [2.741090][] mutex_lock_nested+0x68/0x464 [

[RFC 1/3] i2c: Enhancement of i2c API to address circular lock dependency problem

2015-01-16 Thread Paul Osmialowski
This enhancement of i2c API is designed to address following problem caused by circular lock dependency: - #1 (prepare_lock){+.+.+.}: [2.730502][c0061e50] __lock_acquire+0x3c0/0x8a4 [2.735970][c0062868] lock_acquire+0x6c/0x8c [2.741090][c04a2724]