From: Matt Ranostay <matt.ranostay@konsulko.com>
To: gupt21@gmail.com, jic23@kernel.org
Cc: linux-i2c@vger.kernel.org, linux-iio@vger.kernel.org,
linux-input@vger.kernel.org,
Matt Ranostay <matt.ranostay@konsulko.com>
Subject: [PATCH v4 0/5] HID: mcp2221: iio support and device resource management
Date: Tue, 20 Sep 2022 23:30:21 -0700 [thread overview]
Message-ID: <20220921063026.89619-1-matt.ranostay@konsulko.com> (raw)
This patchset is primarily to enable iio support for the MCP2221 HID driver,
but requires several Kconfig changes and device resource management.
First attempt of this patchset is referenced here:
Link: https://lore.kernel.org/all/20220729154723.99947-1-matt.ranostay@xxxxxxxxxxxx/
Changes from v1:
* Fixing various Kconfig recursive dependencies that appear with 'imply IIO'
* Switch hid-mcp2221 driver to device managed resources for i2c support
* Reworking patchset per advice on lore.kernel.org link above
Changes from v2:
* add linux-iio list to CC
Changes from v3:
* replace .remove() tasks with devm_add_action_or_reset() in .probe()
* reschedule SRAM configuration read on failures
* add IIO_CHAN_INFO_SCALE values for ADC + DAC based on reference voltage
Matt Ranostay (5):
i2c: muxes: ltc4306: fix future recursive dependencies
iio: addac: stx104: fix future recursive dependencies
iio: dac: fix future recursive dependencies
HID: mcp2221: switch i2c registration to devm functions
HID: mcp2221: add ADC/DAC support via iio subsystem
drivers/hid/Kconfig | 1 +
drivers/hid/hid-mcp2221.c | 297 ++++++++++++++++++++++++++++++++++----
drivers/i2c/muxes/Kconfig | 2 +-
drivers/iio/addac/Kconfig | 3 +-
drivers/iio/dac/Kconfig | 6 +-
5 files changed, 275 insertions(+), 34 deletions(-)
--
2.37.2
next reply other threads:[~2022-09-21 6:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 6:30 Matt Ranostay [this message]
2022-09-21 6:30 ` [PATCH v4 1/5] i2c: muxes: ltc4306: fix future recursive dependencies Matt Ranostay
2022-09-21 6:30 ` [PATCH v4 2/5] iio: addac: stx104: " Matt Ranostay
2022-09-24 16:05 ` Jonathan Cameron
2022-09-21 6:30 ` [PATCH v4 3/5] iio: dac: " Matt Ranostay
2022-09-24 16:06 ` Jonathan Cameron
2022-09-21 6:30 ` [PATCH v4 4/5] HID: mcp2221: switch i2c registration to devm functions Matt Ranostay
2022-09-21 8:04 ` Benjamin Tissoires
2022-09-21 17:57 ` Matt Ranostay
2022-09-22 23:44 ` Matt Ranostay
2022-09-23 7:03 ` Benjamin Tissoires
2022-09-23 21:22 ` Matt Ranostay
2022-09-24 16:16 ` Jonathan Cameron
2022-09-21 6:30 ` [PATCH v4 5/5] HID: mcp2221: add ADC/DAC support via iio subsystem Matt Ranostay
2022-09-22 10:23 ` kernel test robot
2022-09-24 16:25 ` Jonathan Cameron
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=20220921063026.89619-1-matt.ranostay@konsulko.com \
--to=matt.ranostay@konsulko.com \
--cc=gupt21@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@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).