From: fange zhang <quic_fangez@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <kernel@quicinc.com>, <quic_lliu6@quicinc.com>,
<quic_xiangxuy@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<quic_fangez@quicinc.com>
Subject: Re: [PATCH 4/6] dt-bindings: display/msm: Add QCS615 DSI phy
Date: Thu, 21 Nov 2024 09:34:25 +0800 [thread overview]
Message-ID: <7a7a0ba7-2d96-455c-aea7-a2cae8f60749@quicinc.com> (raw)
In-Reply-To: <p2glf4gv4jw45yxycptosbs4emcazmeysu4loefvwrfik6rn62@bayln37drvps>
On 2024/11/20 20:22, Dmitry Baryshkov wrote:
> On Tue, Nov 19, 2024 at 12:45:00PM +0800, fange zhang wrote:
>>
>>
>> On 2024/10/14 18:30, Dmitry Baryshkov wrote:
>>> On Mon, Oct 14, 2024 at 05:47:30PM +0800, fangez via B4 Relay wrote:
>>>> From: lliu6 <quic_lliu6@quicinc.com>
>>>>
>>>> QCS615 platform uses the 14nm DSI PHY driver.
>>>
>>> - bindings describe the hardware, not the drivers.
>>> - other platforms also have 14nm DSI PHY. Why do you need a separate
>>> compatible?
>> We need to introduce a new regulator configuration for the PHY:
>> dsi_phy_14nm_36mA_regulators. This configuration has not been used before.
>>
>>>
>>>>
>>>> Signed-off-by: lliu6 <quic_lliu6@quicinc.com>
>>>> ---
>>>> Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml b/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml
>>>> index 52bbe132e6dae57246200757767edcd1c8ec2d77..029606d9e87e3b184bd10bd4a5076d6923d60e9e 100644
>>>> --- a/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml
>>>> +++ b/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml
>>>> @@ -20,6 +20,7 @@ properties:
>>>> - qcom,dsi-phy-14nm-660
>>>> - qcom,dsi-phy-14nm-8953
>>>> - qcom,sm6125-dsi-phy-14nm
>>>> + - qcom,qcs615-dsi-phy-14nm
>
> qcom,sm6150-dsi-phy-14nm
ok, will fix it in next patch >> sorry, still have some question about
this yaml file.
>> it's necessary for b4 check
>>
>> checkpatch.pl: drivers/gpu/drm/msm/dsi/phy/dsi_phy.c:564: WARNING: DT
>> compatible string "qcom,dsi-phy-14nm-6150" appears un-doc
>> umented -- check ./Documentation/devicetree/bindings/
>>
>> need to add this new 6150 node for dsi-phy-14nm.
>> shall i add it?
>>
>>>> reg:
>>>> items:
>>>>
>>>> --
>>>> 2.25.1
>>>>
>>>>
>>>
>>
>> and could you please help to review the new version?
>> Author: Li Liu <quic_lliu6@quicinc.com>
>> Date: Tue Nov 19 12:35:12 2024 +0800
>>
>> dt-bindings: display/msm: Add SM6150 DSI phy
>>
>> Add new compatible for SM6150 with dsi_phy_14nm_36mA_regulators
>>
>> Signed-off-by: Li Liu <quic_lliu6@quicinc.com>
>> Signed-off-by: Fange Zhang <quic_fangez@quicinc.com>
>>
>> diff --git a/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml
>> b/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml
>> index 52bbe132e6da..fd6eb3434450 100644
>> --- a/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml
>> +++ b/Documentation/devicetree/bindings/display/msm/dsi-phy-14nm.yaml
>> @@ -17,6 +17,7 @@ properties:
>> enum:
>> - qcom,dsi-phy-14nm
>> - qcom,dsi-phy-14nm-2290
>> + - qcom,dsi-phy-14nm-6150
>
> qcom,sm6150-dsi-phy-14nm
ok, will fix it in next patch
>
>> - qcom,dsi-phy-14nm-660
>> - qcom,dsi-phy-14nm-8953
>> - qcom,sm6125-dsi-phy-14nm
>>
>
next prev parent reply other threads:[~2024-11-21 1:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 9:47 [PATCH 0/6] add_display_support_for_QCS615 fangez via B4 Relay
2024-10-14 9:47 ` [PATCH 1/6] arm64: defconfig: Enable SX150X fangez via B4 Relay
2024-10-14 10:12 ` Dmitry Baryshkov
2024-11-22 7:51 ` fange zhang
2024-10-14 10:37 ` Dmitry Baryshkov
2024-11-22 7:57 ` fange zhang
2024-11-22 8:09 ` Dmitry Baryshkov
2024-10-14 9:47 ` [PATCH 2/6] arm64: dts: qcom: qcs615: Add display mdss and dsi configuration fangez via B4 Relay
2024-10-14 10:27 ` Dmitry Baryshkov
2024-11-21 2:41 ` fange zhang
2024-10-14 9:47 ` [PATCH 3/6] drm/msm/dpu: Add QCS615 support fangez via B4 Relay
2024-10-14 10:47 ` Dmitry Baryshkov
2024-11-18 8:52 ` fange zhang
2024-11-18 10:55 ` Dmitry Baryshkov
2024-11-22 7:36 ` fange zhang
2024-11-22 7:37 ` Dmitry Baryshkov
2024-11-22 7:48 ` fange zhang
2024-10-14 9:47 ` [PATCH 4/6] dt-bindings: display/msm: Add QCS615 DSI phy fangez via B4 Relay
2024-10-14 10:30 ` Dmitry Baryshkov
2024-11-19 4:45 ` fange zhang
2024-11-20 12:22 ` Dmitry Baryshkov
2024-11-21 1:34 ` fange zhang [this message]
2024-10-14 11:49 ` Krzysztof Kozlowski
2024-10-14 9:47 ` [PATCH 5/6] dt-bindings: display/msm: Add QCS615 MDSS & DPU fangez via B4 Relay
2024-10-14 10:35 ` Dmitry Baryshkov
2024-11-21 9:20 ` fange zhang
2024-10-14 11:50 ` Krzysztof Kozlowski
2024-10-14 9:47 ` [PATCH 6/6] dt-bindings: display/msm: dsi-controller-main: Document QCS615 fangez via B4 Relay
2024-10-14 10:39 ` Dmitry Baryshkov
2024-11-19 4:20 ` fange zhang
2024-10-14 10:36 ` [PATCH 0/6] add_display_support_for_QCS615 Dmitry Baryshkov
2024-10-14 10:48 ` Dmitry Baryshkov
[not found] ` <SJ0PR02MB8750D786748D105839EE905BE3442@SJ0PR02MB8750.namprd02.prod.outlook.com>
2024-10-14 11:59 ` Dmitry Baryshkov
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=7a7a0ba7-2d96-455c-aea7-a2cae8f60749@quicinc.com \
--to=quic_fangez@quicinc.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=kernel@quicinc.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_lliu6@quicinc.com \
--cc=quic_xiangxuy@quicinc.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