From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: Powering OMAP's pins
Date: Wed, 26 Sep 2012 12:03:03 -0700 [thread overview]
Message-ID: <20120926190302.GH4840@atomide.com> (raw)
In-Reply-To: <CACRpkdZN8MnoFvj3yjs=yy7=HqWAp4Dgs8hS9RqR0hmmSe4QJw@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [120926 06:28]:
> On Wed, Sep 26, 2012 at 2:56 PM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
> > [Me]
> >> You can very well do clocks and regulators in these functions as well.
> >
> > That's not really what I mean. The regulators in question are OMAP
> > version specific, so the driver shouldn't know which regulators are
> > needed.
>
> So then it can't be done in generic code atleast, and it becomes a
> matter for the OMAP driver, I guess you're referring to
> Tony's pinctrl-single?
Yes the pins are muxed with pinctrl-single. Then for the SoC specific
regulator handling I suggest you use regulator names that make sense
from the driver point of view that can be mapped in SoC specific way
in the .dts files.
If you need SoC specific more complicated handling, you may want
to have SoC specific glue driver to the DSS core driver, like
dss-44xx.c etc. Then you can select the appropriate glue layer
based on the compatible flag.
Regards,
Tony
prev parent reply other threads:[~2012-09-26 19:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 10:21 Powering OMAP's pins Tomi Valkeinen
2012-09-25 15:38 ` 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 [this message]
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=20120926190302.GH4840@atomide.com \
--to=tony@atomide.com \
--cc=linus.walleij@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).