[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d77353b0-94e6-4461-bd34-44c8cb80eb07@quicinc.com>
Date: Tue, 22 Apr 2025 12:28:20 +0530
From: Ayushi Makhija <quic_amakhija@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Ayushi Makhija
<amakhija@....qualcomm.com>
CC: <linux-arm-msm@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
<freedreno@...ts.freedesktop.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <robdclark@...il.com>,
<sean@...rly.run>, <marijn.suijten@...ainline.org>,
<andersson@...nel.org>, <robh@...nel.org>, <robh+dt@...nel.org>,
<krzk+dt@...nel.org>, <konradybcio@...nel.org>, <conor+dt@...nel.org>,
<andrzej.hajda@...el.com>, <neil.armstrong@...aro.org>,
<rfoss@...nel.org>, <Laurent.pinchart@...asonboard.com>,
<jonas@...boo.se>, <jernej.skrabec@...il.com>,
<quic_abhinavk@...cinc.com>, <quic_rajeevny@...cinc.com>,
<quic_vproddut@...cinc.com>, <quic_jesszhan@...cinc.com>
Subject: Re: [PATCH v4 07/11] arm64: dts: qcom: sa8775p-ride: add anx7625 DSI
to DP bridge nodes
On 4/17/2025 4:10 PM, Dmitry Baryshkov wrote:
> On Thu, Apr 17, 2025 at 11:09:05AM +0530, Ayushi Makhija wrote:
>> From: Ayushi Makhija <quic_amakhija@...cinc.com>
>>
>> Add anx7625 DSI to DP bridge device nodes.
>>
>> Signed-off-by: Ayushi Makhija <quic_amakhija@...cinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 180 +++++++++++++++++++++
>> 1 file changed, 180 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>> index 175f8b1e3b2d..d5b2dabe927d 100644
>> --- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi
>> @@ -28,6 +28,13 @@ chosen {
>> stdout-path = "serial0:115200n8";
>> };
>>
>> + vph_pwr: vph-pwr-regulator {
>> + compatible = "regulator-fixed";
>> + regulator-name = "vph_pwr";
>> + regulator-always-on;
>> + regulator-boot-on;
>> + };
>> +
>> vreg_conn_1p8: vreg_conn_1p8 {
>> compatible = "regulator-fixed";
>> regulator-name = "vreg_conn_1p8";
>> @@ -128,6 +135,30 @@ dp1_connector_in: endpoint {
>> };
>> };
>> };
>> +
>> + dp-dsi0-connector {
>> + compatible = "dp-connector";
>> + label = "DSI0";
>> + type = "full-size";
>> +
>> + port {
>> + dp_dsi0_connector_in: endpoint {
>> + remote-endpoint = <&dsi2dp_bridge0_out>;
>> + };
>> + };
>> + };
>> +
>> + dp-dsi1-connector {
>> + compatible = "dp-connector";
>> + label = "DSI1";
>> + type = "full-size";
>> +
>> + port {
>> + dp_dsi1_connector_in: endpoint {
>> + remote-endpoint = <&dsi2dp_bridge1_out>;
>> + };
>> + };
>> + };
>> };
>>
>> &apps_rsc {
>> @@ -519,7 +550,107 @@ &i2c18 {
>> clock-frequency = <400000>;
>> pinctrl-0 = <&qup_i2c18_default>;
>> pinctrl-names = "default";
>> +
>> status = "okay";
>> +
>> + io_expander: gpio@74 {
>> + compatible = "ti,tca9539";
>> + reg = <0x74>;
>> + interrupts-extended = <&tlmm 98 IRQ_TYPE_EDGE_BOTH>;
>> + gpio-controller;
>> + #gpio-cells = <2>;
>> + interrupt-controller;
>> + #interrupt-cells = <2>;
>
> No reset-gpios? Is the expander being used by something else so that we
> don't want it to be reset during the bootup?
>
Hi Dmitry,
Please, ignore the previous reply.
This io_expander is used by anx7625 bridge only. I have defined the gpio in pinctrl setting and so far it was helping out indirectly to bring io_expander out
of the reset. The reset-gpios is optional for tca9539, because of which the io_expander driver didn't throw an error and I never realize that I should add this property.
I tested by adding the reset-gpios entry and it's working fine. I will update in the next patchset.
+ reset-gpios = <&tlmm 97 GPIO_ACTIVE_LOW>;
Thanks again, for pointing it out.
Thanks,
Ayushi
>> +
>> + pinctrl-0 = <&io_expander_intr_active>,
>> + <&io_expander_reset_active>;
>> + pinctrl-names = "default";
>> + };
>> +
>
> The rest LGTM
>
Powered by blists - more mailing lists