From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anton Habegger Subject: Re: Patch to parameterize =?utf-8?b?RE1BX01JTl9CWVRFUw==?= for omap2-mcspi Date: Tue, 31 May 2016 05:03:16 +0000 (UTC) Message-ID: References: <1426741501.10003.6.camel@midgaarde> <550AC256.4070509@ti.com> <550AF7F6.7080200@ti.com> <1426786080.13824.23.camel@symus-gk-mint> <550C1979.5030208@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: Sender: linux-spi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Hi I'm interessted about the state of the patch? I have a similar situation with a am3352 device and 10kHz SPI transfer. (Kernel version 4.1) The number of bytes to transfer are in between of 3 and 30. The SPI worker thread occupies the CPU with ~60% load. With a DMA_MIN_BYTES = 10, the CPU load will be reduced to 10%, which is still to much in my opinion. Are there other workarounds or options to get rid of busy waits with omap2-mcspi? -- To unsubscribe from this list: send the line "unsubscribe linux-spi" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html