[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1BAFE6F6C881BF42822005164F1491C33EBE4E07@DBDE04.ent.ti.com>
Date: Tue, 7 May 2013 10:47:31 +0000
From: "Hebbar, Gururaja" <gururaja.hebbar@...com>
To: Mark Brown <broonie@...nel.org>
CC: "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Grant Likely <grant.likely@...aro.org>,
"spi-devel-general@...ts.sourceforge.net"
<spi-devel-general@...ts.sourceforge.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] spi/omap2: Let device core handle pinctrl
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists