Devicetree
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bod@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Atanas Filipov <atanas.filipov@oss.qualcomm.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>,
	Jonathan Marek <jonathan@marek.ca>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Gjorgji Rosikopulos <gjorgji.rosikopulos@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: clock: qcom,camcc-sm8250: add interconnect provider
Date: Thu, 29 Oct 2026 09:57:08 +0000	[thread overview]
Message-ID: <f3790c3a-c85c-42e0-98c8-2f3826002e2d@kernel.org> (raw)
In-Reply-To: <uqtvrqp7rsmxcloz2fgzv2jbcofd3x7y6hm6plnan5mao4t5rr@6lxub7q3duti>

On 29/10/2026 01:50, Dmitry Baryshkov wrote:
>  From my PoV, CAMNOX_AXI, is just the same NoC clock, just not being
> wired through RPM/RPMh. From this point of view the clock can be
> described as as an interconnect, it gives correct abstraction: no matter
> how the camera blocks are connected or how the connection between them
> is managed in hardware / firmware / clock devices, there is a bus (aka
> interconnect) between those camera blocks. If at some point the clock
> becomes managed by RPMh, it won't (significantly) change the hardware
> description

yeah I think it should be an icc provider - perhaps interconnect nodes 
make sense, not for one clock but for a number of clocks and components 
in the system JPEG, ICP voting on the bandwidth/clocks.

TBH my point here is more we need to soak up the CPAs clock logic in an 
putative cpas_icc_set() routine since I'm... as sure as I can be that 
icc_set_bw() on its own and CCF can't really capture that logic.

---
bod

  reply	other threads:[~2026-10-29  9:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 17:06 [PATCH v3 0/3] Use icc-clk for the SM8250 camera NoC AXI clock Atanas Filipov
2026-10-16 17:06 ` [PATCH v3 1/3] dt-bindings: clock: qcom,camcc-sm8250: add interconnect provider Atanas Filipov
2026-10-20  7:12   ` Krzysztof Kozlowski
2026-10-20  7:40     ` Gjorgji Rosikopulos (Consultant)
2026-10-20 12:44     ` Atanas Filipov
2026-10-28 18:10       ` Atanas Filipov
2026-10-28 22:00         ` Bryan O'Donoghue
2026-10-29  1:50           ` Dmitry Baryshkov
2026-10-29  9:57             ` Bryan O'Donoghue [this message]
2026-10-29  7:25           ` Gjorgji Rosikopulos (Consultant)
2026-10-16 17:07 ` [PATCH v3 2/3] clk: qcom: camcc-sm8250: use icc-clk for camera NoC AXI clock Atanas Filipov
2026-10-16 17:22   ` sashiko-bot
2026-10-19 14:49   ` Dmitry Baryshkov
2026-10-20  8:20     ` Atanas Filipov
2026-10-16 17:07 ` [PATCH v3 3/3] arm64: dts: qcom: sm8250: add camcc interconnect cells Atanas Filipov
2026-10-19 14:50   ` Dmitry Baryshkov
2026-10-20  8:26     ` Atanas Filipov
2026-10-20  9:45       ` Dmitry Baryshkov
2026-10-20 12:49         ` Atanas Filipov
2026-10-28 17:45           ` Atanas Filipov
2026-10-29  1:41             ` Dmitry Baryshkov
2026-10-29  7:50               ` Atanas Filipov

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=f3790c3a-c85c-42e0-98c8-2f3826002e2d@kernel.org \
    --to=bod@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=atanas.filipov@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djakov@kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=gjorgji.rosikopulos@oss.qualcomm.com \
    --cc=jonathan@marek.ca \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=sboyd@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