From: Hangxiang Ma <hangxiang.ma@oss.qualcomm.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Bryan O'Donoghue <bod@kernel.org>,
Nihal Kumar Gupta <nihal.gupta@oss.qualcomm.com>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Suresh Vankadara <svankada@qti.qualcomm.com>,
Vikram Sharma <vikram.sharma@oss.qualcomm.com>,
linux-i2c@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-phy@lists.infradead.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v3 5/5] media: qcom: camss: Add support for Hawi
Date: Tue, 3 Nov 2026 13:29:21 +0800 [thread overview]
Message-ID: <d92a8aaa-5cef-4416-b1c9-46ecfc6b2745@oss.qualcomm.com> (raw)
In-Reply-To: <fac8cd6d-c3f7-4ed3-b0d4-7cb8a7a6f451@linaro.org>
On 11/2/2026 8:58 PM, Bryan O'Donoghue wrote:
> On 30/10/2026 15:25, Hangxiang Ma wrote:
>>> On 30/10/2026 12:43, Nihal Kumar Gupta wrote:
>>>> +static const struct camss_subdev_resources csid_res_hawi[] = {
>>>> + /* CSID0 */
>>>> + {
>>>> + .clock = { "csid", "csid_csiphy_rx" },
>>>> + .clock_rate = { { 480000000 },
>>>> + { 480000000 } },
>>>> + .reg = { "csid0" },
>>>> + .interrupt = { "csid0" },
>>>> + .csid = {
>>>> + .parent_dev_ops = &vfe_parent_dev_ops,
>>>> + .hw_ops = &csid_ops_1190,
>>>> + .formats = &csid_formats_gen2
>>>> + }
>>>
>>> This looks strange, why is there only one clock rate ?
>>>
>>> ---
>>> bod
>> Hi Bryan, the current CAMSS CSID code always selects the first
>> frequency listed for each clock in the CAMSS resource table.
>>
>> In camss-csid.c:
>>
>> [...]
>> } else if (clock->nfreqs) {
>> clk_set_rate(clock->clk, clock->freq[0]);
>> }
>> [...]
>>
>> For the CSID and CSID_CSIPHY_RX clocks, the hardware supports three
>> clock rates: 200 MHz, 300 MHz, and 480 MHz. If I remember correctly,
>> 200MHz and 300 MHz is not sufficient for the sensor's output pixel
>> rate, so we need to use the highest rate, 480 MHz, to meet the
>> bandwidth requirement. Thanks a lot.
>>
>> ---
>> Best Regards,
>> Hangxiang
>
> We have a series from Antans to address this though.
>
> We should list the clocks the SoC supports not constrain that list for
> one specific sensor on a test-case.
>
> ---
> bod
Good to know that Antans has a series addressing this. I agree that we
should list all the clock rates supported by the SoC rather than
constraining them for a specific sensor.
One additional concern: if the clock selection logic still always picks
freq[0], listing a lower rate first could leave CAMSS unable to work
properly with sensors that need higher bandwidth.
Could you please share the link to the series? I'll rebase the next
revision on top of it.
---
Best Regards,
Hangxiang
next prev parent reply other threads:[~2026-11-03 5:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 12:43 [PATCH v3 0/5] Add CAMSS support for Qualcomm Hawi and Maili Nihal Kumar Gupta
2026-10-30 12:43 ` [PATCH v3 1/5] dt-bindings: i2c: qcom,i2c-cci: Add Hawi compatible Nihal Kumar Gupta
2026-11-02 10:05 ` Krzysztof Kozlowski
2026-10-30 12:43 ` [PATCH v3 2/5] dt-bindings: phy: qcom,x1e80100-csi2-phy: Add Hawi and Maili compatibles Nihal Kumar Gupta
2026-10-30 12:43 ` [PATCH v3 3/5] dt-bindings: media: Add CAMSS device for Hawi and Maili Nihal Kumar Gupta
2026-10-30 13:38 ` Loic Poulain
2026-10-30 14:05 ` Hangxiang Ma
2026-10-30 12:43 ` [PATCH v3 4/5] phy: qcom-mipi-csi2: Add Hawi support Nihal Kumar Gupta
2026-10-30 13:39 ` Loic Poulain
2026-10-30 12:43 ` [PATCH v3 5/5] media: qcom: camss: Add support for Hawi Nihal Kumar Gupta
2026-10-30 15:04 ` Bryan O'Donoghue
2026-10-30 15:25 ` Hangxiang Ma
2026-11-02 12:58 ` Bryan O'Donoghue
2026-11-03 5:29 ` Hangxiang Ma [this message]
2026-10-30 15:05 ` Bryan O'Donoghue
2026-10-30 15:29 ` Hangxiang Ma
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=d92a8aaa-5cef-4416-b1c9-46ecfc6b2745@oss.qualcomm.com \
--to=hangxiang.ma@oss.qualcomm.com \
--cc=andi.shyti@kernel.org \
--cc=bod@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-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mani@kernel.org \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nihal.gupta@oss.qualcomm.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=svankada@qti.qualcomm.com \
--cc=vikram.sharma@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
all inboxes | Powered by JetHome®