From: Damien Le Moal <dlemoal@kernel.org>
To: Louis Sautier <sautier.louis@gmail.com>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
Ranjan Kumar <ranjan.kumar@broadcom.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
MPT-FusionLinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 RESEND 1/2] scsi: mpt3sas: add IO Unit Page 7 config accessor
Date: Wed, 10 Jun 2026 08:12:05 +0800 [thread overview]
Message-ID: <5effba66-0d42-4d42-9833-f2c0be6874ad@kernel.org> (raw)
In-Reply-To: <20260609164423.2829699-2-sautier.louis@gmail.com>
On 2026/06/10 0:44, Louis Sautier wrote:
> Add mpt3sas_config_get_iounit_pg7(), mirroring the existing iounit
> page accessors. Used by the hwmon driver added in the following patch
> to read the IOC and board temperatures.
>
> Assisted-by: Claude:claude-opus-4-7
> Signed-off-by: Louis Sautier <sautier.louis@gmail.com>
> ---
> drivers/scsi/mpt3sas/mpt3sas_base.h | 2 ++
> drivers/scsi/mpt3sas/mpt3sas_config.c | 36 +++++++++++++++++++++++++++
> 2 files changed, 38 insertions(+)
>
> diff --git a/drivers/scsi/mpt3sas/mpt3sas_base.h b/drivers/scsi/mpt3sas/mpt3sas_base.h
> index d4597d058705..c655742d0dde 100644
> --- a/drivers/scsi/mpt3sas/mpt3sas_base.h
> +++ b/drivers/scsi/mpt3sas/mpt3sas_base.h
> @@ -1904,6 +1904,8 @@ int mpt3sas_config_get_iounit_pg3(struct MPT3SAS_ADAPTER *ioc,
> Mpi2ConfigReply_t *mpi_reply, Mpi2IOUnitPage3_t *config_page, u16 sz);
> int mpt3sas_config_set_iounit_pg1(struct MPT3SAS_ADAPTER *ioc, Mpi2ConfigReply_t
> *mpi_reply, Mpi2IOUnitPage1_t *config_page);
> +int mpt3sas_config_get_iounit_pg7(struct MPT3SAS_ADAPTER *ioc,
> + Mpi2ConfigReply_t *mpi_reply, Mpi2IOUnitPage7_t *config_page);
> int mpt3sas_config_get_iounit_pg8(struct MPT3SAS_ADAPTER *ioc, Mpi2ConfigReply_t
> *mpi_reply, Mpi2IOUnitPage8_t *config_page);
> int mpt3sas_config_get_sas_iounit_pg1(struct MPT3SAS_ADAPTER *ioc,
> diff --git a/drivers/scsi/mpt3sas/mpt3sas_config.c b/drivers/scsi/mpt3sas/mpt3sas_config.c
> index 45ac853e1289..ef07825046bc 100644
> --- a/drivers/scsi/mpt3sas/mpt3sas_config.c
> +++ b/drivers/scsi/mpt3sas/mpt3sas_config.c
> @@ -991,6 +991,42 @@ mpt3sas_config_get_iounit_pg3(struct MPT3SAS_ADAPTER *ioc,
> return r;
> }
>
> +/**
> + * mpt3sas_config_get_iounit_pg7 - obtain iounit page 7
> + * @ioc: per adapter object
> + * @mpi_reply: reply mf payload returned from firmware
> + * @config_page: contents of the config page
> + * Context: sleep.
> + *
> + * Return: 0 for success, non-zero for failure.
> + */
> +int
> +mpt3sas_config_get_iounit_pg7(struct MPT3SAS_ADAPTER *ioc,
Please do not break the line after "int"
> + Mpi2ConfigReply_t *mpi_reply, Mpi2IOUnitPage7_t *config_page)
> +{
> + Mpi2ConfigRequest_t mpi_request;
> + int r;
> +
> + memset(&mpi_request, 0, sizeof(Mpi2ConfigRequest_t));
> + mpi_request.Function = MPI2_FUNCTION_CONFIG;
> + mpi_request.Action = MPI2_CONFIG_ACTION_PAGE_HEADER;
> + mpi_request.Header.PageType = MPI2_CONFIG_PAGETYPE_IO_UNIT;
> + mpi_request.Header.PageNumber = 7;
> + mpi_request.Header.PageVersion = MPI2_IOUNITPAGE7_PAGEVERSION;
> + ioc->build_zero_len_sge_mpi(ioc, &mpi_request.PageBufferSGE);
> + r = _config_request(ioc, &mpi_request, mpi_reply,
> + MPT3_CONFIG_PAGE_DEFAULT_TIMEOUT, NULL, 0);
r = _config_request(ioc, &mpi_request, mpi_reply,
MPT3_CONFIG_PAGE_DEFAULT_TIMEOUT, NULL, 0);
is a lot nicer to read.
> + if (r)
> + goto out;
> +
> + mpi_request.Action = MPI2_CONFIG_ACTION_PAGE_READ_CURRENT;
> + r = _config_request(ioc, &mpi_request, mpi_reply,
> + MPT3_CONFIG_PAGE_DEFAULT_TIMEOUT, config_page,
> + sizeof(*config_page));
Same here, please align the arguments.
r = _config_request(ioc, &mpi_request, mpi_reply,
MPT3_CONFIG_PAGE_DEFAULT_TIMEOUT,
config_page, sizeof(*config_page));
With that, looks OK to me.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-06-10 0:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 16:44 [PATCH v3 RESEND 0/2] scsi: mpt3sas: add hwmon support Louis Sautier
2026-06-09 16:44 ` [PATCH v3 RESEND 1/2] scsi: mpt3sas: add IO Unit Page 7 config accessor Louis Sautier
2026-06-10 0:12 ` Damien Le Moal [this message]
2026-06-11 16:38 ` Louis Sautier
2026-06-11 23:32 ` Damien Le Moal
2026-06-09 16:44 ` [PATCH v3 RESEND 2/2] scsi: mpt3sas: add hwmon support Louis Sautier
2026-06-10 0:22 ` Damien Le Moal
2026-06-11 16:39 ` Louis Sautier
2026-06-11 23:34 ` Damien Le Moal
2026-06-22 11:20 ` Louis Sautier
2026-06-22 11:28 ` Damien Le Moal
2026-06-30 0:13 ` Louis Sautier
2026-06-30 0:19 ` Damien Le Moal
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=5effba66-0d42-4d42-9833-f2c0be6874ad@kernel.org \
--to=dlemoal@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=martin.petersen@oracle.com \
--cc=ranjan.kumar@broadcom.com \
--cc=sathya.prakash@broadcom.com \
--cc=sautier.louis@gmail.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.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
all inboxes | Powered by JetHome®