From: Archit Taneja <architt@codeaurora.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>, robh@kernel.org
Cc: andy.gross@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: drm/bridge: adv7511: Add regulator bindings
Date: Fri, 14 Oct 2016 11:10:28 +0530 [thread overview]
Message-ID: <e3d74745-fd14-63f1-e93f-f57e886e26ed@codeaurora.org> (raw)
In-Reply-To: <1527982.jPo8JkVTxZ@avalon>
Hi Rob,
On 09/26/2016 01:42 PM, Laurent Pinchart wrote:
> Hi Archit,
>
> On Monday 26 Sep 2016 12:10:11 Archit Taneja wrote:
>> On 9/25/2016 10:58 PM, Laurent Pinchart wrote:
>>> On Friday 23 Sep 2016 14:50:27 Archit Taneja wrote:
>>>> Add the regulator supply properties needed by ADV7511 and ADV7533. The
>>>> regulator names are named after the pin names, except for DVDD_3V on
>>>> ADV7511, which is left v3p3 to have the same name as it's on ADV7533.
>>>>
>>>> ADV7511 has a BGVDD pin for which the voltage to be configured isn't
>>>> clear. This needs to be updated in the document later.
>>>>
>>>> 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.
>>>>
>>>> Cc: Rob Herring <robh@kernel.org>
>>>> Cc: devicetree@vger.kernel.org
>>>> Signed-off-by: Archit Taneja <architt@codeaurora.org>
>>>> ---
>>>> v2:
>>>> - Specify regulator supplies for ADV7511 too.
>>>> - Have separate supply entries for AVDD, DVDD, PVDD, A2VDD pins.
>>>> - Add additional BGVDD supply for ADV7511.
>>>>
>>>> .../devicetree/bindings/display/bridge/adi,adv7511.txt | 14 +++++++
>>>> 1 file changed, 14 insertions(+)
>>>>
>>>> diff --git
>>>> a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>>>> b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt index
>>>> 6532a59..66e6bae 100644
>>>> --- a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>>>> +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt
>>>>
>>>> @@ -56,6 +56,20 @@ 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: A 1.8V supply that powers up the AVDD pin on the chip.
>>>> +- dvdd-supply: A 1.8V supply that powers up the DVDD pin on the chip.
>>>> +- pvdd-supply: A 1.8V supply that powers up the PVDD pin on the chip.
>>>> +- v3p3-supply: A 3.3V supply that powers up the pin called DVDD_3V on
>>>> + ADV7511 and V3P3 on ADV7533.
>>>> +
>>>> +ADV7511 specific supplies:
>>>> +- bgvdd-supply: Powers the BGVDD pin. The voltage isn't clear from
>>>> + available datasheets.
>>>
>>> It's a 1.8V supply. The ADV7511 hardware user's guide recommends tying it
>>> to the PVDD supply, so I'm not sure we need a separate supply in DT.
>>
>> Thanks for providing the info. I'll update it in the doc.
>>
>>> Similarly, the user's guide recommends supplying the AVDD, DVDD and PVDD
>>> pins with a single 1.8V LDO and three independent filters. We could thus
>>> possibly combine them into a single 1.8V supply.
>>
>> I'd originally specified only one AVDD supply for all the 1.8 V
>> supplies, but Rob had recommended using separate supplies for each pin.
>>
>> I guess it doesn't do much harm specifying separate supplies, a
>> board can just provide avdd-supply, and the rest would be assumed dummy.
>
> DT should use the same regulator phandle for all power supplies in that case,
> not specify a single one.
>
>> It could also help describe boards which may not have followed the
>> user guide's recommendation, but I agree that's probably a rare
>> scenario.
>>
>> Is it okay if we stick with multiple supplies as it is in this version?
>
> It seems overkill to me but I can live with that. I'd remove the bgvdd supply
> though.
>
> Rob, what's your opinion on this ? Is there a specific reason why you prefer
> splitting the 1.8V supply in one supply per pin, when the hardware user's
> guide recommend powering them from the same LDO ?
Could you suggest us which way to go?
Thanks,
Archit
>
>>>> +ADV7533 specific supplies:
>>>> +- a2vdd-supply: 1.8V supply that powers up the A2VDD pin on the chip.
>>>> +- v1p2-supply: A supply that powers up the V1P2 pin on the chip. It can
>>>> be
>>>> + either 1.2V or 1.8V.
>>>>
>>>> Required nodes:
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-10-14 5:40 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
[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 [this message]
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=e3d74745-fd14-63f1-e93f-f57e886e26ed@codeaurora.org \
--to=architt@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--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).