From: Soutrik Mukhopadhyay <quic_mukhopad@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <andersson@kernel.org>, <konradybcio@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_riteshk@quicinc.com>,
<quic_vproddut@quicinc.com>, <quic_abhinavk@quicinc.com>
Subject: Re: [PATCH v2 2/2] arm64: dts: qcom: sa8775p-ride: Enable Display Port
Date: Mon, 28 Oct 2024 14:18:51 +0530 [thread overview]
Message-ID: <e7543055-316e-447e-ab0e-15d2fdd19dca@quicinc.com> (raw)
In-Reply-To: <zluuezrywecffsh3f7yzrtvd2sa3nyzl52sk6bluvjch5icvuu@noecozosseko>
On 10/8/2024 5:46 PM, Dmitry Baryshkov wrote:
> On Tue, Oct 08, 2024 at 04:55:16PM GMT, Soutrik Mukhopadhyay wrote:
>> Enable DPTX0 and DPTX1 along with their corresponding PHYs for
>> sa8775p-ride platform.
> What is connected to those DP lanes? If they are routed directly to the
> DisplayPort connectors, please add corresponding devices (see
> dp-connector).
We are defining the functionality of gpio101 and gpio102 as "edp0_hot"
and "edp1_hot"
respectively. This ensures that the hot plug will be directly routed via
the display interrupt
line "mdss0" to the display port driver and no external dependencies on
dp-connector is
necessary.
>
>> Signed-off-by: Soutrik Mukhopadhyay <quic_mukhopad@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 54 ++++++++++++++++++++++
>> 1 file changed, 54 insertions(+)
>>
>>
next prev parent reply other threads:[~2024-10-28 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 11:25 [PATCH v2 0/2] Enable Display Port for Qualcomm SA8775P-ride platform Soutrik Mukhopadhyay
2024-10-08 11:25 ` [PATCH v2 1/2] arm64: dts: qcom: sa8775p: add DisplayPort device nodes Soutrik Mukhopadhyay
2024-10-08 11:25 ` [PATCH v2 2/2] arm64: dts: qcom: sa8775p-ride: Enable Display Port Soutrik Mukhopadhyay
2024-10-08 12:16 ` Dmitry Baryshkov
2024-10-28 8:48 ` Soutrik Mukhopadhyay [this message]
2024-10-28 9:45 ` Dmitry Baryshkov
2024-10-29 6:08 ` Soutrik Mukhopadhyay
2024-10-29 13:00 ` 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=e7543055-316e-447e-ab0e-15d2fdd19dca@quicinc.com \
--to=quic_mukhopad@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_riteshk@quicinc.com \
--cc=quic_vproddut@quicinc.com \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®