From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH 3/3] spi/s3c64xx: Implement runtime PM support Date: Sat, 21 Jan 2012 14:18:05 +0000 Message-ID: <20120121141804.GB10751@opensource.wolfsonmicro.com> References: <20120121132329.GA10751@opensource.wolfsonmicro.com> <1327152265-10789-1-git-send-email-broonie@opensource.wolfsonmicro.com> <1327152265-10789-3-git-send-email-broonie@opensource.wolfsonmicro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from opensource.wolfsonmicro.com ([80.75.67.52]:34893 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751775Ab2AUOSK (ORCPT ); Sat, 21 Jan 2012 09:18:10 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: Bill Gatliff Cc: Grant Likely , Linus Walleij , spi-devel-general@lists.sourceforge.net, linux-samsung-soc@vger.kernel.org On Sat, Jan 21, 2012 at 02:41:59PM +0100, Bill Gatliff wrote: > What about using autosuspend instead? If a client is doing a lot of > closely-spaced SPI transactions on a relatively flat device tree, > might the resulting runtime suspend/resume overhead between each > transaction become noticeable? It seems very low overhead, particularly in the context of the overhead of the SPI transactions themselves. I have sometimes wondered if it might be an idea to just make the core do something along these lines by default as there should be very few cases where it's important to have the suspend happen immediately.