From: "Bryan O'Donoghue" <bryan.odonoghue@linaro.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, Bryan O'Donoghue <bod@kernel.org>
Subject: [PATCH 0/2] media: qcom: camss: Split VFE 690 and VFE 780/880
Date: Fri, 02 Oct 2026 16:58:58 +0100 [thread overview]
Message-ID: <20261002-vfe690-780-split-v1-0-40e15aa8716c@kernel.org> (raw)
Looking at the write-master indexes for VFE690 and VFE780/880 its clear 780
and 880 share the same indexes but 690 is significantly different.
That's enough of a difference to separate out the logic of both. Two
patches in this series do that. One patch to reverse the rename another
patch to disjunct the logic into two separate files.
Signed-off-by: Bryan O'Donoghue <bod@kernel.org>
---
Bryan O'Donoghue (2):
media: qcom: camss: vfe: Rename gen3 back to vfe780
media: qcom: camss: vfe: Separate VFE 690 from VFE 780/880
drivers/media/platform/qcom/camss/Makefile | 3 +-
.../camss/{camss-vfe-gen3.c => camss-vfe-690.c} | 49 ++-----
drivers/media/platform/qcom/camss/camss-vfe-780.c | 160 +++++++++++++++++++++
drivers/media/platform/qcom/camss/camss-vfe.h | 3 +-
drivers/media/platform/qcom/camss/camss.c | 34 ++---
5 files changed, 193 insertions(+), 56 deletions(-)
---
base-commit: 89a3d2a2237e017cdbefcb036db71ce74e67faf5
change-id: 20261002-vfe690-780-split-c40a89bd22a5
Best regards,
--
Bryan O'Donoghue <bod@kernel.org>
next reply other threads:[~2026-10-02 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 15:58 Bryan O'Donoghue [this message]
2026-10-02 15:58 ` [PATCH 1/2] media: qcom: camss: vfe: Rename gen3 back to vfe780 Bryan O'Donoghue
2026-10-02 15:59 ` [PATCH 2/2] media: qcom: camss: vfe: Separate VFE 690 from VFE 780/880 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=20261002-vfe690-780-split-v1-0-40e15aa8716c@kernel.org \
--to=bryan.odonoghue@linaro.org \
--cc=bod@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=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®