LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: linux-i2c@vger.kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
peda@axentia.se, robh+dt@kernel.org,
Eddie James <eajames@linux.ibm.com>
Subject: [PATCH v2 0/2] i2c: mux: pca954x: Support multiple devices on a single reset line
Date: Tue, 27 Jul 2021 11:03:13 -0500 [thread overview]
Message-ID: <20210727160315.15575-1-eajames@linux.ibm.com> (raw)
Some systems connect several PCA954x devices to a single reset GPIO. For
these devices to get out of reset and probe successfully, each device must
defer the probe until the GPIO has been hogged. Accomplish this by
attempting to grab a new "reset-shared-hogged" devicetree property, but
expect it to fail with EPROBE_DEFER or EBUSY.
Changes since v1:
- Rework the patch to use a new devicetree property that we don't expect to
successfully obtain
Eddie James (2):
dt-bindings: i2c: i2c-mux-pca954x: Define the reset-shared-hogged gpio
i2c: mux: pca954x: Support multiple devices on a single reset line
.../bindings/i2c/i2c-mux-pca954x.yaml | 5 ++
drivers/i2c/muxes/i2c-mux-pca954x.c | 46 +++++++++++++++----
2 files changed, 42 insertions(+), 9 deletions(-)
--
2.27.0
next reply other threads:[~2021-07-27 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 16:03 Eddie James [this message]
2021-07-27 16:03 ` [PATCH v2 1/2] dt-bindings: i2c: i2c-mux-pca954x: Define the reset-shared-hogged gpio Eddie James
2021-07-27 16:03 ` [PATCH v2 2/2] i2c: mux: pca954x: Support multiple devices on a single reset line Eddie James
2021-08-02 20:46 ` Rob Herring
2021-08-02 21:51 ` Eddie James
2021-08-02 22:35 ` Rob Herring
2021-08-04 7:50 ` Peter Rosin
2021-08-04 13:28 ` Rob Herring
2021-08-04 15:12 ` Eddie James
2021-08-04 16:35 ` 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=20210727160315.15575-1-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--subject='Re: [PATCH v2 0/2] i2c: mux: pca954x: Support multiple devices on a single reset line' \
/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
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).