From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Richard Acayan <mailingradian@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Cc: Robert Mader <robert.mader@collabora.com>
Subject: Re: [PATCH v3 3/4] arm64: dts: qcom: sdm670: remove camss endpoint nodes
Date: Wed, 8 Oct 2025 12:05:55 +0200 [thread overview]
Message-ID: <95704b74-52e7-4831-bc93-d4d7aa32736f@oss.qualcomm.com> (raw)
In-Reply-To: <20250905215516.289998-9-mailingradian@gmail.com>
On 9/5/25 11:55 PM, Richard Acayan wrote:
> There is no need to add these by default for all of SDM670. Originally,
> they were added so there could be a label for each port. This is
> unnecessary if the endpoints are all added in a fixup to the camss node.
>
> Suggested-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Link: https://lore.kernel.org/r/488281f6-5e5d-4864-8220-63e2a0b2d7f2@linaro.org
my comment on that discussion is "????????"
referring to nodes by label is the least error-prone way
Konrad
next prev parent reply other threads:[~2025-10-08 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 21:55 [PATCH v3 0/4] media: i2c: IMX355 for the Pixel 3a Richard Acayan
2025-09-05 21:55 ` [PATCH v3 1/4] dt-bindings: media: i2c: Add Sony IMX355 Richard Acayan
2025-09-05 22:08 ` Sakari Ailus
2025-09-05 21:55 ` [PATCH v3 2/4] media: i2c: imx355: Support devicetree and power management Richard Acayan
2025-09-05 22:16 ` Sakari Ailus
2025-09-05 21:55 ` [PATCH v3 3/4] arm64: dts: qcom: sdm670: remove camss endpoint nodes Richard Acayan
2025-10-08 10:05 ` Konrad Dybcio [this message]
2025-10-08 15:51 ` Dmitry Baryshkov
2025-09-05 21:55 ` [PATCH v3 4/4] arm64: dts: qcom: sdm670-google-sargo: add imx355 front camera Richard Acayan
2025-10-08 10:08 ` Konrad Dybcio
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=95704b74-52e7-4831-bc93-d4d7aa32736f@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=mchehab@kernel.org \
--cc=robert.mader@collabora.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.com \
/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