public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Vijay Kumar Tumati <vijay.tumati@oss.qualcomm.com>,
	Bryan O'Donoghue <bod@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>
Cc: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema
Date: Mon, 23 Mar 2026 14:29:56 +0000	[thread overview]
Message-ID: <8acb3888-0ef8-440a-a680-14478bba3ed1@linaro.org> (raw)
In-Reply-To: <4b1b5b79-df37-499e-99c4-1a965a9b2455@oss.qualcomm.com>

On 23/03/2026 14:22, Konrad Dybcio wrote:
>> Sure, FYI: Dmitry, Konrad.
> I'll admit I haven't yet read up on all of the background discussions that you
> guys had on LKML, but*if* we're going to put the PHY under camss, the GDSC and
> CPAS_AHB/CAMNOC_AXI_RT references should be unnecessary, given they're not
> related strictly to this PHY itself, rather it sitting in a specific corner of
> the subsystem that needs them to be active (see related:
> https://lore.kernel.org/linux-arm-msm/cb2430f2-8601-4c72- 
> af6b-10f1ff16c188@oss.qualcomm.com/
> )

That's fair comment with the PHYs inside of the CAMSS block. Obviously 
if its outside of the block we need the full gamut of clocks defined.

..

Yeah I think I'm happy enough to drop these predicated on sub-nodes.

> For the other names, I*think* we won't need to rely on them (i.e. only operate
> the resources through PHY APIs from the V4L2 driver) and can come up with new
> ones. And hence I think we can turn "csiphy" to "core" and "csiphy_timer" to
> "timer" (because we really don't need to repeat the csiphy_ prefix)

Works for me.

---
bod

  reply	other threads:[~2026-03-23 14:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-15 23:52 [PATCH v4 0/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-03-15 23:52 ` [PATCH v4 1/2] dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema Bryan O'Donoghue
2026-03-16  1:58   ` Vladimir Zapolskiy
2026-03-16  2:45     ` Dmitry Baryshkov
2026-03-16 10:49       ` Konrad Dybcio
2026-03-16 12:09         ` Bryan O'Donoghue
2026-03-16  7:42   ` Krzysztof Kozlowski
2026-03-16 21:31   ` Vijay Kumar Tumati
2026-03-17  5:26     ` Bryan O'Donoghue
2026-03-17 20:25       ` Vijay Kumar Tumati
2026-03-23 14:22         ` Konrad Dybcio
2026-03-23 14:29           ` Bryan O'Donoghue [this message]
2026-03-15 23:52 ` [PATCH v4 2/2] phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver Bryan O'Donoghue
2026-03-16 10:12   ` Krzysztof Kozlowski
2026-03-16 12:04     ` Bryan O'Donoghue
2026-03-18 10:15   ` Neil Armstrong
2026-03-18 13:17     ` Bryan O'Donoghue
2026-03-18 15:07       ` Neil Armstrong
2026-03-18 15:27         ` Dmitry Baryshkov
2026-03-19 13:08           ` Vladimir Zapolskiy
2026-03-19 13:17             ` Bryan O'Donoghue
2026-03-19 14:05               ` Neil Armstrong
2026-03-19 15:06                 ` Bryan O'Donoghue
2026-03-19 14:56               ` Vladimir Zapolskiy
2026-03-19 15:18                 ` Bryan O'Donoghue
2026-03-19 16:08                   ` Neil Armstrong
2026-03-19 16:56                     ` Bryan O'Donoghue
2026-03-19 17:39                       ` Neil Armstrong
2026-03-20  0:37                   ` Vladimir Zapolskiy
2026-03-20  9:56                     ` Bryan O'Donoghue
2026-03-18 15:47         ` Bryan O'Donoghue
2026-03-22 16:44   ` kernel test robot
2026-03-22 23:31   ` kernel test robot

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=8acb3888-0ef8-440a-a680-14478bba3ed1@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=bod@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=vijay.tumati@oss.qualcomm.com \
    --cc=vkoul@kernel.org \
    --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