Hi!
[I was waiting for a comment from Rob for the initial submission,
but that never came and I nearly forgot. Instead of pinging again,
I'm resubmitting with the review comment from Guenter fixed, hoping
that Rob will react this time.]
This is a workaround for a problem in the AT91 I2C adapt
Hi Peter,
On Wed, Oct 25, 2017 at 11:40:50PM +0200, Peter Rosin wrote:
> Hi Ludovic,
>
> On 2017-10-17 09:58, Ludovic Desroches wrote:
> > Hi Peter,
> >
> > On Fri, Oct 13, 2017 at 05:01:04PM +0200, Peter Rosin wrote:
> >> On 2017-10-13 15:29, Alan Cox wrote:
> >>> On Thu, 12 Oct 2017 13:35:17 +
Hi Ludovic,
On 2017-10-17 09:58, Ludovic Desroches wrote:
> Hi Peter,
>
> On Fri, Oct 13, 2017 at 05:01:04PM +0200, Peter Rosin wrote:
>> On 2017-10-13 15:29, Alan Cox wrote:
>>> On Thu, 12 Oct 2017 13:35:17 +0200
>>> Peter Rosin wrote:
>>>
Hi!
I have encountered an "interesting"
Hi Peter,
On Fri, Oct 13, 2017 at 05:01:04PM +0200, Peter Rosin wrote:
> On 2017-10-13 15:29, Alan Cox wrote:
> > On Thu, 12 Oct 2017 13:35:17 +0200
> > Peter Rosin wrote:
> >
> >> Hi!
> >>
> >> I have encountered an "interesting" bug. It silently corrupts data
> >> and is generally nasty...
> >
On 2017-10-13 15:29, Alan Cox wrote:
> On Thu, 12 Oct 2017 13:35:17 +0200
> Peter Rosin wrote:
>
>> Hi!
>>
>> I have encountered an "interesting" bug. It silently corrupts data
>> and is generally nasty...
>>
>> On an I2C bus, driven by the at91 driver and DMA (an Atmel
>> sama5d31 chip), I have
On Thu, 12 Oct 2017 13:35:17 +0200
Peter Rosin wrote:
> Hi!
>
> I have encountered an "interesting" bug. It silently corrupts data
> and is generally nasty...
>
> On an I2C bus, driven by the at91 driver and DMA (an Atmel
> sama5d31 chip), I have an 256 byte eeprom (NXP SE97BTP). I'm using
> Li
Hi!
This is a workaround for a problem in the AT91 I2C adapter driver
(or perhaps the hardware?) when it drives the TWI peripheral on an
Atmel sama5d3 chip as I2C.
Apparently, that driver can delay in excess of 100 ms just after
the transfer of the 7th bit of the last byte. When it does this
the
On 10/12/2017 02:19 PM, Peter Rosin wrote:
On 2017-10-12 16:42, Guenter Roeck wrote:
On 10/12/2017 07:32 AM, Peter Rosin wrote:
On 2017-10-12 13:35, Peter Rosin wrote:
Hi!
I have encountered an "interesting" bug. It silently corrupts data
and is generally nasty...
On an I2C bus, driven by th
On 2017-10-12 16:42, Guenter Roeck wrote:
> On 10/12/2017 07:32 AM, Peter Rosin wrote:
>> On 2017-10-12 13:35, Peter Rosin wrote:
>>> Hi!
>>>
>>> I have encountered an "interesting" bug. It silently corrupts data
>>> and is generally nasty...
>>>
>>> On an I2C bus, driven by the at91 driver and DMA
On 10/12/2017 07:32 AM, Peter Rosin wrote:
On 2017-10-12 13:35, Peter Rosin wrote:
Hi!
I have encountered an "interesting" bug. It silently corrupts data
and is generally nasty...
On an I2C bus, driven by the at91 driver and DMA (an Atmel
sama5d31 chip), I have an 256 byte eeprom (NXP SE97BTP)
On 2017-10-12 13:35, Peter Rosin wrote:
> Hi!
>
> I have encountered an "interesting" bug. It silently corrupts data
> and is generally nasty...
>
> On an I2C bus, driven by the at91 driver and DMA (an Atmel
> sama5d31 chip), I have an 256 byte eeprom (NXP SE97BTP). I'm using
> Linux v4.13.
>
>
Hi!
I have encountered an "interesting" bug. It silently corrupts data
and is generally nasty...
On an I2C bus, driven by the at91 driver and DMA (an Atmel
sama5d31 chip), I have an 256 byte eeprom (NXP SE97BTP). I'm using
Linux v4.13.
The at24 driver for the eeprom detects that the I2C adapter
12 matches
Mail list logo
