[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130510095629.GM3200@sirena.org.uk>
Date: Fri, 10 May 2013 10:56:29 +0100
From: Mark Brown <broonie@...nel.org>
To: "Hebbar, Gururaja" <gururaja.hebbar@...com>
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 10:47:31AM +0000, Hebbar, Gururaja wrote:
> On Tue, May 07, 2013 at 14:25:35, Mark Brown wrote:
> > 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.
It was part of the threads where the idea of adding the helper for the
boilerplate stuff to the core was discussed initially IIRC.
> > > 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.
Well, I guess I'll keep the patch for now and drop it when you send out
the PM code.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists