linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] pinctrl: add a driver for Energy Micro's efm32 SoCs
Date: Mon, 12 Dec 2011 15:37:50 +0100	[thread overview]
Message-ID: <20111212143750.GA27267@pengutronix.de> (raw)
In-Reply-To: <CACRpkdYpq1phHTTLy875xSr-upiW5BmvKMPO_d-niG+-J14t9w@mail.gmail.com>

On Sat, Dec 10, 2011 at 01:18:43AM +0100, Linus Walleij wrote:
> On Fri, Dec 9, 2011 at 12:08 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> 
> > I still think it should be "I'm board Y, please set all my pins up for me"
> 
> This is basically what the current pinmux hog concept does.
> 
> > Drivers should not be bothered with pin muxing *at all*.
> 
> Not if they are simple. Like - set them up once and for all and
> then forget about it.
> 
> It gets problematic when we get to sleep states and the system
> need to reconfigure all pins on say idle or deep sleep.

If you need to reconfigure your pins in deep sleep and you control
the pins in the driver this seems to suggest that your device won't
suspend properly if the driver is not loaded?

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2011-12-12 14:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 22:40 [PATCH] [RFC] pinctrl: add a driver for Energy Micro's efm32 SoCs Uwe Kleine-König
2011-12-08 22:55 ` Arnd Bergmann
2011-12-09  9:23   ` Uwe Kleine-König
2011-12-09 13:55     ` Arnd Bergmann
2011-12-09 14:15       ` Uwe Kleine-König
2011-12-08 23:14 ` Stephen Warren
2011-12-09  1:01   ` Shawn Guo
2011-12-09  3:44     ` Stephen Warren
2011-12-09  4:32       ` Shawn Guo
2011-12-09  4:47         ` Stephen Warren
2011-12-09  5:14           ` Shawn Guo
2011-12-09 11:08             ` Sascha Hauer
2011-12-09 13:01               ` Uwe Kleine-König
2011-12-10  0:18               ` Linus Walleij
2011-12-12 14:37                 ` Sascha Hauer [this message]
2011-12-12 15:29                   ` Uwe Kleine-König
2011-12-13  0:41                   ` Linus Walleij
2011-12-09 16:53             ` Stephen Warren
2011-12-09 15:03           ` Dong Aisheng
2011-12-09 16:49             ` Stephen Warren
2011-12-09 17:24               ` Tony Lindgren
2011-12-09 17:53                 ` Tony Lindgren
2011-12-10  0:14                   ` Stephen Warren
2011-12-11 19:34                     ` Tony Lindgren
2011-12-09  9:31   ` Uwe Kleine-König
2011-12-10  0:04   ` Linus Walleij

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=20111212143750.GA27267@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).