On 11/27/2013 07:12 PM, Enric Balletbo Serra wrote:
Hi all,
2013/11/27 Nikita Kiryanov :
On 11/27/2013 06:10 PM, Thomas Petazzoni wrote:
Dear Nikita Kiryanov,
On Wed, 27 Nov 2013 17:52:31 +0200, Nikita Kiryanov wrote:
The zeroing of the cnt register also happens in other places in the
driv
Hi Tom,
> On Wed, Nov 27, 2013 at 06:01:18PM +0200, Lubomir Popov wrote:
>> Hi Nikita,all,
>>
>> On 27-Nov-13 17:52, Nikita Kiryanov wrote:
>> >On 11/27/2013 05:28 PM, Thomas Petazzoni wrote:
>> >>Dear Nikita Kiryanov,
>> >>
>> >>On Wed, 27 Nov 2013 16:52:56 +0200, Nikita Kiryanov wrote:
>> >>
>>
Hi all,
2013/11/27 Nikita Kiryanov :
> On 11/27/2013 06:10 PM, Thomas Petazzoni wrote:
>>
>> Dear Nikita Kiryanov,
>>
>> On Wed, 27 Nov 2013 17:52:31 +0200, Nikita Kiryanov wrote:
>>
>>> The zeroing of the cnt register also happens in other places in the
>>> driver, and it is entirely possible tha
On 11/27/2013 06:10 PM, Thomas Petazzoni wrote:
Dear Nikita Kiryanov,
On Wed, 27 Nov 2013 17:52:31 +0200, Nikita Kiryanov wrote:
The zeroing of the cnt register also happens in other places in the
driver, and it is entirely possible that they should be removed for
OMAP3s as well.
In my patch
On Wed, Nov 27, 2013 at 06:01:18PM +0200, Lubomir Popov wrote:
> Hi Nikita,all,
>
> On 27-Nov-13 17:52, Nikita Kiryanov wrote:
> >On 11/27/2013 05:28 PM, Thomas Petazzoni wrote:
> >>Dear Nikita Kiryanov,
> >>
> >>On Wed, 27 Nov 2013 16:52:56 +0200, Nikita Kiryanov wrote:
> >>
> >Not sure to un
Dear Nikita Kiryanov,
On Wed, 27 Nov 2013 17:52:31 +0200, Nikita Kiryanov wrote:
> The zeroing of the cnt register also happens in other places in the
> driver, and it is entirely possible that they should be removed for
> OMAP3s as well.
>
> In my patch I removed it only for i2c_write() because
Hi Nikita,all,
On 27-Nov-13 17:52, Nikita Kiryanov wrote:
On 11/27/2013 05:28 PM, Thomas Petazzoni wrote:
Dear Nikita Kiryanov,
On Wed, 27 Nov 2013 16:52:56 +0200, Nikita Kiryanov wrote:
Not sure to understand your question: my paragraph above mentions the
IGEP board as being the platform on
On 11/27/2013 05:28 PM, Thomas Petazzoni wrote:
Dear Nikita Kiryanov,
On Wed, 27 Nov 2013 16:52:56 +0200, Nikita Kiryanov wrote:
Not sure to understand your question: my paragraph above mentions the
IGEP board as being the platform on which I'm seeing this. So indeed, a
OMAP3-based board is af
Hi Thomas
On Wed, Nov 27, 2013 at 4:35 PM, Thomas Petazzoni
wrote:
> Dear Tom Rini,
>
> On Wed, 27 Nov 2013 09:45:55 -0500, Tom Rini wrote:
>
>> > I see that 960187ffa125b3938fec4b827bd9e8c04a204af8 ("ARM: OMAP: I2C:
>> > New read, write and probe functions") has changed significantly the
>> > OM
Dear Tom Rini,
On Wed, 27 Nov 2013 09:45:55 -0500, Tom Rini wrote:
> > I see that 960187ffa125b3938fec4b827bd9e8c04a204af8 ("ARM: OMAP: I2C:
> > New read, write and probe functions") has changed significantly the
> > OMAP I2C driver. And it turns out that reverting this commit actually
> > fixes
Dear Nikita Kiryanov,
On Wed, 27 Nov 2013 16:52:56 +0200, Nikita Kiryanov wrote:
> >> Not sure to understand your question: my paragraph above mentions the
> >> IGEP board as being the platform on which I'm seeing this. So indeed, a
> >> OMAP3-based board is affected. But maybe I misunderstood yo
On 11/27/2013 04:22 PM, Enric Balletbo Serra wrote:
Hi Thomas,
2013/11/27 Thomas Petazzoni :
Dear Enric Balletbo Serra,
On Wed, 27 Nov 2013 14:56:15 +0100, Enric Balletbo Serra wrote:
2013/11/27 Thomas Petazzoni :
Hello,
We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
I
On 11/27/2013 04:22 PM, Enric Balletbo Serra wrote:
Hi Thomas,
2013/11/27 Thomas Petazzoni :
Dear Enric Balletbo Serra,
On Wed, 27 Nov 2013 14:56:15 +0100, Enric Balletbo Serra wrote:
2013/11/27 Thomas Petazzoni :
Hello,
We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
I
Dear Enric Balletbo Serra,
On 11/27/2013 03:22 PM, Enric Balletbo Serra wrote:
> 2013/11/27 Thomas Petazzoni :
>> On Wed, 27 Nov 2013 14:56:15 +0100, Enric Balletbo Serra wrote:
>>> 2013/11/27 Thomas Petazzoni :
We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
IGEP boa
On Wed, Nov 27, 2013 at 01:19:29PM +0100, Thomas Petazzoni wrote:
> Hello,
>
> We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
> IGEP boards (OMAP3 based, U-Boot shows "OMAP36XX/37XX-GP ES1.2"), and
> we're seeing random I2C communication problems at startup.
>
> Most of the
Hi Thomas,
2013/11/27 Thomas Petazzoni :
> Dear Enric Balletbo Serra,
>
> On Wed, 27 Nov 2013 14:56:15 +0100, Enric Balletbo Serra wrote:
>
>> 2013/11/27 Thomas Petazzoni :
>> > Hello,
>> >
>> > We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
>> > IGEP boards (OMAP3 based, U-Bo
Dear Enric Balletbo Serra,
On Wed, 27 Nov 2013 14:56:15 +0100, Enric Balletbo Serra wrote:
> 2013/11/27 Thomas Petazzoni :
> > Hello,
> >
> > We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
> > IGEP boards (OMAP3 based, U-Boot shows "OMAP36XX/37XX-GP ES1.2"), and
> > we're see
Hi Thomas,
CC'ing Javier Martínez
2013/11/27 Thomas Petazzoni :
> Hello,
>
> We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
> IGEP boards (OMAP3 based, U-Boot shows "OMAP36XX/37XX-GP ES1.2"), and
> we're seeing random I2C communication problems at startup.
>
Right, I've rep
Hello,
We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our
IGEP boards (OMAP3 based, U-Boot shows "OMAP36XX/37XX-GP ES1.2"), and
we're seeing random I2C communication problems at startup.
Most of the time it's just:
"""
Out: serial
Err: serial
i2c_write: pads on bus 0 probabl
19 matches
Mail list logo
