From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@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>
Cc: linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: media: qcom,x1e80100-camss: Add optional bus-type property
Date: Tue, 6 May 2025 11:02:28 +0200 [thread overview]
Message-ID: <c165476a-cf57-494d-92fc-0d4b4fc1eac4@kernel.org> (raw)
In-Reply-To: <20250502204142.2064496-3-vladimir.zapolskiy@linaro.org>
On 02/05/2025 22:41, Vladimir Zapolskiy wrote:
> Since CSIPHY IP on modern Qualcomm SoCs supports D-PHY and C-PHY
> interfaces, it might be necessary to specify it explicitly for some
> particular devices.
>
> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> ---
> .../devicetree/bindings/media/qcom,x1e80100-camss.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-06 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 20:41 [PATCH 0/3] dt-bindings: media: qcom,x1e80100-camss: Some minor fixes Vladimir Zapolskiy
2025-05-02 20:41 ` [PATCH 1/3] dt-bindings: media: qcom,x1e80100-camss: Tighten the property regex pattern Vladimir Zapolskiy
2025-05-06 9:01 ` Krzysztof Kozlowski
2025-05-07 9:01 ` kernel test robot
2025-05-27 12:17 ` Vladimir Zapolskiy
2025-05-27 12:26 ` Bryan O'Donoghue
2025-05-02 20:41 ` [PATCH 2/3] dt-bindings: media: qcom,x1e80100-camss: Add optional bus-type property Vladimir Zapolskiy
2025-05-06 8:44 ` Bryan O'Donoghue
2025-05-06 9:02 ` Krzysztof Kozlowski [this message]
2025-05-02 20:41 ` [PATCH 3/3] dt-bindings: media: qcom,x1e80100-camss: Remove clock-lanes port property Vladimir Zapolskiy
2025-05-06 8:49 ` Bryan O'Donoghue
2025-05-06 9:03 ` Krzysztof Kozlowski
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=c165476a-cf57-494d-92fc-0d4b4fc1eac4@kernel.org \
--to=krzk@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.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