[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240802152435.35796-1-jorcrous@amazon.com>
Date: Fri, 2 Aug 2024 15:24:32 +0000
From: Jordan Crouse <jorcrous@...zon.com>
To: <linux-media@...r.kernel.org>
CC: Bryan O'Donoghue <bryan.odonoghue@...aro.org>, Mauro Carvalho Chehab
<mchehab@...nel.org>, Robert Foss <rfoss@...nel.org>, Todor Tomov
<todor.too@...il.com>, <linux-arm-msm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH v1 0/2] media: camss: Fixups for large capture frames
A few small issues discovered while (thus far unsuccessfully) trying to bring
up a 64MP sensor. The chosen frame limitation of 8192 seems to be somewhat
arbitrary as there don't appear to be any hardware limits on maximum frame size.
Double the maximum allowable frame size to accommodate bigger sensors.
Next the larger data sizes end up needing bigger pixel clocks. This exposed a
bug for 8250 devices where the VFE clocks are shared between two blocks, but
the CSID block is being initialized second and overwriting the carefully
selected clock rates from VFE. This was likely not a problem earlier because
the lowest VFE clock rate that CSID was selecting was good enough for the
family of sensors that were being used.
Jordan Crouse (2):
media: camss: Increase the maximum frame size
media: camss: Avoid overwriting vfe clock rates for 8250
.../media/platform/qcom/camss/camss-csid.c | 8 +++----
.../media/platform/qcom/camss/camss-csiphy.c | 4 ++--
.../media/platform/qcom/camss/camss-ispif.c | 4 ++--
drivers/media/platform/qcom/camss/camss-vfe.c | 4 ++--
.../media/platform/qcom/camss/camss-video.c | 6 +++---
drivers/media/platform/qcom/camss/camss.c | 21 +++++++++++++------
6 files changed, 28 insertions(+), 19 deletions(-)
--
2.40.1
Powered by blists - more mailing lists