From: Evan Green <evgreen@chromium.org>
To: Peter Rosin <peda@axentia.se>
Cc: Wolfram Sang <wsa@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Evan Green <evgreen@chromium.org>,
Peter Korsgaard <peter.korsgaard@barco.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land
Date: Fri, 16 Oct 2020 15:25:21 -0700 [thread overview]
Message-ID: <20201016222523.364218-1-evgreen@chromium.org> (raw)
The i2c-mux-gpio driver is a handy driver to have in your bag of tricks,
but it currently only works with DT-based firmware. Enable this driver
on ACPI platforms as well.
The first patch is a little dinky. Peter, if it turns out you'd rather
just take this all as a single patch, feel free to squash the first
patch into the second. Or I can resend a squashed patch if needed.
Changes in v3:
- Introduced minor &pdev->dev to dev refactor (Peter)
- Update commit message again (Peter)
- Added missing \n (Peter)
- adr64 overflow check (Peter)
- Don't initialize child (Peter)
- Limit scope of dev_handle (Peter)
Changes in v2:
- Make it compile properly when !CONFIG_ACPI (Randy)
- Update commit message regarding i2c-parent (Peter)
Evan Green (2):
i2c: i2c-mux-gpio: Factor out pdev->dev in _probe_dt()
i2c: i2c-mux-gpio: Enable this driver in ACPI land
drivers/i2c/muxes/i2c-mux-gpio.c | 112 ++++++++++++++++++++++---------
1 file changed, 82 insertions(+), 30 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-16 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 22:25 Evan Green [this message]
2020-10-16 22:25 ` [PATCH v3 1/2] i2c: i2c-mux-gpio: Factor out pdev->dev in _probe_dt() Evan Green
2020-10-16 22:25 ` [PATCH v3 2/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land Evan Green
2020-10-18 18:58 ` Andy Shevchenko
2020-10-19 16:53 ` Evan Green
2020-10-27 23:00 ` Evan Green
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=20201016222523.364218-1-evgreen@chromium.org \
--to=evgreen@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=peter.korsgaard@barco.com \
--cc=rdunlap@infradead.org \
--cc=wsa@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).