From: Roger Quadros <rogerq@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: OMAP4 Panda DVI problem
Date: Mon, 17 Jun 2013 14:37:36 +0300 [thread overview]
Message-ID: <51BEF500.4080308@ti.com> (raw)
In-Reply-To: <51BEF2BF.3000104@ti.com>
On 06/17/2013 02:27 PM, Tomi Valkeinen wrote:
> On 17/06/13 14:18, Tony Lindgren wrote:
>
>> You should be able to get the regulator based on the name just fine
>> from the drivers even if one driver is using DT and one is not. That is
>> as long as the regulator is defined. Then the regulator fwk will track
>> the usecount properly.
>
> Doesn't the regulator need to be "bound" to a device for the driver to
> use the proper name for the regulator? I mean, in this case the dvi
> driver wants to get a regulator named "vdd_5v" (or something like that,
> I'm not sure what's the proper name). The USB host driver uses a name
> "vcc", while the real name of the regulator is "hsusbX_vcc".
Right. I think if the regulator is not bound to any device then you can
get it just by supply name.
http://lxr.free-electrons.com/source/drivers/regulator/core.c#L1175
But the USB PHY driver will always try to get the regulator for it's device
that has supply name "vcc".
cheers,
-roger
prev parent reply other threads:[~2013-06-17 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 13:52 OMAP4 Panda DVI problem Tomi Valkeinen
2013-06-17 8:12 ` Roger Quadros
2013-06-17 11:18 ` Tony Lindgren
2013-06-17 11:27 ` Tomi Valkeinen
2013-06-17 11:35 ` Tony Lindgren
2013-06-17 11:37 ` Roger Quadros [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=51BEF500.4080308@ti.com \
--to=rogerq@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).