Re: [PATCH v6 2/2] media: i2c: Add driver for IMX519 sensor

Hi Umang,

Thank you for the patch.

On Fri, Sep 08, 2023 at 08:43:44AM -0400, Umang Jain wrote:

From: Lee Jackson <redacted>

Add a driver for the 16MPix IMX519 CSI2 sensor.
Whilst the sensor supports 2 or 4 CSI2 data lanes, this driver
currently only supports 2 lanes.

The following Bayer modes are currently available:

4656x3496 10-bit @ 10fps
3840x2160 10-bit (cropped) @ 21fps
2328x1748 10-bit (binned) @ 30fps
1920x1080 10-bit (cropped/binned) @ 60fps
1280x720 10-bit (cropped/binned) @ 120fps

Signed-off-by: Lee Jackson <redacted>
Signed-off-by: Umang Jain <redacted>
---
 MAINTAINERS                |    1 +
 drivers/media/i2c/Kconfig  |   14 +
 drivers/media/i2c/Makefile |    1 +
 drivers/media/i2c/imx519.c | 1842 ++++++++++++++++++++++++++++++++++++
 4 files changed, 1858 insertions(+)
 create mode 100644 drivers/media/i2c/imx519.c

[snip]

[snip]

+/* 16 mpix 10fps */
+static const struct cci_reg_sequence mode_4656x3496_regs[] = {
+	{ CCI_REG8(0x0111), 0x02 },
+	{ CCI_REG8(0x0112), 0x0a },
+	{ CCI_REG8(0x0113), 0x0a },
+	{ CCI_REG8(0x0114), 0x01 },
+	{ CCI_REG8(0x0342), 0x42 },
+	{ CCI_REG8(0x0343), 0x00 },
+	{ CCI_REG8(0x0340), 0x0d },
+	{ CCI_REG8(0x0341), 0xf4 },
+	{ CCI_REG8(0x0344), 0x00 },
+	{ CCI_REG8(0x0345), 0x00 },
+	{ CCI_REG8(0x0346), 0x00 },
+	{ CCI_REG8(0x0347), 0x00 },
+	{ CCI_REG8(0x0348), 0x12 },
+	{ CCI_REG8(0x0349), 0x2f },
+	{ CCI_REG8(0x034a), 0x0d },
+	{ CCI_REG8(0x034b), 0xa7 },
+	{ CCI_REG8(0x0220), 0x00 },
+	{ CCI_REG8(0x0221), 0x11 },
+	{ CCI_REG8(0x0222), 0x01 },
+	{ CCI_REG8(0x0900), 0x00 },
+	{ CCI_REG8(0x0901), 0x11 },
+	{ CCI_REG8(0x0902), 0x0a },
+	{ CCI_REG8(0x3f4c), 0x01 },
+	{ CCI_REG8(0x3f4d), 0x01 },
+	{ CCI_REG8(0x4254), 0x7f },
+	{ CCI_REG8(0x0401), 0x00 },
+	{ CCI_REG8(0x0404), 0x00 },
+	{ CCI_REG8(0x0405), 0x10 },
+	{ CCI_REG8(0x0408), 0x00 },
+	{ CCI_REG8(0x0409), 0x00 },
+	{ CCI_REG8(0x040a), 0x00 },
+	{ CCI_REG8(0x040b), 0x00 },
+	{ CCI_REG8(0x040c), 0x12 },
+	{ CCI_REG8(0x040d), 0x30 },
+	{ CCI_REG8(0x040e), 0x0d },
+	{ CCI_REG8(0x040f), 0xa8 },
+	{ CCI_REG8(0x034c), 0x12 },
+	{ CCI_REG8(0x034d), 0x30 },
+	{ CCI_REG8(0x034e), 0x0d },
+	{ CCI_REG8(0x034f), 0xa8 },
+	{ CCI_REG8(0x0301), 0x06 },
+	{ CCI_REG8(0x0303), 0x04 },
+	{ CCI_REG8(0x0305), 0x04 },
+	{ CCI_REG8(0x0306), 0x01 },
+	{ CCI_REG8(0x0307), 0x57 },
+	{ CCI_REG8(0x0309), 0x0a },
+	{ CCI_REG8(0x030b), 0x02 },
+	{ CCI_REG8(0x030d), 0x04 },
+	{ CCI_REG8(0x030e), 0x01 },
+	{ CCI_REG8(0x030f), 0x49 },
+	{ CCI_REG8(0x0310), 0x01 },
+	{ CCI_REG8(0x0820), 0x07 },
+	{ CCI_REG8(0x0821), 0xb6 },
+	{ CCI_REG8(0x0822), 0x00 },
+	{ CCI_REG8(0x0823), 0x00 },
+	{ CCI_REG8(0x3e20), 0x01 },
+	{ CCI_REG8(0x3e37), 0x00 },
+	{ CCI_REG8(0x3e3b), 0x00 },
+	{ CCI_REG8(0x0106), 0x00 },
+	{ CCI_REG8(0x0b00), 0x00 },
+	{ CCI_REG8(0x3230), 0x00 },
+	{ CCI_REG8(0x3f14), 0x01 },
+	{ CCI_REG8(0x3f3c), 0x01 },
+	{ CCI_REG8(0x3f0d), 0x0a },
+	{ CCI_REG8(0x3fbc), 0x00 },
+	{ CCI_REG8(0x3c06), 0x00 },
+	{ CCI_REG8(0x3c07), 0x48 },
+	{ CCI_REG8(0x3c0a), 0x00 },
+	{ CCI_REG8(0x3c0b), 0x00 },
+	{ CCI_REG8(0x3f78), 0x00 },
+	{ CCI_REG8(0x3f79), 0x40 },
+	{ CCI_REG8(0x3f7c), 0x00 },
+	{ CCI_REG8(0x3f7d), 0x00 },
+};

Looking at the per-mode tables, it appears that all registers below
0x3000 are CCS-compliant. Furthermore, all registers from 0x3000 above
(defined in CCS as the manufacturer-specific register - or MSR - range)
are identical for all modes. I can't tell if other modes could require
different values for MSRs, so it's hard to assess real CCS compliance,
but it looks like giving the CCS driver a try would be a good idea.

I'm sure Sakari will be delighted :-)

[snip]

-- 
Regards,

Laurent Pinchart

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel