From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH 0/2] i2c: gpio: fault-injector: add two new injectors
Date: Sun, 17 Feb 2019 13:41:24 +0100 [thread overview]
Message-ID: <20190217124126.7257-1-wsa+renesas@sang-engineering.com> (raw)
After sending out the 'lose_arbitration' injector as RFC, here is now a patch
series with that injector updated and another one added.
The first one successfully triggers an ARBITRATION_LOST interrupt on my Renesas
Lager board (R-Car H2). The other one leaves SCL low on the same board because
of the Kernel panic, so reboot handlers need to handle that. But more
interestingly, it causes a deadlock because it needs this I2C adapter to
trigger a reboot via the PMIC. This is a good testcase for the soon to be
developed master_xfer_atomic callback for the I2C core.
Wolfram Sang (2):
i2c: gpio: fault-injector: add 'lose_arbitration' injector
i2c: gpio: fault-injector: add 'inject_panic' injector
Documentation/i2c/gpio-fault-injection | 51 ++++++++++++++++++
drivers/i2c/busses/i2c-gpio.c | 97 ++++++++++++++++++++++++++++++++++
2 files changed, 148 insertions(+)
--
2.11.0
next reply other threads:[~2019-02-17 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 12:41 Wolfram Sang [this message]
2019-02-17 12:41 ` [PATCH 1/2] i2c: gpio: fault-injector: add 'lose_arbitration' injector Wolfram Sang
2019-02-18 9:17 ` Geert Uytterhoeven
2019-02-18 20:41 ` Wolfram Sang
2019-02-18 23:48 ` Peter Rosin
2019-02-19 13:13 ` Wolfram Sang
2019-02-19 14:07 ` Peter Rosin
2019-02-19 7:53 ` Geert Uytterhoeven
2019-02-19 13:18 ` Wolfram Sang
2019-02-19 13:33 ` Geert Uytterhoeven
2019-02-19 13:37 ` Wolfram Sang
2019-02-19 16:26 ` Wolfram Sang
2019-02-17 12:41 ` [PATCH 2/2] i2c: gpio: fault-injector: add 'inject_panic' injector Wolfram Sang
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=20190217124126.7257-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@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).