From: Wolfram Sang <wsa@kernel.org>
To: Evan Nimmo <evan.nimmo@alliedtelesis.co.nz>
Cc: andriy.shevchenko@linux.intel.com,
chris.packham@alliedtelesis.co.nz, jarkko.nikula@linux.intel.com,
jdelvare@suse.de, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after reset
Date: Wed, 9 Sep 2020 10:23:38 +0200 [thread overview]
Message-ID: <20200909082338.GC2272@ninjato> (raw)
In-Reply-To: <20200908203247.14374-1-evan.nimmo@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
On Wed, Sep 09, 2020 at 08:32:47AM +1200, Evan Nimmo wrote:
> If something goes wrong (such as the SCL being stuck low) then we need
> to reset the PCA chip. The issue with this is that on reset we lose all
> config settings and the chip ends up in a disabled state which results
> in a lock up/high CPU usage. We need to re-apply any configuration that
> had previously been set and re-enable the chip.
>
> Signed-off-by: Evan Nimmo <evan.nimmo@alliedtelesis.co.nz>
> Reviewed-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Reviewed-by: Wolfram Sang <wsa@kernel.org>
Applied to for-current, thanks!
For the record, were you able to test both, PCA9564 and PCA9665?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-09 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 20:32 [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after reset Evan Nimmo
2020-09-09 8:23 ` Wolfram Sang [this message]
2020-09-09 20:39 ` Chris Packham
2020-09-11 19:45 ` Wolfram Sang
2020-09-13 21:23 ` Chris Packham
2020-09-14 6:49 ` Wolfram Sang
2020-09-14 20:50 ` Chris Packham
2020-09-14 8:50 ` Andy Shevchenko
2020-09-14 8:51 ` Andy Shevchenko
2020-09-14 10:42 ` Stephen Rothwell
2020-09-14 11:01 ` Andy Shevchenko
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=20200909082338.GC2272@ninjato \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=evan.nimmo@alliedtelesis.co.nz \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--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.