From: Ayushi Makhija <quic_amakhija@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.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>, <jonathan@marek.ca>,
<jonas@kwiboo.se>, <jernej.skrabec@gmail.com>,
<quic_rajeevny@quicinc.com>, <quic_vproddut@quicinc.com>
Subject: Re: [PATCH v2 7/7] arm64: dts: qcom: qcs8300-ride: add anx7625 DSI to DP bridge node
Date: Tue, 14 Oct 2025 12:06:13 +0530 [thread overview]
Message-ID: <3597f849-fe69-48a5-91cb-7a0bdc9f3e7d@quicinc.com> (raw)
In-Reply-To: <vj3pwikzgbflzwqwkbvdfac44llinsmrhrqnvu6gx756xz4h3e@2lspa6zx5xgr>
On 10/6/2025 3:46 PM, Dmitry Baryshkov wrote:
> On Mon, Oct 06, 2025 at 07:09:24AM +0530, Ayushi Makhija wrote:
>> Add anx7625 DSI to DP bridge device node.
>>
>> Signed-off-by: Ayushi Makhija <quic_amakhija@quicinc.com>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/qcs8300-ride.dts | 170 ++++++++++++++++++++++
>> 1 file changed, 170 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qcs8300-ride.dts b/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
>> index 891e49602c97..5d4040376857 100644
>> --- a/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
>> +++ b/arch/arm64/boot/dts/qcom/qcs8300-ride.dts
>> @@ -24,6 +24,64 @@ chosen {
>> stdout-path = "serial0:115200n8";
>> };
>>
>> + vreg_12p0: vreg-12p0-regulator {
>
> Why are these nodes not in a correct place? Also, why are they named
> differently from all other regulators in this board file?
Hi Dmitry,
Will keep the nodes at their correct place based on alphabetical order in next patchset.
Similar names I have used in LeMans for these regulators. We have kept these name based on the information of these regulator we got from SW doc for monaco.
Thanks,
Ayushi
next prev parent reply other threads:[~2025-10-14 6:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 1:39 [PATCH v2 0/7] Add DSI display support for QCS8300 target Ayushi Makhija
2025-10-06 1:39 ` [PATCH v2 1/7] dt-bindings: display: msm-dsi-phy-7nm: document the QCS8300 DSI PHY Ayushi Makhija
2025-10-06 1:39 ` [PATCH v2 2/7] dt-bindings: msm: dsi-controller-main: document the QCS8300 DSI CTRL Ayushi Makhija
2025-10-06 10:09 ` Dmitry Baryshkov
2025-10-06 1:39 ` [PATCH v2 3/7] dt-bindings: display: msm: document DSI controller and phy on QCS8300 Ayushi Makhija
2025-10-06 1:39 ` [PATCH v2 4/7] drm/msm/dsi: add DSI PHY configuration " Ayushi Makhija
2025-10-06 8:30 ` Konrad Dybcio
2025-10-06 10:12 ` Dmitry Baryshkov
2025-10-06 1:39 ` [PATCH v2 5/7] drm/msm/dsi: add DSI support for QCS8300 Ayushi Makhija
2025-10-06 8:28 ` Konrad Dybcio
2025-10-06 1:39 ` [PATCH v2 6/7] arm64: dts: qcom: qcs8300: add Display Serial Interface device nodes Ayushi Makhija
2025-10-06 10:14 ` Dmitry Baryshkov
2025-10-14 6:24 ` Ayushi Makhija
2025-10-14 8:53 ` Konrad Dybcio
2025-10-14 9:19 ` Dmitry Baryshkov
2025-10-06 1:39 ` [PATCH v2 7/7] arm64: dts: qcom: qcs8300-ride: add anx7625 DSI to DP bridge node Ayushi Makhija
2025-10-06 10:16 ` Dmitry Baryshkov
2025-10-14 6:36 ` Ayushi Makhija [this message]
2025-10-14 9:36 ` 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=3597f849-fe69-48a5-91cb-7a0bdc9f3e7d@quicinc.com \
--to=quic_amakhija@quicinc.com \
--cc=Laurent.pinchart@ideasonboard.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=jonathan@marek.ca \
--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_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
all inboxes | Powered by JetHome®