From: Ayushi Makhija <quic_amakhija@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Ayushi Makhija <amakhija@qti.qualcomm.com>
Cc: <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <robdclark@gmail.com>,
<sean@poorly.run>, <marijn.suijten@somainline.org>,
<andersson@kernel.org>, <robh@kernel.org>, <robh+dt@kernel.org>,
<krzk+dt@kernel.org>, <konradybcio@kernel.org>,
<conor+dt@kernel.org>, <andrzej.hajda@intel.com>,
<neil.armstrong@linaro.org>, <rfoss@kernel.org>,
<Laurent.pinchart@ideasonboard.com>, <jonas@kwiboo.se>,
<jernej.skrabec@gmail.com>, <quic_abhinavk@quicinc.com>,
<quic_rajeevny@quicinc.com>, <quic_vproddut@quicinc.com>,
<quic_jesszhan@quicinc.com>
Subject: Re: [PATCH v4 07/11] arm64: dts: qcom: sa8775p-ride: add anx7625 DSI to DP bridge nodes
Date: Tue, 22 Apr 2025 12:28:20 +0530 [thread overview]
Message-ID: <d77353b0-94e6-4461-bd34-44c8cb80eb07@quicinc.com> (raw)
In-Reply-To: <qnhfnxvdsgnw5jh4xxaqz3p2x67qcrr7kn3vwdnyz5huchdtzy@aagflznjrvly>
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@quicinc.com>
>>
>> Add anx7625 DSI to DP bridge device nodes.
>>
>> Signed-off-by: Ayushi Makhija <quic_amakhija@quicinc.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
>
next prev parent reply other threads:[~2025-04-22 6:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 5:38 [PATCH v4 00/11] Add DSI display support for SA8775P target Ayushi Makhija
2025-04-17 5:38 ` [PATCH v4 01/11] dt-bindings: display: msm-dsi-phy-7nm: document the SA8775P DSI PHY Ayushi Makhija
2025-04-17 5:39 ` [PATCH v4 02/11] dt-bindings: msm: dsi-controller-main: document the SA8775P DSI CTRL Ayushi Makhija
2025-04-17 5:39 ` [PATCH v4 03/11] dt-bindings: display: msm: document DSI controller and phy on SA8775P Ayushi Makhija
2025-04-17 5:46 ` Krzysztof Kozlowski
2025-04-17 5:39 ` [PATCH v4 04/11] drm/msm/dsi: add DSI PHY configuration " Ayushi Makhija
2025-04-17 5:39 ` [PATCH v4 05/11] drm/msm/dsi: add DSI support for SA8775P Ayushi Makhija
2025-04-17 5:39 ` [PATCH v4 06/11] arm64: dts: qcom: sa8775p: add Display Serial Interface device nodes Ayushi Makhija
2025-04-17 5:39 ` [PATCH v4 07/11] arm64: dts: qcom: sa8775p-ride: add anx7625 DSI to DP bridge nodes Ayushi Makhija
2025-04-17 10:40 ` Dmitry Baryshkov
2025-04-22 5:28 ` Ayushi Makhija
2025-04-22 6:58 ` Ayushi Makhija [this message]
2025-04-22 11:02 ` Dmitry Baryshkov
2025-04-17 5:39 ` [PATCH v4 08/11] drm/bridge: anx7625: enable HPD interrupts Ayushi Makhija
2025-04-17 5:39 ` [PATCH v4 09/11] drm/bridge: anx7625: fix drm_bridge ops flags to support hot-plugging Ayushi Makhija
2025-04-17 5:39 ` [PATCH v4 10/11] drm/bridge: anx7625: fix anx7625_sink_detect() to return correct hpd status Ayushi Makhija
2025-04-17 10:44 ` Dmitry Baryshkov
2025-04-23 9:33 ` Ayushi Makhija
2025-04-23 13:58 ` Dmitry Baryshkov
2025-04-17 5:39 ` [PATCH v4 11/11] drm/bridge: anx7625: change the gpiod_set_value API Ayushi Makhija
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=d77353b0-94e6-4461-bd34-44c8cb80eb07@quicinc.com \
--to=quic_amakhija@quicinc.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=amakhija@qti.qualcomm.com \
--cc=andersson@kernel.org \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_rajeevny@quicinc.com \
--cc=quic_vproddut@quicinc.com \
--cc=rfoss@kernel.org \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sean@poorly.run \
/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