From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vikram Sharma <quic_vikramsa@quicinc.com>,
rfoss@kernel.org, todor.too@gmail.com, mchehab@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
hverkuil-cisco@xs4all.nl, cros-qcom-dts-watchers@chromium.org,
catalin.marinas@arm.com, will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/7] media: qcom: camss: enable vfe 690 for qcs8300
Date: Wed, 13 Aug 2025 22:35:23 +0100 [thread overview]
Message-ID: <0a049417-6545-4cdb-95cb-cf41c810b57c@linaro.org> (raw)
In-Reply-To: <20250813053724.232494-6-quic_vikramsa@quicinc.com>
On 13/08/2025 06:37, Vikram Sharma wrote:
> The vfe in qcs8300 is version 690, it is same as vfe used in
> lemans(sa8775p). vfe gen3 have support for vfe 690.
>
> Signed-off-by: Vikram Sharma <quic_vikramsa@quicinc.com>
> ---
> drivers/media/platform/qcom/camss/camss-vfe-gen3.c | 3 ++-
> drivers/media/platform/qcom/camss/camss-vfe.c | 2 ++
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/qcom/camss/camss-vfe-gen3.c b/drivers/media/platform/qcom/camss/camss-vfe-gen3.c
> index f2001140ead1..22579617def7 100644
> --- a/drivers/media/platform/qcom/camss/camss-vfe-gen3.c
> +++ b/drivers/media/platform/qcom/camss/camss-vfe-gen3.c
> @@ -13,7 +13,8 @@
> #include "camss-vfe.h"
>
> #define IS_VFE_690(vfe) \
> - (vfe->camss->res->version == CAMSS_8775P)
> + ((vfe->camss->res->version == CAMSS_8775P) \
> + || (vfe->camss->res->version == CAMSS_8300))
I'd really prefer a patch setting the CSID and VFE versions as
properties of their respective data-structures.
BUT, again this will do for now.
>
> #define BUS_REG_BASE_690 \
> (vfe_is_lite(vfe) ? 0x480 : 0x400)
> diff --git a/drivers/media/platform/qcom/camss/camss-vfe.c b/drivers/media/platform/qcom/camss/camss-vfe.c
> index 99cbe09343f2..1d40184d7d04 100644
> --- a/drivers/media/platform/qcom/camss/camss-vfe.c
> +++ b/drivers/media/platform/qcom/camss/camss-vfe.c
> @@ -344,6 +344,7 @@ static u32 vfe_src_pad_code(struct vfe_line *line, u32 sink_code,
> case CAMSS_8x96:
> case CAMSS_8250:
> case CAMSS_8280XP:
> + case CAMSS_8300:
> case CAMSS_845:
> case CAMSS_8550:
> case CAMSS_8775P:
> @@ -1974,6 +1975,7 @@ static int vfe_bpl_align(struct vfe_device *vfe)
> case CAMSS_7280:
> case CAMSS_8250:
> case CAMSS_8280XP:
> + case CAMSS_8300:
> case CAMSS_845:
> case CAMSS_8550:
> case CAMSS_8775P:
Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
next prev parent reply other threads:[~2025-08-13 21:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 5:37 [PATCH v3 0/7] qcom: qcs8300: Add qcs8300 camss support Vikram Sharma
2025-08-13 5:37 ` [PATCH v3 1/7] media: dt-bindings: Add qcom,qcs8300-camss compatible Vikram Sharma
2025-08-13 21:31 ` Bryan O'Donoghue
2025-08-13 5:37 ` [PATCH v3 2/7] media: qcom: camss: Add qcs8300 compatible Vikram Sharma
2025-08-13 5:37 ` [PATCH v3 3/7] media: qcom: camss: Add CSIPHY support for QCS8300 Vikram Sharma
2025-08-13 21:32 ` Bryan O'Donoghue
2025-08-13 5:37 ` [PATCH v3 4/7] media: qcom: camss: enable csid 690 for qcs8300 Vikram Sharma
2025-08-13 21:33 ` Bryan O'Donoghue
2025-08-14 6:54 ` Vikram Sharma
2025-08-13 5:37 ` [PATCH v3 5/7] media: qcom: camss: enable vfe " Vikram Sharma
2025-08-13 21:35 ` Bryan O'Donoghue [this message]
2025-08-13 5:37 ` [PATCH v3 6/7] media: qcom: camss: Enumerate resources for QCS8300 Vikram Sharma
2025-08-13 5:37 ` [PATCH v3 7/7] arm64: dts: qcom: qcs8300: Add support for camss Vikram Sharma
2025-08-13 21:37 ` 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=0a049417-6545-4cdb-95cb-cf41c810b57c@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_vikramsa@quicinc.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).