Hello, Tony!
24.11.2014 22:47, Tony Lindgren t...@atomide.com *:
If you post a patch, I can test boot with it. Looks like the failing
ones have i2c rev3.3 on 34xx vs rev4.4 on 36xx.
So I doubt we just want to change the test for for a higher rev number
for OMAP_I2C_REV_ON_3430_3530.
You
* Alexander Kochetkov al.koc...@gmail.com [141124 16:11]:
24 нояб. 2014 г., в 23:05, Alexander Kochetkov al.koc...@gmail.com
написал(а):
Something (u-boot, may be) leave the bus in the wrong state.
Really strange.
Actually something wrong with i2c-pullups on i2c.1 bus on fault
On Mon, Nov 24, 2014 at 11:08:48AM -0800, Kevin Hilman wrote:
On Sat, Nov 22, 2014 at 11:47 AM, Alexander Kochetkov
al.koc...@gmail.com wrote:
In a multimaster environment, after IP software reset, BB-bit value doesn't
correspond to the current bus state. It may happen what BB-bit will be 0,
On Mon, Nov 24, 2014 at 01:10:23PM -0600, Felipe Balbi wrote:
On Mon, Nov 24, 2014 at 11:08:48AM -0800, Kevin Hilman wrote:
On Sat, Nov 22, 2014 at 11:47 AM, Alexander Kochetkov
al.koc...@gmail.com wrote:
In a multimaster environment, after IP software reset, BB-bit value
doesn't
On Sat, Nov 22, 2014 at 11:47 AM, Alexander Kochetkov
al.koc...@gmail.com wrote:
In a multimaster environment, after IP software reset, BB-bit value doesn't
correspond to the current bus state. It may happen what BB-bit will be 0,
while the bus is busy due to another I2C master activity.
Any
* Wolfram Sang w...@the-dreams.de [141124 11:14]:
On Mon, Nov 24, 2014 at 01:10:23PM -0600, Felipe Balbi wrote:
On Mon, Nov 24, 2014 at 11:08:48AM -0800, Kevin Hilman wrote:
On Sat, Nov 22, 2014 at 11:47 AM, Alexander Kochetkov
al.koc...@gmail.com wrote:
In a multimaster environment,
24 нояб. 2014 г., в 22:08, Kevin Hilman khil...@kernel.org написал(а):
This patch recently hit linux-next (as commit 903c3859f77f) and boot
breakage[1] in next-20141124 on OMAP3530 Beagle and Overo/Tobi boards
was bisected down to this commit.
Kevin
[1]
* Alexander Kochetkov al.koc...@gmail.com [141124 11:41]:
24 нояб. 2014 г., в 22:08, Kevin Hilman khil...@kernel.org написал(а):
This patch recently hit linux-next (as commit 903c3859f77f) and boot
breakage[1] in next-20141124 on OMAP3530 Beagle and Overo/Tobi boards
was bisected down
Guys, I really sorry for that :(
Just try to boot it with your patch? :)
Yes, may be two-three times (max).
Something (u-boot, may be) leave the bus in the wrong state.
Really strange.
But the test function should not loop forever in any case I take?
It doesn't loop forever. It finish with
24 нояб. 2014 г., в 22:47, Tony Lindgren t...@atomide.com написал(а):
I'd say by Tuesday as we have multiple automated test systems failing
as soon as people update their trees. And when they are failing, we
may miss other breakage happening in linux next.
Fix:
24 нояб. 2014 г., в 23:05, Alexander Kochetkov al.koc...@gmail.com написал(а):
Something (u-boot, may be) leave the bus in the wrong state.
Really strange.
Actually something wrong with i2c-pullups on i2c.1 bus on fault boards.
May be these are boards without pull-ups?
All beagles doesn't
11 matches
Mail list logo
