From: Archit Taneja <architt@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: andy.gross@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: drm/bridge: adv7511: Add regulators for ADV7533
Date: Tue, 6 Sep 2016 09:52:40 +0530 [thread overview]
Message-ID: <57CE4490.6060406@codeaurora.org> (raw)
In-Reply-To: <20160902155611.GA4226@rob-hp-laptop>
On 09/02/2016 09:26 PM, Rob Herring wrote:
> On Wed, Aug 31, 2016 at 04:22:08PM +0530, Archit Taneja wrote:
>> Add the regulator supply properties needed for ADV7533. The regulator
>> names are named after the pin names. The exact use of each supply isn't
>> clear from the data sheets.
>>
>> The regulators are specified as optional properties since there can
>> be boards which have a fixed supply directly routed to the pins, and
>> these may not be modelled as regulator supplies.
>>
>> There might be a similar set of regulators for ADV7511, but we don't
>> have the docs at the moment to find out what supplies it needs. The
>> regulator properties needed by ADV7511 can be updated as we get more
>> data on it.
>
> The ADV7510 is available and there's a pinout comparison with the 7511:
>
> http://www.analog.com/media/en/technical-documentation/evaluation-documentation/ADV7510_to_ADV7511_differences.pdf
>
> These 2 seem to have the same supplies...
Thanks. I'll use this.
>
>>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Archit Taneja <architt@codeaurora.org>
>> ---
>> Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>> index 6532a59..669b6f2 100644
>> --- a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>> +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>> @@ -56,6 +56,12 @@ Optional properties:
>> - adi,disable-timing-generator: Only for ADV7533. Disables the internal timing
>> generator. The chip will rely on the sync signals in the DSI data lanes,
>> rather than generate its own timings for HDMI output.
>> +- avdd-supply: Only for ADV7533. A 1.8V supply that powers up the AVDD, DVDD
>> + PVDD and A2VDD pins on the chip.
>
> This sounds wrong. Each input to the chip should be a property even if
> they are typically from the same supply.
I'll create an entry for each.
>
> The 7511 has DVDD, AVDD, and PVDD.
>
>> +- v1p2-supply: Only for ADV7533. A supply that powers up the V1P2 pin on the
>> + chip. Can be either 1.2V or 1.8V.
>
> This appears to be 7533 specific.
>
>> +- v3p3-supply: Only for ADV7533. A 3.3V supply that powers up the V3P3 pin on
>> + the chip.
>
> DVDD_3V on 7511
>
> 7510/7511 also have BGVDD (for Bandgap). Not clear what the voltage is.
I'll add this regulator, and mention that we don't know
what the voltage is.
>
> Rob
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-09-06 4:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1472640730-24326-1-git-send-email-architt@codeaurora.org>
[not found] ` <1472640730-24326-1-git-send-email-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-08-31 10:52 ` [PATCH 1/3] dt-bindings: drm/bridge: adv7511: Add regulators for ADV7533 Archit Taneja
2016-09-02 15:56 ` Rob Herring
2016-09-06 4:22 ` Archit Taneja [this message]
[not found] ` <1474622430-6704-1-git-send-email-architt@codeaurora.org>
2016-09-23 9:20 ` [PATCH v2 1/4] dt-bindings: drm/bridge: adv7511: Add regulator bindings Archit Taneja
2016-09-23 22:31 ` Rob Herring
[not found] ` <1474622430-6704-2-git-send-email-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-09-25 17:28 ` Laurent Pinchart
2016-09-26 6:40 ` Archit Taneja
2016-09-26 8:12 ` Laurent Pinchart
2016-10-14 5:40 ` Archit Taneja
2016-11-10 1:34 ` Rob Herring
[not found] ` <CAL_Jsq+KMPoyWvh1U3OKL6pX8D4QByqVFgcMks8myDfZEYeFCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-15 3:35 ` Archit Taneja
[not found] ` <1480399662-8858-1-git-send-email-architt@codeaurora.org>
[not found] ` <1480399662-8858-1-git-send-email-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-11-29 6:07 ` [PATCH v3 1/2] " Archit Taneja
[not found] ` <1480399662-8858-2-git-send-email-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-11-29 6:33 ` Laurent Pinchart
2016-11-29 8:11 ` Archit Taneja
2016-11-29 9:11 ` Laurent Pinchart
2016-11-29 11:01 ` Mark Brown
2016-11-29 19:37 ` Laurent Pinchart
2016-11-30 16:14 ` Mark Brown
2016-12-05 21:11 ` Bjorn Andersson
2016-12-05 21:16 ` Laurent Pinchart
2016-12-06 10:05 ` Mark Brown
2016-12-06 12:46 ` Laurent Pinchart
2016-12-06 13:20 ` Mark Brown
2016-12-06 16:08 ` Laurent Pinchart
2016-12-06 16:11 ` Mark Brown
[not found] ` <1480924435-20882-1-git-send-email-architt@codeaurora.org>
2016-12-05 7:53 ` [PATCH v4 " Archit Taneja
2016-12-09 22:11 ` Rob Herring
2016-12-18 11:17 ` Archit Taneja
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=57CE4490.6060406@codeaurora.org \
--to=architt@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh@kernel.org \
/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).