From: Patrick Rudolph <patrick.rudolph@9elements.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Patrick Rudolph <patrick.rudolph@9elements.com>,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/4] Add support for Maxim MAX735x/MAX736x variants
Date: Sat, 8 Jan 2022 19:57:54 +0100 [thread overview]
Message-ID: <20220108185759.2086347-1-patrick.rudolph@9elements.com> (raw)
v2:
- Move dt-bindings to separate file
- Added support for MAX736x as they are very similar
- Fixed an issue found by kernel test robot
- Dropped max735x property and custom IRQ check
- Added MAX7357 config register defines instead of magic values
- Renamed vcc-supply to vdd-supply
Patrick Rudolph (4):
dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants
i2c: muxes: pca954x: Add MAX735x/MAX736x support
dt-bindings: i2c: Add regulator to pca954x and max735x
i2c: muxes: pca954x: Add regulator support
.../bindings/i2c/i2c-mux-max735x.yaml | 106 +++++++++++++++
.../bindings/i2c/i2c-mux-pca954x.yaml | 5 +
drivers/i2c/muxes/Kconfig | 4 +-
drivers/i2c/muxes/i2c-mux-pca954x.c | 124 ++++++++++++++++--
4 files changed, 228 insertions(+), 11 deletions(-)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-max735x.yaml
--
2.33.1
next reply other threads:[~2022-01-08 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 18:57 Patrick Rudolph [this message]
2022-01-08 18:57 ` [PATCH v2 1/4] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants Patrick Rudolph
2022-01-08 23:14 ` Laurent Pinchart
2022-01-08 18:57 ` [PATCH v2 2/4] i2c: muxes: pca954x: Add MAX735x/MAX736x support Patrick Rudolph
2022-01-08 18:57 ` [PATCH v2 3/4] dt-bindings: i2c: Add regulator to pca954x and max735x Patrick Rudolph
2022-01-08 23:17 ` Laurent Pinchart
2022-01-08 18:57 ` [PATCH v2 4/4] i2c: muxes: pca954x: Add regulator support Patrick Rudolph
2022-01-12 9:31 ` Wolfram Sang
2022-01-20 7:22 ` Patrick Rudolph
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=20220108185759.2086347-1-patrick.rudolph@9elements.com \
--to=patrick.rudolph@9elements.com \
--cc=devicetree@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.