From: Krzysztof Kozlowski <krzk@kernel.org>
To: Almog Ben Shaul <almogbs@amazon.com>
Cc: linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
itamark@amazon.com, talel@amazon.com, farbere@amazon.com,
ayalstei@amazon.com, dwmw@amazon.com
Subject: Re: [PATCH 2/2] hwmon: Add JEDEC PMIC50x0 driver
Date: Thu, 22 Jan 2026 09:13:23 +0100 [thread overview]
Message-ID: <20260122-adamant-stereotyped-bird-e7deec@quoll> (raw)
In-Reply-To: <20260121151947.37719-3-almogbs@amazon.com>
On Wed, Jan 21, 2026 at 03:19:47PM +0000, Almog Ben Shaul wrote:
> Add hardware monitoring driver for JEDEC PMIC50x0 compliant I2C DDR5
> PMICs.
>
> The driver provides monitoring for voltage, current, power, and
> temperature across multiple channels, along with comprehensive error
> reporting.
>
> Signed-off-by: Almog Ben Shaul <almogbs@amazon.com>
> Tested-by: Almog Ben Shaul <almogbs@amazon.com>
Drop. You cannot send it untested, read submitting patches. The tag is
for OTHER people to test, not create impression that all code is
untested but here you did some testing.
> ---
...
> +
> +static int pmic50x0_panic_callback(struct notifier_block *nb,
> + unsigned long action, void *data)
> +{
> + struct pmic50x0 *pmic50x0 = container_of(nb, struct pmic50x0, panic_notifier);
> +
> + dev_emerg(pmic50x0->dev, "volt(mV): A=%ld, B=%ld, C=%ld, D=%ld\n",
> + pmic50x0->last_voltage[0], pmic50x0->last_voltage[1],
> + pmic50x0->last_voltage[2], pmic50x0->last_voltage[3]);
You did not Cc any maintainers, so maybe one of your 5 CCs from Amazon
can explain me why exactly random hwmon driver should receive panic
callbacks? Do you see such pattern in hwmon?
> +
> + return NOTIFY_DONE;
> +}
> +
> +static void pmic50x0_panic_notifier_unregister(void *data)
> +{
> + struct pmic50x0 *pmic50x0 = data;
> +
> + atomic_notifier_chain_unregister(&panic_notifier_list, &pmic50x0->panic_notifier);
> +}
> +
> +static int pmic50x0_panic_notifier_register(struct pmic50x0 *pmic50x0)
> +{
> + struct notifier_block *panic_notifier = &pmic50x0->panic_notifier;
> + struct device *dev = pmic50x0->dev;
> + int ret;
> +
> + panic_notifier->notifier_call = pmic50x0_panic_callback;
> + panic_notifier->priority = 0;
> +
> + ret = atomic_notifier_chain_register(&panic_notifier_list, panic_notifier);
> + if (ret) {
> + dev_err(dev, "failed to register panic notifier (%d)\n", ret);
> + return ret;
> + }
> +
> + return devm_add_action_or_reset(dev, pmic50x0_panic_notifier_unregister, pmic50x0);
> +}
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-22 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:19 [PATCH 0/2] hwmon: Add JEDEC PMIC50x0 driver for DDR5 PMICs Almog Ben Shaul
2026-01-21 15:19 ` [PATCH 1/2] dt-bindings: trivial-devices: Add jedec,pmic50x0 Almog Ben Shaul
2026-01-22 8:10 ` Krzysztof Kozlowski
2026-01-27 17:12 ` Guenter Roeck
2026-01-21 15:19 ` [PATCH 2/2] hwmon: Add JEDEC PMIC50x0 driver Almog Ben Shaul
2026-01-22 8:13 ` Krzysztof Kozlowski [this message]
2026-01-27 0:08 ` Guenter Roeck
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=20260122-adamant-stereotyped-bird-e7deec@quoll \
--to=krzk@kernel.org \
--cc=almogbs@amazon.com \
--cc=ayalstei@amazon.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.com \
--cc=farbere@amazon.com \
--cc=itamark@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=talel@amazon.com \
/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