From: Igor Grinberg <grinberg@compulab.co.il>
To: Ilya Yanok <yanok@emcraft.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, sasha_d@emcraft.com
Subject: Re: [PATCH 2/2] mt_ventoux: support for TeeJet Mt.Ventoux board
Date: Tue, 03 Jan 2012 11:48:06 +0200 [thread overview]
Message-ID: <4F02CED6.8090709@compulab.co.il> (raw)
In-Reply-To: <4EFA4E9C.30307@emcraft.com>
Hi Ilya,
On 12/28/11 01:02, Ilya Yanok wrote:
> On 27.12.2011 11:56, Igor Grinberg wrote:
>>> +/*
>>> + * use fake regulator for vdds_dsi as we can't find this pin inside
>>> + * AM3517 datasheet.
>>> + */
>>> +static struct regulator_consumer_supply mt_ventoux_vdds_dsi_supply[] = {
>>> + REGULATOR_SUPPLY("vdds_dsi", "omapdss"),
>>> + REGULATOR_SUPPLY("vdds_dsi", "omapdss_dsi.0"),
>>> +};
>>
>> Although the TRM states that there is a vdds_dsi signal,
>> it looks, from the datasheet, that VDDSHV is used to power the DSS.
>> Either way, it can't be switched off, I think...
>> Therefore, depending on your board wiring, you can leave it as fixed
>> regulator or bind to a supply on TPS65023.
>
> I will forward this info to hardware guys and ask about wiring. For now
> I will leave it as is. Thanks for this information it turned to be some
> kind of mystery. It would be great if you could give some pointer to the
> datasheet regarding VDDSHV and DSS.
Well, there is no direct pointer to that information, but
I've found these facts:
1) the "Ball Characteristics" tables state that the DSS related pins
(and also many others) are powered by the VDDSHV.
2) the estimated power consumption of VDDSHV is the largest after the
VDD_CORE, which is typical for DSS, but it is also one of the largest
power domains, so I guess this cannot be a valid argument ;-)
3) On the "Voltage domains" diagram, only the VDD_CORE is exposed and
DSS is not listed in it, but there are other domains which are not
exposed... (this only can exclude the DSS from VDD_CORE, but not
absolutely, as datasheets can have mistakes or just not give that piece
of information).
Still, it is a guess and not verified information.
[...]
--
Regards,
Igor.
next prev parent reply other threads:[~2012-01-03 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 23:08 [PATCH 0/2] Support for TeeJet Mt.Ventoux Ilya Yanok
2011-12-26 23:08 ` [PATCH 1/2] mt_ventoux: very basic support for TeeJet Mt.Ventoux board Ilya Yanok
2012-01-04 19:54 ` Grant Likely
2012-01-05 8:40 ` Igor Grinberg
2011-12-26 23:08 ` [PATCH 2/2] mt_ventoux: " Ilya Yanok
2011-12-27 7:56 ` Igor Grinberg
2011-12-27 23:02 ` Ilya Yanok
2012-01-03 9:48 ` Igor Grinberg [this message]
2012-01-11 20:04 ` Ilya Yanok
2011-12-27 23:09 ` [PATCH V2] " Ilya Yanok
2012-02-01 10:51 ` Stefano Babic
2012-03-05 21:46 ` 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=4F02CED6.8090709@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sasha_d@emcraft.com \
--cc=yanok@emcraft.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).