From: Julien Massot <julien.massot@collabora.com>
To: linux-media@vger.kernel.org, sakari.ailus@iki.fi
Cc: devicetree@vger.kernel.org, kernel@collabora.com,
linux-kernel@vger.kernel.org, mchehab@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, Julien Massot <julien.massot@collabora.com>
Subject: [PATCH v7 0/5] Add support for MAX96714/F and MAX96717/F GMSL2 ser/des
Date: Tue, 30 Apr 2024 15:19:26 +0200 [thread overview]
Message-ID: <20240430131931.166012-1-julien.massot@collabora.com> (raw)
Change since v6:
- Remove mention of C-PHY for MAX96717, this serializer is D-PHY only
- Remove bus-type requirement for MAX96717
- Minor changes requested by Sakari
- Workaround a MAX96717 issue, which occurs when stopping
the CSI source before stopping the MAX96717 CSI receiver.
Power management is not included in this patchset. The GMSL link is
not always resuming when the deserializer is suspended without
suspending the serializer.
Change since v5:
- Reverse fallback logic: max9671{4,7} can fallback to max9671{4,7}F
- use const instead of enum for max9671{4,7}f compatible as suggested
Change since v4:
- Add support for MAX96717 and MAX96714 and use them as a fallback for
MAX96717F and MAX96714F respectively
- The drivers are now compatible with MAX96717 and MAX96714 since no change in
the logic is needed
- Reference 'i2c-gate' instead of 'i2c-controller' in the bindings
Change since v3:
- bindings
- Renamed bindings to drop the 'f' suffix
- Add bus type to MAX96717 and remove from MAX9674
- Add lane-polarities to both bindings
- drivers
- Address changes requested by Sakari in v3
- use v4l2_subdev_s_stream_helper for MAX96714
- do not init regmap twice in the MAX96714 driver
- Fix compilations on 32 bits platforms
Change since v2:
- Convert drivers to use CCI helpers
- Use generic node name
- Use 'powerdown' as gpio name instead of 'enable'
- Add pattern generator support for MAX96714
These patches add support for Maxim MAX96714F deserializer and
MAX96717F serializer.
MAX96714F has one GMSL2 input port and one CSI2 4 lanes output port,
MAX96717F has one CSI2 input port and one GMSL2 output port.
The drivers support the tunnel mode where all the
CSI2 traffic coming from an imager is replicated through the deserializer
output port.
Both MAX96714F and MAX96717F are limited to a 3Gbps forward link rate
leaving a maximum of 2.6Gbps for the video payload.
Julien Massot (9):
dt-bindings: media: add Maxim MAX96717 GMSL2 Serializer
dt-bindings: media: add Maxim MAX96714 GMSL2 Deserializer
media: i2c: add MAX96717 driver
media: i2c: add MAX96714 driver
drivers: media: max96717: stop the csi receiver before the source
.../bindings/media/i2c/maxim,max96714.yaml | 174 +++
.../bindings/media/i2c/maxim,max96717.yaml | 157 +++
MAINTAINERS | 14 +
drivers/media/i2c/Kconfig | 34 +
drivers/media/i2c/Makefile | 2 +
drivers/media/i2c/max96714.c | 1024 +++++++++++++++++
drivers/media/i2c/max96717.c | 927 +++++++++++++++
7 files changed, 2332 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/maxim,max96714.yaml
create mode 100644 Documentation/devicetree/bindings/media/i2c/maxim,max96717.yaml
create mode 100644 drivers/media/i2c/max96714.c
create mode 100644 drivers/media/i2c/max96717.c
--
2.44.0
next reply other threads:[~2024-04-30 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 13:19 Julien Massot [this message]
2024-04-30 13:19 ` [PATCH v7 1/5] dt-bindings: media: add Maxim MAX96717 GMSL2 Serializer Julien Massot
2024-04-30 13:19 ` [PATCH v7 2/5] dt-bindings: media: add Maxim MAX96714 GMSL2 Deserializer Julien Massot
2024-04-30 13:19 ` [PATCH v7 3/5] media: i2c: add MAX96717 driver Julien Massot
2024-04-30 13:19 ` [PATCH v7 4/5] media: i2c: add MAX96714 driver Julien Massot
2024-04-30 13:19 ` [PATCH v7 5/5] drivers: media: max96717: stop the csi receiver before the source Julien Massot
2024-05-17 14:16 ` [PATCH v7 0/5] Add support for MAX96714/F and MAX96717/F GMSL2 ser/des Tommaso Merciai
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=20240430131931.166012-1-julien.massot@collabora.com \
--to=julien.massot@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).