RE: [PATCH] spi/s3c64xx: Log error interrupts

2011-12-06 Thread Kukjin Kim
Jassi Brar wrote: > > On Fri, Dec 2, 2011 at 5:16 PM, Linus Walleij > wrote: > > On Mon, Nov 28, 2011 at 12:31 PM, Mark Brown > > wrote: > > > >> Although the hardware supports interrupts we're not currently using > them > >> at all since for small transfers the overhead is greater than that for

Re: [PATCH] spi/s3c64xx: Log error interrupts

2011-12-02 Thread Jassi Brar
On Fri, Dec 2, 2011 at 5:16 PM, Linus Walleij wrote: > On Mon, Nov 28, 2011 at 12:31 PM, Mark Brown > wrote: > >> Although the hardware supports interrupts we're not currently using them >> at all since for small transfers the overhead is greater than that for >> busy waiting and for large transf

Re: [PATCH] spi/s3c64xx: Log error interrupts

2011-12-02 Thread Linus Walleij
On Mon, Nov 28, 2011 at 12:31 PM, Mark Brown wrote: > Although the hardware supports interrupts we're not currently using them > at all since for small transfers the overhead is greater than that for > busy waiting and for large transfers we have interrupts from the DMA. > This means that if the

[PATCH] spi/s3c64xx: Log error interrupts

2011-11-28 Thread Mark Brown
Although the hardware supports interrupts we're not currently using them at all since for small transfers the overhead is greater than that for busy waiting and for large transfers we have interrupts from the DMA. This means that if the hardware reports an error (especially one which might not stal

[PATCH] spi/s3c64xx: Log error interrupts

2011-11-10 Thread Mark Brown
Although the hardware supports interrupts we're not currently using them at all since for small transfers the overhead is greater than that for busy waiting and for large transfers we have interrupts from the DMA. This means that if the hardware reports an error (especially one which might not stal