Re: OMAP4 Panda DVI problem

[Tomi Valkeinen <tomi.valkeinen@ti.com>]

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

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".

If DVI driver wanted to use the regulator, it'd need to get
"hsusbX_vcc". Which, I presume, would work, but is board specific and
hacky, and it makes handling EPROBE_DEFER a bit more difficult.

Then again, maybe that's still simpler than making the regulator
always-on, as there are complications with that approach also, which we
are currently studying.

>>> So I think the simplest solution is to make DC_HST_5V always-on. This
>>> should be fixed for 3.10 also.
>>
>> I am fine with this.
> 
> For a short term fix I'm fine with that, but please investigate using
> the regulator, it might be simpler than you think.

I'll have a look, maybe there's something I'm missing.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]