From: fange zhang <quic_fangez@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Krishna Manikandan" <quic_mkrishn@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Liu Li <quic_lliu6@quicinc.com>,
Xiangxu Yin <quic_xiangxuy@quicinc.com>,
<linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 9/9] arm64: dts: qcom: Add display support for QCS615 RIDE board
Date: Wed, 18 Dec 2024 11:18:01 +0800 [thread overview]
Message-ID: <baab6fc5-755a-4675-a42d-ba7ba7facf0c@quicinc.com> (raw)
In-Reply-To: <CAA8EJpqyM-r3jvY7sTpG-KKRHP9K7c3q0xfoLb_f0th7vunPYw@mail.gmail.com>
On 2024/12/13 18:19, Dmitry Baryshkov wrote:
> On Fri, 13 Dec 2024 at 11:21, fange zhang <quic_fangez@quicinc.com> wrote:
>>
>>
>>
>> On 2024/12/10 19:02, Dmitry Baryshkov wrote:
>>> On Tue, Dec 10, 2024 at 02:54:00PM +0800, Fange Zhang wrote:
>>>> From: Li Liu <quic_lliu6@quicinc.com>
>>>>
>>>> Add display MDSS and DSI configuration for QCS615 RIDE board.
>>>> QCS615 has a DP port, and DP support will be added in a later patch.
>>>>
>>>> Signed-off-by: Li Liu <quic_lliu6@quicinc.com>
>>>> Signed-off-by: Fange Zhang <quic_fangez@quicinc.com>
>>>> ---
>>>> arch/arm64/boot/dts/qcom/qcs615-ride.dts | 89 ++++++++++++++++++++++++++++++++
>>>> 1 file changed, 89 insertions(+)
>>>>
>>>> diff --git a/arch/arm64/boot/dts/qcom/qcs615-ride.dts b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>>>> index a25928933e2b66241258e418c6e5bc36c306101e..694719a09ac46bfa2fe34f1883c0970b9d0902be 100644
>>>> --- a/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>>>> +++ b/arch/arm64/boot/dts/qcom/qcs615-ride.dts
>>>> @@ -32,6 +32,18 @@ xo_board_clk: xo-board-clk {
>>>> #clock-cells = <0>;
>>>> };
>>>> };
>>>> +
>>>> + dp-connector {
>>>> + compatible = "dp-connector";
>>>> + label = "DP";
>>>> + type = "mini";
>>>> +
>>>> + port {
>>>> + dp_connector_out: endpoint {
>>>> + remote-endpoint = <&anx_7625_out>;
>>>> + };
>>>> + };
>>>> + };
>>>> };
>>>>
>>>> &apps_rsc {
>>>> @@ -202,6 +214,83 @@ &gcc {
>>>> <&sleep_clk>;
>>>> };
>>>>
>>>> +&i2c2 {
>>>> + clock-frequency = <400000>;
>>>> + status = "okay";
>>>> +
>>>> + ioexp: gpio@3e {
>>>> + compatible = "semtech,sx1509q";
>>>> + reg = <0x3e>;
>>>> + interrupt-parent = <&tlmm>;
>>>> + interrupts = <58 0>;
>>>
>>> Use IRQ flags instead of just 0 (here and further on). Also it might be
>>> better to use interrupts-extended instead.
>> Got it, will use interrupts-extended instead
>> - interrupt-parent = <&tlmm>;
>> - interrupts = <58 0>;
>> + interrupts-extended = <&tlmm 58 IRQ_TYPE_NONE>;
>>>
>>>> + gpio-controller;
>>>> + #gpio-cells = <2>;
>>>> + interrupt-controller;
>>>> + #interrupt-cells = <2>;
>>>> + semtech,probe-reset;
>>>> + };
>>>> +
>>>> + i2c-mux@77 {
>>>> + compatible = "nxp,pca9542";
>>>> + reg = <0x77>;
>>>> + #address-cells = <1>;
>>>> + #size-cells = <0>;
>>>
>>> Add empty line before device nodes (here and furher on).
>> Sorry, will add it in next patch.
>>>
>>>> + i2c@0 {
>>>> + reg = <0>;
>>>> + #address-cells = <1>;
>>>> + #size-cells = <0>;
>>>> +
>>>> + anx7625@58 {
>>>> + compatible = "analogix,anx7625";
>>>> + reg = <0x58>;
>>>> + interrupt-parent = <&ioexp>;
>>>> + interrupts = <0 0>;
>> will change it to interrupts-extended in next patch
>> - interrupt-parent = <&ioexp>;
>> - interrupts = <0 0>;
>> + interrupts-extended = <&ioexp 0 IRQ_TYPE_NONE>;
>
> Yes, much better. BTW: are you sure that it's really IRQ_TYPE_NONE?
We extensively tested FALLING and BOTH type, and they all work. However,
I believe it’s better to use the default type, which is the same as the
downstream approach. This way, it will be more stable.
>
>>>> + enable-gpios = <&tlmm 4 GPIO_ACTIVE_HIGH>;
>>>> + reset-gpios = <&tlmm 5 GPIO_ACTIVE_HIGH>;
>>>> + wakeup-source;
>>>> +
>>>> + ports {
>>>> + #address-cells = <1>;
>>>> + #size-cells = <0>;
>>>> +
>>>> + port@0 {
>>>> + reg = <0>;
>>>> + anx_7625_in: endpoint {
>>>> + remote-endpoint = <&mdss_dsi0_out>;
>>>> + };
>>>> + };
>>>> +
>>>> + port@1 {
>>>> + reg = <1>;
>>>> + anx_7625_out: endpoint {
>>>> + remote-endpoint = <&dp_connector_out>;
>>>> + };
>>>> + };
>>>> + };
>>>> + };
>>>> + };
>>>> + };
>>>> +};
>>>> +
>>>> +&mdss {
>>>> + status = "okay";
>>>> +};
>>>> +
>>>> +&mdss_dsi0 {
>>>> + vdda-supply = <&vreg_l11a>;
>>>> + status = "okay";
>>>> +};
>>>> +
>>>> +&mdss_dsi0_out {
>>>> + remote-endpoint = <&anx_7625_in>;
>>>> + data-lanes = <0 1 2 3>;
>>>> +};
>>>> +
>>>> +&mdss_dsi0_phy {
>>>> + vdds-supply = <&vreg_l5a>;
>>>> + status = "okay";
>>>> +};
>>>> +
>>>> &qupv3_id_0 {
>>>> status = "okay";
>>>> };
>>>>
>>>> --
>>>> 2.34.1
>>>>
>>>
>>
>
>
next prev parent reply other threads:[~2024-12-18 3:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 6:53 [PATCH v4 0/9] Add display support for QCS615 platform Fange Zhang
2024-12-10 6:53 ` [PATCH v4 1/9] dt-bindings: display/msm: Add SM6150 DSI phy Fange Zhang
2024-12-10 6:53 ` [PATCH v4 2/9] dt-bindings: display/msm: dsi-controller-main: Document SM6150 Fange Zhang
2024-12-10 8:22 ` Krzysztof Kozlowski
2024-12-10 6:53 ` [PATCH v4 3/9] dt-bindings: display/msm: Add SM6150 MDSS & DPU Fange Zhang
2024-12-10 8:26 ` Krzysztof Kozlowski
2024-12-10 6:53 ` [PATCH v4 4/9] drm/msm: mdss: Add SM6150 support Fange Zhang
2024-12-10 6:53 ` [PATCH v4 5/9] drm/msm/dpu: " Fange Zhang
2024-12-17 10:54 ` Dmitry Baryshkov
2024-12-17 11:02 ` fange zhang
2024-12-17 12:06 ` Dmitry Baryshkov
2024-12-10 6:53 ` [PATCH v4 6/9] drm/msm/dsi: Add dsi phy support for SM6150 Fange Zhang
2024-12-10 6:53 ` [PATCH v4 7/9] drm/msm/dsi: Add " Fange Zhang
2024-12-10 10:58 ` Dmitry Baryshkov
2024-12-10 6:53 ` [PATCH v4 8/9] arm64: dts: qcom: Add display support for QCS615 Fange Zhang
2024-12-10 6:54 ` [PATCH v4 9/9] arm64: dts: qcom: Add display support for QCS615 RIDE board Fange Zhang
2024-12-10 11:02 ` Dmitry Baryshkov
2024-12-13 9:21 ` fange zhang
2024-12-13 10:19 ` Dmitry Baryshkov
2024-12-18 3:18 ` fange zhang [this message]
2024-12-18 11:44 ` Dmitry Baryshkov
2024-12-30 3:32 ` fange zhang
2024-12-15 13:10 ` [PATCH v4 0/9] Add display support for QCS615 platform Dmitry Baryshkov
2024-12-16 8:02 ` fange zhang
2024-12-26 5:18 ` Bjorn Andersson
2024-12-30 3:10 ` fange zhang
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=baab6fc5-755a-4675-a42d-ba7ba7facf0c@quicinc.com \
--to=quic_fangez@quicinc.com \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_lliu6@quicinc.com \
--cc=quic_mkrishn@quicinc.com \
--cc=quic_xiangxuy@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®