From: sashiko-bot@kernel.org
To: "Nuno Sá" <nuno.sa@analog.com>
Cc: devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/4] hwmon: (pmbus/core) Add mapping function to pmbus_read_block_data()
Date: Fri, 11 Sep 2026 13:59:46 +0000 [thread overview]
Message-ID: <20260911135947.631F11F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260911-hwmon-max20826-support-v2-2-5e30cbd97d84@analog.com>
> This is in preparation for adding support to a device which needs to
> use it's own read_block implementation.
>
> The MAX20826 family is one such device. When not in PMBus page mode, each
> of its two rails sits at a different I2C address, so selecting the rail
> cannot be done through pmbus_set_page() and has to be handled by the
> driver.
>
> Signed-off-by: Nuno Sá <nuno.sa@analog.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260911-hwmon-max20826-support-v2-0-5e30cbd97d84@analog.com?part=2
next prev parent reply other threads:[~2026-09-11 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 13:53 [PATCH v2 0/4] hwmon: (pmbus) Add support for MAX20826 and similar devices Nuno Sá
2026-09-11 13:53 ` [PATCH v2 1/4] hwmon: (pmbus/core) increase number of phases and add new mask Nuno Sá
2026-09-11 14:09 ` sashiko-bot
2026-09-11 14:32 ` Guenter Roeck
2026-09-12 14:20 ` Guenter Roeck
2026-09-11 13:53 ` [PATCH v2 2/4] hwmon: (pmbus/core) Add mapping function to pmbus_read_block_data() Nuno Sá
2026-09-11 13:59 ` sashiko-bot [this message]
2026-09-12 14:21 ` Guenter Roeck
2026-09-11 13:53 ` [PATCH v2 3/4] dt-bindings: hwmon/pmbus: Document MAX20826 and similar devices Nuno Sá
2026-09-11 14:00 ` sashiko-bot
2026-09-12 10:21 ` Conor Dooley
2026-09-12 14:21 ` Guenter Roeck
2026-09-11 13:53 ` [PATCH v2 4/4] hwmon: (pmbus) add support for " Nuno Sá
2026-09-12 14:22 ` 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=20260911135947.631F11F00893@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=nuno.sa@analog.com \
--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 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.