Hi,
On Fri, Nov 21, 2014 at 01:28:43AM +0400, Alexander Kochetkov 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
On Sun, Nov 23, 2014 at 04:18:40PM +0300, Alexander Kochetkov wrote:
>
> 23 нояб. 2014 г., в 7:43, Felipe Balbi написал(а):
>
> > maybe there was a typo? I tested on v3.18-rc3 :-)
>
> I do my tests on kernel from angstrom with almost all i2c-omap patches
> backported from linux/master.
> Then
On Sun, Nov 23, 2014 at 04:18:40PM +0300, Alexander Kochetkov wrote:
23 нояб. 2014 г., в 7:43, Felipe Balbi ba...@ti.com написал(а):
maybe there was a typo? I tested on v3.18-rc3 :-)
I do my tests on kernel from angstrom with almost all i2c-omap patches
backported from linux/master.
Hi,
On Fri, Nov 21, 2014 at 01:28:43AM +0400, Alexander Kochetkov 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
23 нояб. 2014 г., в 7:43, Felipe Balbi написал(а):
> maybe there was a typo? I tested on v3.18-rc3 :-)
I do my tests on kernel from angstrom with almost all i2c-omap patches
backported from linux/master.
Then I rebased them to wrong (old) kernel version and posted to the list.
Angstrom
23 нояб. 2014 г., в 7:43, Felipe Balbi ba...@ti.com написал(а):
maybe there was a typo? I tested on v3.18-rc3 :-)
I do my tests on kernel from angstrom with almost all i2c-omap patches
backported from linux/master.
Then I rebased them to wrong (old) kernel version and posted to the list.
On Sat, Nov 22, 2014 at 07:02:22PM +0100, Wolfram Sang wrote:
> On Sat, Nov 22, 2014 at 05:06:10PM +0300, Alexander Kochetkov wrote:
> >
> > 22 нояб. 2014 г., в 16:23, Wolfram Sang написал(а):
> >
> > > Huh, I can't apply this one? Which kernel version is this based on?
> >
> > v.3.13-rc8
>
>
On Sat, Nov 22, 2014 at 05:06:10PM +0300, Alexander Kochetkov wrote:
>
> 22 нояб. 2014 г., в 16:23, Wolfram Sang написал(а):
>
> > Huh, I can't apply this one? Which kernel version is this based on?
>
> v.3.13-rc8
Wow, that's old. Can you please rebase the series on top of 3.18-rc4? Or
my
22 нояб. 2014 г., в 16:23, Wolfram Sang написал(а):
> Huh, I can't apply this one? Which kernel version is this based on?
v.3.13-rc8
It depends on PATCH 1/4
alexander@ubuntu:git.kernel.org.pub.scm.linux.kernel.git.stable.linux-stable$
git log --pretty=oneline --abbrev-commit -6
204c058 i2c:
On Fri, Nov 21, 2014 at 10:08:08AM -0600, Felipe Balbi wrote:
> On Fri, Nov 21, 2014 at 01:28:43AM +0400, Alexander Kochetkov 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 Fri, Nov 21, 2014 at 10:08:08AM -0600, Felipe Balbi wrote:
On Fri, Nov 21, 2014 at 01:28:43AM +0400, Alexander Kochetkov 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
22 нояб. 2014 г., в 16:23, Wolfram Sang w...@the-dreams.de написал(а):
Huh, I can't apply this one? Which kernel version is this based on?
v.3.13-rc8
It depends on PATCH 1/4
alexander@ubuntu:git.kernel.org.pub.scm.linux.kernel.git.stable.linux-stable$
git log --pretty=oneline --abbrev-commit
On Sat, Nov 22, 2014 at 05:06:10PM +0300, Alexander Kochetkov wrote:
22 нояб. 2014 г., в 16:23, Wolfram Sang w...@the-dreams.de написал(а):
Huh, I can't apply this one? Which kernel version is this based on?
v.3.13-rc8
Wow, that's old. Can you please rebase the series on top of
On Sat, Nov 22, 2014 at 07:02:22PM +0100, Wolfram Sang wrote:
On Sat, Nov 22, 2014 at 05:06:10PM +0300, Alexander Kochetkov wrote:
22 нояб. 2014 г., в 16:23, Wolfram Sang w...@the-dreams.de написал(а):
Huh, I can't apply this one? Which kernel version is this based on?
v.3.13-rc8
On Fri, Nov 21, 2014 at 01:28:43AM +0400, Alexander Kochetkov 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
On Fri, Nov 21, 2014 at 01:28:43AM +0400, Alexander Kochetkov 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 transfer
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 transfer started when BB=0 and bus is busy wouldn't be completed by IP
and results in
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 transfer started when BB=0 and bus is busy wouldn't be completed by IP
and results in
18 matches
Mail list logo
