devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Clark <robdclark@gmail.com>
To: Archit Taneja <architt@codeaurora.org>
Cc: Rob Herring <robh@kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Lloyd Atkinson <latkinso@codeaurora.org>,
	sibis@codeaurora.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 6/7] dt-bindings: display: msm/dsi: Add compatible for 14nm DSI PHY
Date: Wed, 31 Jan 2018 11:20:04 -0500	[thread overview]
Message-ID: <CAF6AEGsLrXBUub9Y5r-bTY2OPDksRSDjYpJXYoKxYp3MvHCP2w@mail.gmail.com> (raw)
In-Reply-To: <7b0254be-8dcf-f2cf-4911-64f0b5881759@codeaurora.org>

On Wed, Jan 31, 2018 at 1:40 AM, Archit Taneja <architt@codeaurora.org> wrote:
>
>
> On 01/29/2018 10:45 PM, Rob Herring wrote:
>>
>> On Wed, Jan 17, 2018 at 03:04:47PM +0530, Archit Taneja wrote:
>>>
>>> Add the compatible string for 14nm DSI PHY (used in MSM8996/APQ8096).
>>>  From 14nm PHY onwards, the "dsi_phy_regulator" reg-name is not required,
>>> but "dsi_phy_lane" reg-name is. Update the doc to specify the reg-names
>>> each PHY revision needs.
>>>
>>> Cc: Rob Herring <robh@kernel.org>
>>> Cc: devicetree@vger.kernel.org
>>> Signed-off-by: Archit Taneja <architt@codeaurora.org>
>>> ---
>>>   Documentation/devicetree/bindings/display/msm/dsi.txt | 13
>>> +++++++++++--
>>>   1 file changed, 11 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/display/msm/dsi.txt
>>> b/Documentation/devicetree/bindings/display/msm/dsi.txt
>>> index 9c3ad6bbb9f0..26a1796b7145 100644
>>> --- a/Documentation/devicetree/bindings/display/msm/dsi.txt
>>> +++ b/Documentation/devicetree/bindings/display/msm/dsi.txt
>>> @@ -86,12 +86,19 @@ Required properties:
>>>     * "qcom,dsi-phy-28nm-lp"
>>>     * "qcom,dsi-phy-20nm"
>>>     * "qcom,dsi-phy-28nm-8960"
>>> -- reg: Physical base address and length of the registers of PLL, PHY and
>>> PHY
>>> -  regulator
>>> +  * "qcom,dsi-phy-14nm"
>>> +- reg: Physical base address and length of the registers of PLL, PHY.
>>> Some
>>> +  revisions require the PHY regulator base address, whereas others
>>> require the
>>> +  PHY lane base address. See below for each PHY revision.
>>>   - reg-names: The names of register regions. The following regions are
>>> required:
>>> +  For DSI 28nm HPM/LP/8960 PHYs and 20nm PHY:
>>>     * "dsi_pll"
>>>     * "dsi_phy"
>>>     * "dsi_phy_regulator"
>>> +  For DSI 14nm PHY:
>>> +  * "dsi_pll"
>>> +  * "dsi_phy"
>>> +  * "dsi_phy_lane"
>>>   - clock-cells: Must be 1. The DSI PHY block acts as a clock provider,
>>> creating
>>>     2 clocks: A byte clock (index 0), and a pixel clock (index 1).
>>>   - power-domains: Should be <&mmcc MDSS_GDSC>.
>>> @@ -102,6 +109,8 @@ Required properties:
>>>   - vddio-supply: phandle to vdd-io regulator device node
>>>     For 20nm PHY:
>>>   - vddio-supply: phandle to vdd-io regulator device node
>>> +- vcca-supply: phandle to vcca regulator device node
>>
>>
>> Did you mean to add this?
>
>
> Yes, I didn't intend it to be a part of this patch, but this supply is
> indeed needed for the
> 20nm PHY. I'll move this to a separate patch.

actually, this looks correct, just formatted counter-intuitively by
git-format-patch..

vcca-supply for 20nm was introduced by "dt-bindings: display: msm/dsi:
Fix the PHY regulator supply props", but when 14nm phy is added in
this patch, it shows the addition of same line beneath 14nm PHY as an
addition above the line.

So I don't think it needs to be split up.

BR,
-R

> Thanks,
> Archit
>
>
>>
>>> +  For 14nm PHY:
>>>   - vcca-supply: phandle to vcca regulator device node
>>>     Optional properties:
>>> --
>>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>>> Forum,
>>> hosted by The Linux Foundation
>>>
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project

  reply	other threads:[~2018-01-31 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180117093448.4102-1-architt@codeaurora.org>
2018-01-17  9:34 ` [PATCH 4/7] dt-bindings: display: msm/dsi: Remove unused properties Archit Taneja
2018-01-29 17:11   ` Rob Herring
2018-01-17  9:34 ` [PATCH 5/7] dt-bindings: display: msm/dsi: Fix the PHY regulator supply props Archit Taneja
     [not found]   ` <20180117093448.4102-6-architt-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-01-29 17:13     ` Rob Herring
2018-01-17  9:34 ` [PATCH 6/7] dt-bindings: display: msm/dsi: Add compatible for 14nm DSI PHY Archit Taneja
2018-01-29 17:15   ` Rob Herring
2018-01-31  6:40     ` Archit Taneja
2018-01-31 16:20       ` Rob Clark [this message]
     [not found]         ` <CAF6AEGsLrXBUub9Y5r-bTY2OPDksRSDjYpJXYoKxYp3MvHCP2w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-01  5:29           ` Archit Taneja
2018-02-01 14:41             ` Rob Herring
2018-01-17  9:34 ` [PATCH 7/7] dt-bindings: display: msm/dsi: Add updates for SDM845 Archit Taneja
2018-01-29 17:16   ` Rob Herring

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=CAF6AEGsLrXBUub9Y5r-bTY2OPDksRSDjYpJXYoKxYp3MvHCP2w@mail.gmail.com \
    --to=robdclark@gmail.com \
    --cc=architt@codeaurora.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=latkinso@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sibis@codeaurora.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).