Re: [PATCH v3 2/4] i2c: mpc: Interrupt driven transfer

2021-04-13 Thread Chris Packham
On 14/04/21 10:28 am, Chris Packham wrote: > > On 14/04/21 1:52 am, Andy Shevchenko wrote: >> On Tue, Apr 13, 2021 at 8:10 AM Chris Packham >> wrote: >>> The fsl-i2c controller will generate an interrupt after every byte >>> transferred. Make use of this interrupt to drive a state machine which

Re: [PATCH v3 2/4] i2c: mpc: Interrupt driven transfer

2021-04-13 Thread Chris Packham
On 14/04/21 1:52 am, Andy Shevchenko wrote: > On Tue, Apr 13, 2021 at 8:10 AM Chris Packham > wrote: >> The fsl-i2c controller will generate an interrupt after every byte >> transferred. Make use of this interrupt to drive a state machine which >> allows the next part of a transfer to happen as

Re: [PATCH v3 2/4] i2c: mpc: Interrupt driven transfer

2021-04-13 Thread Andy Shevchenko
On Tue, Apr 13, 2021 at 8:10 AM Chris Packham wrote: > > The fsl-i2c controller will generate an interrupt after every byte > transferred. Make use of this interrupt to drive a state machine which > allows the next part of a transfer to happen as soon as the interrupt is > received. This is

Re: [PATCH v3 2/4] i2c: mpc: Interrupt driven transfer

2021-04-13 Thread Wolfram Sang
On Tue, Apr 13, 2021 at 05:09:53PM +1200, Chris Packham wrote: > The fsl-i2c controller will generate an interrupt after every byte > transferred. Make use of this interrupt to drive a state machine which > allows the next part of a transfer to happen as soon as the interrupt is > received. This

[PATCH v3 2/4] i2c: mpc: Interrupt driven transfer

2021-04-12 Thread Chris Packham
The fsl-i2c controller will generate an interrupt after every byte transferred. Make use of this interrupt to drive a state machine which allows the next part of a transfer to happen as soon as the interrupt is received. This is particularly helpful with SMBUS devices like the LM81 which will