public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>,
	linux-omap <linux-omap@vger.kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Powering OMAP's pins
Date: Tue, 25 Sep 2012 13:21:14 +0300	[thread overview]
Message-ID: <1348568474.2342.35.camel@deskari> (raw)

[-- Attachment #1: Type: text/plain, Size: 468 bytes --]

Hi Tony,

Each pin of OMAP requires a particular power to be enabled for the pin
to function (Ball Characteristics table from data manual). Is there a
plan how this is managed with pinctrl? Currently each driver needs to
make sure the correct regulators are enabled for the pins it uses, which
is platform specific and messy.

As a driver maintainer, I would wish that the pins would just get
enabled automatically when I call pm_runtime_get()...

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-09-25 10:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 10:21 Tomi Valkeinen [this message]
2012-09-25 15:38 ` Powering OMAP's pins Tony Lindgren
2012-09-25 17:05   ` Tomi Valkeinen
2012-09-25 19:07     ` Tony Lindgren
2012-09-26  7:05       ` Tomi Valkeinen
2012-09-26 18:59         ` Tony Lindgren
2012-09-27  7:18           ` Tomi Valkeinen
2012-09-27 18:43             ` Tony Lindgren
2012-09-27 18:51               ` Tony Lindgren
2012-09-28  6:13                 ` Tomi Valkeinen
2012-09-28 14:37                   ` Tony Lindgren
2012-09-26 11:46     ` Linus Walleij
2012-09-26 12:56       ` Tomi Valkeinen
2012-09-26 13:27         ` Linus Walleij
2012-09-26 19:03           ` Tony Lindgren

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=1348568474.2342.35.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=peter.ujfalusi@ti.com \
    --cc=tony@atomide.com \
    /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