From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: rfoss@kernel.org, todor.too@gmail.com,
bryan.odonoghue@linaro.org, agross@kernel.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
laurent.pinchart@ideasonboard.com, sakari.ailus@linux.intel.com,
andrey.konovalov@linaro.org
Cc: linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 00/10] media: qcom: camss: Bugfix series
Date: Wed, 30 Aug 2023 16:16:05 +0100 [thread overview]
Message-ID: <20230830151615.3012325-1-bryan.odonoghue@linaro.org> (raw)
V3:
- Adds Reviewed-by where indicated - Laurent
- Adds a new patch for genpd cleanup. TBH I completely missed this so thanks ! - Laurent
- "media: qcom: camss: Fix V4L2 async notifier error path" stays the same fixes spalt in -next
Fixes: 51397a4ec75d ("media: qcom: Initialise V4L2 async notifier later")
- I like the suggesting of using a common fix for vfe-17x and vfe-480 however, I believe
we need to support multiple write-master/RDI => VCs in 17x which currently we only do
in vfe-480 so sharing the code between the two here right now, is n't possible.
- Included other suggestions on vfe-17x and vfe-480 - Laurent
- I didn't change the val |= 1 << CSI2_RX_CFG1_VC_MODE to BIT(2)
The reason for that is all of the code uses this odd bit-shifting and I'd rather do
the conversion from shifting to BIT(x) as a distinct series instead of piecemeal - bod
V2:
- Amends commit log for TPG fix to cover dropping of fixed
VC when setting up a TPG - Konrad
- Leaves GENMASK etc out. I'm happy to do a "make it pretty"
series later on. - bod
Link: https://git.codelinaro.org/bryan.odonoghue/kernel/-/commits/Bugfix-series-v2?ref_type=tags
V1:
- Drops dt_id = vc * 4 in favour of a patch in a later series - Hans
Link: https://git.codelinaro.org/bryan.odonoghue/kernel/-/commit/d4c382c5d6ee153b410a01e172b3e811011d0b14
- Adds Konrad's Acked-by as indicated
V0:
This series covers a number of Fixes: all of which are for application to
stable as well as -next with the exception of the second patch which is a
fix for a SHA that is still in -next.
Link: https://git.codelinaro.org/bryan.odonoghue/kernel/-/tree/linux-next-23-08-07-db410c-rb3-camss-dts-v3
This series is part of a larger set of fixes, improvements developed/found
when adding a new SoC.
Link: https://git.codelinaro.org/bryan.odonoghue/kernel/-/tree/lenovo-x13s-v6.5-rc4-x13s-camss-patches
First pass on that larger series is to get all of the current Fixes: in the
branch out.
Andrey Konovalov (1):
media: qcom: camss: Fix csid-gen2 for test pattern generator
Bryan O'Donoghue (9):
media: qcom: camss: Fix pm_domain_on sequence in probe
media: qcom: camss: Fix V4L2 async notifier error path
media: qcom: camss: Fix genpd cleanup
media: qcom: camss: Fix vfe_get() error jump
media: qcom: camss: Fix VFE-17x vfe_disable_output()
media: qcom: camss: Fix VFE-480 vfe_disable_output()
media: qcom: camss: Fix missing vfe_lite clocks check
media: qcom: camss: Fix invalid clock enable bit disjunction
media: qcom: camss: Fix set CSI2_RX_CFG1_VC_MODE when VC is greater
than 3
.../platform/qcom/camss/camss-csid-gen2.c | 11 ++--
.../qcom/camss/camss-csiphy-3ph-1-0.c | 2 +-
.../media/platform/qcom/camss/camss-vfe-170.c | 22 +-------
.../media/platform/qcom/camss/camss-vfe-480.c | 22 +-------
drivers/media/platform/qcom/camss/camss-vfe.c | 5 +-
drivers/media/platform/qcom/camss/camss.c | 55 +++++++++++--------
6 files changed, 46 insertions(+), 71 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-30 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 15:16 Bryan O'Donoghue [this message]
2023-08-30 15:16 ` [PATCH v3 01/10] media: qcom: camss: Fix pm_domain_on sequence in probe Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 02/10] media: qcom: camss: Fix V4L2 async notifier error path Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 03/10] media: qcom: camss: Fix genpd cleanup Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 04/10] media: qcom: camss: Fix vfe_get() error jump Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 05/10] media: qcom: camss: Fix VFE-17x vfe_disable_output() Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 06/10] media: qcom: camss: Fix VFE-480 vfe_disable_output() Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 07/10] media: qcom: camss: Fix missing vfe_lite clocks check Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 08/10] media: qcom: camss: Fix invalid clock enable bit disjunction Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 09/10] media: qcom: camss: Fix set CSI2_RX_CFG1_VC_MODE when VC is greater than 3 Bryan O'Donoghue
2023-08-30 15:16 ` [PATCH v3 10/10] media: qcom: camss: Fix csid-gen2 for test pattern generator Bryan O'Donoghue
2023-08-30 18:35 ` [PATCH v3 00/10] media: qcom: camss: Bugfix series Bryan O'Donoghue
2023-08-30 20:47 ` Laurent Pinchart
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=20230830151615.3012325-1-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konrad.dybcio@linaro.org \
--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=sakari.ailus@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).