From: Alex Tran <alex.t.tran@gmail.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Pavel Machek <pavel@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Alex Tran <alex.t.tran@gmail.com>
Subject: [PATCH v2 0/4] media: omap3isp/et8ek8: Add CCP2 CRC configuration support
Date: Sun, 14 Dec 2025 23:58:31 -0800 [thread overview]
Message-ID: <cover.1765782992.git.alex.t.tran@gmail.com> (raw)
This patch series provides support for configuring CRC checksum via device tree
for et8ek8 sensor and OMAP3 ISP receiver.
Previously, CRC was hardcoded to enabled (1) in the sensor driver and ISP
receiver. This series makes it configurable through DT, allowing both
sides to be aligned, as both must use the same CRC setting for proper CCP2
communication.
Changes maintain backward compatibility by defaulting CRC to 1 when the
property is not specified in the device tree.
The series also converts both device tree bindings from TXT to YAML
schema format, as required.
Changes in v2:
- Fixed broken patch threading
- Added receiver support for reading crc from device tree
- Converted both sensor and ISP bindings from TXT to YAML format
- Both sensor and ISP endpoints can now be configured consistently via DT
Alex Tran (4):
media: i2c: et8ek8: et8ek8_driver: add support for crc configuration
via device tree
dt-bindings: media: i2c: et8ek8: document missing crc as optional
property
media: platform: ti: omap3isp: isp: read crc configuration from device
tree for CCP2
dt-bindings: media: omap3isp: document missing crc as optional
property
.../bindings/media/i2c/toshiba,et8ek8.txt | 55 -----
.../bindings/media/i2c/toshiba,et8ek8.yaml | 99 +++++++++
.../devicetree/bindings/media/ti,omap3isp.txt | 71 -------
.../bindings/media/ti,omap3isp.yaml | 196 ++++++++++++++++++
MAINTAINERS | 1 +
drivers/media/i2c/et8ek8/et8ek8_driver.c | 49 ++++-
drivers/media/platform/ti/omap3isp/isp.c | 5 +-
7 files changed, 339 insertions(+), 137 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/media/i2c/toshiba,et8ek8.txt
create mode 100644 Documentation/devicetree/bindings/media/i2c/toshiba,et8ek8.yaml
delete mode 100644 Documentation/devicetree/bindings/media/ti,omap3isp.txt
create mode 100644 Documentation/devicetree/bindings/media/ti,omap3isp.yaml
--
2.51.0
next reply other threads:[~2025-12-15 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 7:58 Alex Tran [this message]
2025-12-15 7:58 ` [PATCH v2 1/4] media: i2c: et8ek8: et8ek8_driver: add support for crc configuration via device tree Alex Tran
2025-12-17 8:28 ` Krzysztof Kozlowski
2025-12-15 7:58 ` [PATCH v2 2/4] dt-bindings: media: i2c: et8ek8: document missing crc as optional property Alex Tran
2025-12-17 8:27 ` Krzysztof Kozlowski
2025-12-18 23:50 ` Alex Tran
2025-12-15 7:58 ` [PATCH v2 3/4] media: platform: ti: omap3isp: isp: read crc configuration from device tree for CCP2 Alex Tran
2025-12-15 7:58 ` [PATCH v2 4/4] dt-bindings: media: omap3isp: document missing crc as optional property Alex Tran
2025-12-17 8:28 ` Krzysztof Kozlowski
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=cover.1765782992.git.alex.t.tran@gmail.com \
--to=alex.t.tran@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pavel@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.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