From: sashiko-bot@kernel.org
To: "Oleksij Rempel" <o.rempel@pengutronix.de>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
linux-hwmon@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v14 5/6] hwmon: add NXP MC33978/MC34978 driver
Date: Fri, 22 May 2026 06:47:51 +0000 [thread overview]
Message-ID: <20260522064751.B2FE11F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260522044855.1772639-6-o.rempel@pengutronix.de>
> Add hardware monitoring support for the NXP MC33978/MC34978 Multiple
> Switch Detection Interface (MSDI).
>
> The hardware utilizes a clear-on-read FAULT register, but physical
> faults remain asserted as long as the underlying condition exists. This
> asserts a global FAULT_STAT bit on the SPI bus. To handle this without
> trapping the CPU in an interrupt storm, this driver implements the
> following architecture:
> - Requests a rising-edge nested IRQ (IRQF_TRIGGER_RISING) from the MFD
> core to catch the initial 0 -> 1 transition of the global fault state.
> - Caches hwmon-specific alarm bits and calculates state edges (XOR) to
> isolate alarm transitions from system integrity faults.
> - Implements a 1Hz delayed workqueue that polls the hardware as long as
> any alarm is active. This compensates for the edge-triggered IRQ by
> discovering secondary faults that occur without a rising edge, and
> detecting when the hardware clears.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260522044855.1772639-1-o.rempel@pengutronix.de?part=5
next prev parent reply other threads:[~2026-05-22 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 4:48 [PATCH v14 0/6] mfd: Add support for NXP MC33978/MC34978 MSDI Oleksij Rempel
2026-05-22 4:48 ` [PATCH v14 1/6] dt-bindings: pinctrl: add " Oleksij Rempel
2026-05-22 4:58 ` sashiko-bot
2026-05-22 4:48 ` [PATCH v14 2/6] mfd: add NXP MC33978/MC34978 core driver Oleksij Rempel
2026-05-22 5:24 ` sashiko-bot
2026-05-22 4:48 ` [PATCH v14 3/6] pinctrl: core: Make pin group callbacks optional for pin-only drivers Oleksij Rempel
2026-05-22 5:55 ` sashiko-bot
2026-05-22 4:48 ` [PATCH v14 4/6] pinctrl: add NXP MC33978/MC34978 pinctrl driver Oleksij Rempel
2026-05-22 6:22 ` sashiko-bot
2026-05-22 4:48 ` [PATCH v14 5/6] hwmon: add NXP MC33978/MC34978 driver Oleksij Rempel
2026-05-22 6:47 ` sashiko-bot [this message]
2026-05-22 4:48 ` [PATCH v14 6/6] mux: add NXP MC33978/MC34978 AMUX driver Oleksij Rempel
2026-05-22 7:09 ` sashiko-bot
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=20260522064751.B2FE11F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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