From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] media: qcom: camss: Add sc8280xp resources
Date: Tue, 16 Jan 2024 13:42:18 +0100 [thread overview]
Message-ID: <efadbf5d-bec9-4127-8928-ea0def4326fc@linaro.org> (raw)
In-Reply-To: <20240111-linux-next-24-01-09-sc8280xp-camss-changes-v1-3-b92a650121ba@linaro.org>
On 1/11/24 20:57, Bryan O'Donoghue wrote:
> This commit describes the hardware layout for the sc8280xp for the
> following hardware blocks:
>
> - 4 x VFE, 4 RDI per VFE
> - 4 x VFE Lite, 4 RDI per VFE
> - 4 x CSID
> - 4 x CSID Lite
> - 4 x CSI PHY
>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
>
> ---
[...]
> +static const struct camss_subdev_resources csiphy_res_sc8280xp[] = {
> + /* CSIPHY0 */
Are there any cases where a platform has PHYs with different
capabilities? Might be another nice thing to clean up in the
future..
[...]
> +
> +static const struct camss_subdev_resources vfe_res_sc8280xp[] = {
> + /* IFE0 */
> + {
> + .regulators = {},
> + .clock = { "gcc_axi_hf", "gcc_axi_sf", "cpas_ahb", "camnoc_axi", "vfe0", "vfe0_axi" },
VFE->IFE?
> + .clock_rate = { { 0 },
> + { 0 },
> + { 19200000, 80000000},
Missing space
Also, the source of this clock has shared_ops, which means it's
parked to XO on disable.. Is the first frequency here useful?
> + { 19200000, 150000000, 266666667, 320000000, 400000000, 480000000 },
Similar story here
> + { 400000000, 558000000, 637000000, 760000000 },
And you (perhaps correctly) omitted 19.2MHz here
Same story for all other IFE/_LITEs in this patch
> +
> +static const struct resources_icc icc_res_sc8280xp[] = {
> + {
> + .name = "cam_ahb",
> + .icc_bw_tbl.avg = 150000,
> + .icc_bw_tbl.peak = 300000,
> + },
> + {
> + .name = "cam_hf_mnoc",
> + .icc_bw_tbl.avg = 2097152,
> + .icc_bw_tbl.peak = 2097152,
> + },
> + {
> + .name = "cam_sf_mnoc",
> + .icc_bw_tbl.avg = 2097152,
> + .icc_bw_tbl.peak = 2097152,
> + },
> + {
> + .name = "cam_sf_icp_mnoc",
> + .icc_bw_tbl.avg = 2097152,
> + .icc_bw_tbl.peak = 2097152,
Mbps_to_icc()?
> static const struct of_device_id camss_dt_match[] = {
> { .compatible = "qcom,msm8916-camss", .data = &msm8916_resources },
> { .compatible = "qcom,msm8996-camss", .data = &msm8996_resources },
> { .compatible = "qcom,sdm660-camss", .data = &sdm660_resources },
> { .compatible = "qcom,sdm845-camss", .data = &sdm845_resources },
> { .compatible = "qcom,sm8250-camss", .data = &sm8250_resources },
> + { .compatible = "qcom,sc8280xp-camss", .data = &sc8280xp_resources },
"sc" < "sd"
Konrad
next prev parent reply other threads:[~2024-01-16 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 19:57 [PATCH 0/5] media: qcom: camss: Add sc8280xp support Bryan O'Donoghue
2024-01-11 19:57 ` [PATCH 1/5] media: qcom: camss: csiphy-3ph: Add Gen2 v1.1 two-phase MIPI CSI-2 DPHY init Bryan O'Donoghue
2024-01-11 19:57 ` [PATCH 2/5] media: qcom: camss: Add CAMSS_SC8280XP enum Bryan O'Donoghue
2024-01-11 19:57 ` [PATCH 3/5] media: qcom: camss: Add sc8280xp resources Bryan O'Donoghue
2024-01-16 12:42 ` Konrad Dybcio [this message]
2024-01-11 19:57 ` [PATCH 4/5] media: qcom: camss: Add sc8280xp support Bryan O'Donoghue
2024-01-11 19:57 ` [PATCH 5/5] media: qcom: camss: vfe-17x: Rename camss-vfe-170 to camss-vfe-17x Bryan O'Donoghue
2024-01-11 20:13 ` [PATCH 0/5] media: qcom: camss: Add sc8280xp support Konrad Dybcio
2024-01-12 0:05 ` Bryan O'Donoghue
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=efadbf5d-bec9-4127-8928-ea0def4326fc@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.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