From: Mark Brown <broonie@kernel.org>
To: "Hebbar, Gururaja" <gururaja.hebbar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Grant Likely <grant.likely@linaro.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi/omap2: Let device core handle pinctrl
Date: Tue, 7 May 2013 09:55:35 +0100 [thread overview]
Message-ID: <20130507085535.GN7478@sirena.org.uk> (raw)
In-Reply-To: <1BAFE6F6C881BF42822005164F1491C33EBE473A@DBDE04.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
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.
There's also been some discussion about factoring out the suspend/resume
code since it's going to get equally repetitive.
> I will be submitting a patch to enhance the existing pinctrl support for
> spi omap2 shortly which does above work.
How soon is shortly?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-07 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 19:36 Mark Brown
2013-05-07 3:56 ` Hebbar, Gururaja
2013-05-07 8:55 ` Mark Brown [this message]
2013-05-07 10:47 ` Hebbar, Gururaja
2013-05-10 9:56 ` Mark Brown
2013-05-13 6:25 ` Hebbar, Gururaja
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130507085535.GN7478@sirena.org.uk \
--to=broonie@kernel.org \
--cc=grant.likely@linaro.org \
--cc=gururaja.hebbar@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®