Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757962Ab3EGKr5 (ORCPT ); Tue, 7 May 2013 06:47:57 -0400 Received: from arroyo.ext.ti.com ([192.94.94.40]:51990 "EHLO arroyo.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757782Ab3EGKry convert rfc822-to-8bit (ORCPT ); Tue, 7 May 2013 06:47:54 -0400 From: "Hebbar, Gururaja" To: Mark Brown CC: "linux-omap@vger.kernel.org" , Grant Likely , "spi-devel-general@lists.sourceforge.net" , "linux-kernel@vger.kernel.org" Subject: RE: [PATCH] spi/omap2: Let device core handle pinctrl Thread-Topic: [PATCH] spi/omap2: Let device core handle pinctrl Thread-Index: AQHOSpEtMssOEU4sAUGUr3i0BAEdV5j5FsQg///PQ4CAAKQJQA== Date: Tue, 7 May 2013 10:47:31 +0000 Message-ID: <1BAFE6F6C881BF42822005164F1491C33EBE4E07@DBDE04.ent.ti.com> References: <1367868998-12667-1-git-send-email-broonie@opensource.wolfsonmicro.com> <1BAFE6F6C881BF42822005164F1491C33EBE473A@DBDE04.ent.ti.com> <20130507085535.GN7478@sirena.org.uk> In-Reply-To: <20130507085535.GN7478@sirena.org.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.24.170.142] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1277 Lines: 37 On Tue, May 07, 2013 at 14:25:35, Mark Brown wrote: > On Tue, May 07, 2013 at 03:56:09AM +0000, Hebbar, Gururaja wrote: > > > There are cases where driver('s) needs to place pin-mux's to sleep on suspend > > & default/idle on resume. For such cases Pinctrl needs to be handled inside > > the driver. Example [1]. > > Well, obviously - but at the minute the driver is pure boilerplate. Correct. > There's also been some discussion about factoring out the suspend/resume > code since it's going to get equally repetitive. Really. Any link/referenceso that I can follow. But I think each module will have its own work to do. May be I can confirm once I look at the factoring-out discussion. > > > I will be submitting a patch to enhance the existing pinctrl support for > > spi omap2 shortly which does above work. > > How soon is shortly? Since I am adding this Pinctrl PM mode support to many other drivers (i2c, cpsw, da8xx-fb, hsmmc, ti-pwm, usb ...), I would say Shortly = 1 week - 10 days. > Regards, Gururaja -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/