From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
Cc: Bryan O'Donoghue <bod@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] media: qcom: camss: vfe: Add support for VFE 900
Date: Sun, 20 Sep 2026 15:17:49 +0800 [thread overview]
Message-ID: <aq-Ina0nVQTBTL0-@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <20260915-nord-v1-4-20db41a7f1ff@oss.qualcomm.com>
On Tue, Sep 15, 2026 at 05:34:14PM +0800, Wenmeng Liu wrote:
> The VFE on the Nord platform reuses the gen4 VFE driver but places its
> bus registers at a different base and does not implement the write
> master CGC override register. Add a VFE 900 variant to the gen4 driver
> to handle the different bus register base, the separate location of the
> test bus control register, and to skip the missing CGC override
> register.
Are you saying VFE 900 has no CGC override register? Hardware document
seems suggest there is TITAN_A_RT_0_IFE_0_CLC_BUS_WR_INPUT_IF_CGC_OVERRIDE
at bus-module + 0x08.
Shawn
>
> In addition, the v900 ADDR_IMAGE register takes a full byte address
> rather than the 256-byte-unit encoding used by the gen4 baseline, and
> the full IFE write master client map places the RDI clients at index 28
> (the lite instances keep RDI0 at client 0).
>
> Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
next prev parent reply other threads:[~2026-09-20 7:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:34 [PATCH 0/6] media: qcom: camss: Add support for Nord CAMSS Wenmeng Liu
2026-09-15 9:34 ` [PATCH 1/6] dt-bindings: media: Add bindings for qcom,nord-camss Wenmeng Liu
2026-09-15 9:45 ` sashiko-bot
2026-09-17 10:13 ` Krzysztof Kozlowski
2026-09-17 12:37 ` Wenmeng Liu
2026-09-18 6:47 ` Krzysztof Kozlowski
2026-09-18 7:08 ` Wenmeng Liu
2026-09-15 9:34 ` [PATCH 2/6] media: qcom: camss: csid: Add support for CSID 900 Wenmeng Liu
2026-09-15 9:50 ` sashiko-bot
2026-09-20 7:01 ` Shawn Guo
2026-09-15 9:34 ` [PATCH 3/6] media: qcom: camss: vfe: Add support for VFE gen4 Wenmeng Liu
2026-09-15 9:53 ` sashiko-bot
2026-09-20 7:19 ` Shawn Guo
2026-09-15 9:34 ` [PATCH 4/6] media: qcom: camss: vfe: Add support for VFE 900 Wenmeng Liu
2026-09-15 9:43 ` sashiko-bot
2026-09-20 7:17 ` Shawn Guo [this message]
2026-09-15 9:34 ` [PATCH 5/6] media: qcom: camss: tpg: Add support for TPG v2.5.0 Wenmeng Liu
2026-09-15 9:34 ` [PATCH 6/6] media: qcom: camss: Add support for nord camss Wenmeng Liu
[not found] ` <6aa92fc5.2eca3aba.387881.68f4@mx.google.com>
2026-09-16 2:57 ` [0/6] media: qcom: camss: Add support for Nord CAMSS Wenmeng Liu
2026-09-17 10:57 ` Bryan O'Donoghue
2026-09-17 12:39 ` Wenmeng Liu
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=aq-Ina0nVQTBTL0-@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@oss.qualcomm.com \
--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-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=vladimir.zapolskiy@linaro.org \
--cc=wenmeng.liu@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.