Skip to contentSkip to conversation

vdds_dsi doesn't exist on all omap3430 arch chip

DISCUSSION stanley.miao 3 participants 5 messages Mar 4, 2010 – Mar 5, 2010 Framebuffer layer

lore
Share & tools
lore
#2 lore raw
Quoted 14 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Tomi Valkeinen
Sent: Thursday, March 04, 2010 4:07 PM
To: ext stanley.miao
Cc: [email protected]; [email protected]
Subject: Re: vdds_dsi doesn't exist on all omap3430 arch chip

Hi,

Quoted 2 lines · ext stanley.miao

Hi, Tomi,

Quoted 9 lines
Quoted 2 lines

The commit below:
http://www.gitorious.org/linux-omap-

dss2/linux/commit/ec70668fa99b2dd0d305fbdb451a728f2e2a4c58

Quoted 1 line

doesn't apply to ti_omap_am3517. There is no "vdds_dsi" on am3517.

DSS hardware seems to require vdds_dsi power on OMAP3 chips. You need to add it to the board file's regulator configuration. Or do you mean that on am3517 there's no power connected to OMAP's vdds_dsi line?

[Hiremath, Vaibhav] Tomi,

Currently we do have only one EVM for AM3517 available in the market and which doesn't support DSI interface, so there is no DSI power source available or required. Also the power chip being used is low cost which doesn't have these many sources available.

At-least for our internal release, the quick solution I did is, I have encapsulated the regulator_* API calls under !cpu_is_omap3517() && !cpu_is_omap3505().

The ideal solution would be to take the input from board hook up part for power supply also, that way we can support OMAP3 based various EVM's where we have different power chip. Since I am busy with some other high priority issues, I will be able to take this up after this only.

Thanks,
Vaibhav

Quoted 7 lines

Tomi

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
Quoted 22 lines · Vaibhav
Quoted 13 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Tomi Valkeinen
Sent: Thursday, March 04, 2010 4:07 PM
To: ext stanley.miao
Cc: [email protected]; [email protected]
Subject: Re: vdds_dsi doesn't exist on all omap3430 arch chip

Hi,

Quoted 2 lines · ext stanley.miao

Hi, Tomi,

Quoted 9 lines
Quoted 2 lines

The commit below:
http://www.gitorious.org/linux-omap-

dss2/linux/commit/ec70668fa99b2dd0d305fbdb451a728f2e2a4c58

Quoted 1 line

doesn't apply to ti_omap_am3517. There is no "vdds_dsi" on am3517.

DSS hardware seems to require vdds_dsi power on OMAP3 chips. You need to add it to the board file's regulator configuration. Or do you mean that on am3517 there's no power connected to OMAP's vdds_dsi line?

Quoted 7 lines

[Hiremath, Vaibhav] Tomi,

Currently we do have only one EVM for AM3517 available in the market and which doesn't support DSI interface, so there is no DSI power source available or required. Also the power chip being used is low cost which doesn't have these many sources available.

At-least for our internal release, the quick solution I did is, I have encapsulated the regulator_* API calls under !cpu_is_omap3517() && !cpu_is_omap3505().

The ideal solution would be to take the input from board hook up part for power supply also, that way we can support OMAP3 based various EVM's where we have different power chip. Since I am busy with some other high priority issues, I will be able to take this up after this only.

Hmm okay, so what is AM3517 exactly =)?

An OMAP-like SoC, with the same DSS block as on OMAP?

I think this power issue should be asked from some TI HW guy who can tell us what is going on there. If OMAP3430 requires vdds_dsi power to power all the pins (and this is still unclear, although it is the current assumption), then which OMAP variants need the power and which do not?

Also something related I've been wondering: Different OMAP versions have different DSS features. Currently we check these features by checking what OMAP version we're running on.

But there is a readable revision number in the DSS HW blocks, and if that could be used to choose which features are available, it'd be a much better solution. TRM doesn't mention these revision numbers. I wonder if TI has a list of DSS revisions...

Tomi

#4 lore raw
Quoted 43 lines

-----Original Message-----
From: Tomi Valkeinen [mailto:[email protected]]
Sent: Thursday, March 04, 2010 9:45 PM
To: Hiremath, Vaibhav
Cc: ext stanley.miao; [email protected]; linux- [email protected]
Subject: RE: vdds_dsi doesn't exist on all omap3430 arch chip

Quoted 18 lines · Vaibhav
Quoted 18 lines

-----Original Message-----
From: [email protected] [mailto:linux-omap- [email protected]] On Behalf Of Tomi Valkeinen
Sent: Thursday, March 04, 2010 4:07 PM
To: ext stanley.miao
Cc: [email protected]; [email protected]
Subject: Re: vdds_dsi doesn't exist on all omap3430 arch chip

Hi,

Quoted 4 lines · ext stanley.miao

Hi, Tomi,

The commit below:
http://www.gitorious.org/linux-omap-

dss2/linux/commit/ec70668fa99b2dd0d305fbdb451a728f2e2a4c58

Quoted 1 line

doesn't apply to ti_omap_am3517. There is no "vdds_dsi" on am3517.

Quoted 7 lines
Quoted 4 lines

DSS hardware seems to require vdds_dsi power on OMAP3 chips. You need to add it to the board file's regulator configuration. Or do you mean that on am3517 there's no power connected to OMAP's vdds_dsi line?

[Hiremath, Vaibhav] Tomi,

Currently we do have only one EVM for AM3517 available in the market and

which doesn't support DSI interface, so there is no DSI power source available or required. Also the power chip being used is low cost which doesn't have these many sources available.

Quoted 2 lines

At-least for our internal release, the quick solution I did is, I have

encapsulated the regulator_* API calls under !cpu_is_omap3517() && !cpu_is_omap3505().

Quoted 1 line
Quoted 8 lines
Quoted 1 line

The ideal solution would be to take the input from board hook up part for

power supply also, that way we can support OMAP3 based various EVM's where we have different power chip. Since I am busy with some other high priority issues, I will be able to take this up after this only.

Hmm okay, so what is AM3517 exactly =)?

An OMAP-like SoC, with the same DSS block as on OMAP?

[Hiremath, Vaibhav] Yes, this is an OMAP-like SoC with some new IP addition and some got removed. But the DSS block is exactly same as OMAP3.

Quoted 7 lines

I think this power issue should be asked from some TI HW guy who can tell us what is going on there. If OMAP3430 requires vdds_dsi power to power all the pins (and this is still unclear, although it is the current assumption), then which OMAP variants need the power and which do not?

[Hiremath, Vaibhav] I will take this issue and explore more on this, but as I said will be able to spend time after next week only.

Quoted 8 lines

Also something related I've been wondering: Different OMAP versions have different DSS features. Currently we check these features by checking what OMAP version we're running on.

But there is a readable revision number in the DSS HW blocks, and if that could be used to choose which features are available, it'd be a much better solution. TRM doesn't mention these revision numbers. I wonder if TI has a list of DSS revisions...

[Hiremath, Vaibhav] Yes you are right, TRM doesn't talk about it. I will try to get further details on this.

Thanks,
Vaibhav

Quoted 3 lines

Tomi