From: Patrick Rudolph <patrick.rudolph@9elements.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-i2c@vger.kernel.org
Cc: Patrick Rudolph <patrick.rudolph@9elements.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [v7 0/3] Add support for Maxim MAX735x/MAX736x variants
Date: Tue, 5 Apr 2022 14:05:48 +0200 [thread overview]
Message-ID: <20220405120552.433415-1-patrick.rudolph@9elements.com> (raw)
v7:
- Reworked the commit message, comments and renamed a struct
field. No functional change.
v6:
- Fix typo in dt-bindings
v5:
- Remove optional and make vdd-supply mandatory
v4:
- Add missing maxitems dt-bindings property
v3:
- Merge dt-bindings into i2c-mux-pca954x.yaml
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 (3):
dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants
i2c: muxes: pca954x: Add MAX735x/MAX736x support
i2c: muxes: pca954x: Add regulator support
.../bindings/i2c/i2c-mux-pca954x.yaml | 44 ++++--
drivers/i2c/muxes/Kconfig | 4 +-
drivers/i2c/muxes/i2c-mux-pca954x.c | 126 ++++++++++++++++--
3 files changed, 153 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2022-04-05 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 12:05 Patrick Rudolph [this message]
2022-04-05 12:05 ` [v7 1/3] dt-bindings: i2c: Add Maxim MAX735x/MAX736x variants Patrick Rudolph
2022-04-05 13:46 ` Laurent Pinchart
2022-04-06 18:43 ` Rob Herring
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=20220405120552.433415-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 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 NNTP newsgroup(s).