From: Lee Trager <lee@trager.us>
To: Andre Przywara <andre.przywara@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Hanjun Guo <guohanjun@huawei.com>,
Sudeep Holla <sudeep.holla@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, James Morse <james.morse@arm.com>,
Ben Horgan <ben.horgan@arm.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Fenghua Yu <fenghuay@nvidia.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Srivathsa L Rao <srivathsa.rao@oss.qualcomm.com>,
Ganapatrao Kulkarni <ganapatrao.kulkarni@oss.qualcomm.com>,
Trilok Soni <tsoni@quicinc.com>,
Srinivas Ramana <sramana@qti.qualcomm.com>,
Niyas Sait <niyas.sait@arm.com>,
Ritwick Sharma <ritwick.sharma@arm.com>,
Gavin Shan <gshan@redhat.com>,
linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 10/12] arm_mpam: add MPAM-Fb MSC firmware access support
Date: Mon, 31 Aug 2026 15:19:59 -0700 [thread overview]
Message-ID: <948381d2-8ba7-458b-b729-d5398e0a8559@trager.us> (raw)
In-Reply-To: <20260807105451.3728284-11-andre.przywara@arm.com>
On 8/7/26 3:54 AM, Andre Przywara wrote:
> +
> +static int mpam_fb_send_request(struct mpam_msc *msc, u32 msc_id,
> + u16 reg, u32 *result, int mpam_fb_command)
> +{
> + unsigned int token = atomic_inc_return(&mpam_fb_token);
> + struct acpi_pcct_ext_pcc_shared_memory __iomem *pcc_shmem;
> + struct mpam_pcc_chan *pcc_chan;
> + struct pcc_mbox_chan *chan;
> + void __iomem *payload_ofs;
> + int mpam_fb_err = 0;
> + u32 status;
> + int ret;
> +
> + pcc_chan = msc->pcc_chan;
> + if (!pcc_chan)
> + return -ENODEV;
> +
> + chan = pcc_chan->pcc_chan;
> +
> + /* prune token to fit into the 10 bits inside the command register */
> + token = FIELD_GET(MPAM_MSC_TOKEN_MASK,
> + FIELD_PREP(MPAM_MSC_TOKEN_MASK, token));
> +
> + mutex_lock(&pcc_chan->pcc_chan_lock);
> +
> + switch (mpam_fb_command) {
> + case MPAM_PROTOCOL_VERSION_CMD:
> + mpam_fb_build_version_message(token, chan->shmem);
> + break;
> + case MPAM_MSC_READ_CMD:
> + mpam_fb_build_read_message(msc_id, reg, token, chan->shmem);
> + break;
> + case MPAM_MSC_WRITE_CMD:
> + mpam_fb_build_write_message(msc_id, reg, *result,
> + token, chan->shmem);
> + break;
> + default:
> + dev_err(&msc->pdev->dev, "unsupported MPAM-Fb command %d\n",
> + mpam_fb_command);
> + ret = -EINVAL;
> + goto out_err;
> + }
> +
> + ret = mbox_send_message(chan->mchan, NULL);
> + if (ret < 0)
> + goto out_err;
> +
While testing this series when building arm64 allnoconfig with
CONFIG_ARM4_MPAM=y I got a link failure:
drivers/resctrl/mpam_fb.o: undefined reference to `mbox_send_message`
Since the ACPI MPAM-Fb transport also reqiures PCC, wold it make sense
for ARM64_MPAM_DRIVER to select both dependencies?
select MAILBOX
select PCC if ACPI
Lee
next prev parent reply other threads:[~2026-08-31 22:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 10:54 [PATCH v9 00/12] arm_mpam: Add MPAM-Fb firmware support Andre Przywara
2026-08-07 10:54 ` [PATCH v9 01/12] arm_mpam: let low level MSC accessors return an error Andre Przywara
2026-08-07 10:54 ` [PATCH v9 02/12] arm_mpam: propagate MSC access errors for hw_probe functions Andre Przywara
2026-08-07 10:54 ` [PATCH v9 03/12] arm_mpam: propagate MSC access errors for MBWU counters Andre Przywara
2026-08-07 10:54 ` [PATCH v9 04/12] arm_mpam: propagate MSC access errors for msmon helpers Andre Przywara
2026-08-07 10:54 ` [PATCH v9 05/12] arm_mpam: propagate MSC access errors for __ris_msmon_read() Andre Przywara
2026-08-07 10:54 ` [PATCH v9 06/12] arm_mpam: propagate MSC access errors for state saving function Andre Przywara
2026-08-07 10:54 ` [PATCH v9 07/12] arm_mpam: propagate MSC access errors for mpam_reprogram_ris_partid() Andre Przywara
2026-08-26 17:41 ` Srivathsa L Rao
2026-08-07 10:54 ` [PATCH v9 08/12] arm_mpam: propagate MSC access errors for interrupt control Andre Przywara
2026-08-26 17:37 ` Srivathsa L Rao
2026-08-07 10:54 ` [PATCH v9 09/12] arm_mpam: prepare mon_sel locking for MPAM-Fb Andre Przywara
2026-08-07 10:54 ` [PATCH v9 10/12] arm_mpam: add MPAM-Fb MSC firmware access support Andre Przywara
2026-08-26 17:39 ` Srivathsa L Rao
2026-08-31 22:19 ` Lee Trager [this message]
2026-09-01 10:01 ` Andre Przywara
2026-08-07 10:54 ` [PATCH v9 11/12] arm_mpam: change MPAM-Fb error IRQ to use a threaded IRQ handler Andre Przywara
2026-08-26 17:38 ` Srivathsa L Rao
2026-08-27 0:09 ` Gavin Shan
2026-08-07 10:54 ` [PATCH v9 12/12] arm_mpam: detect and enable MPAM-Fb PCC support Andre Przywara
2026-08-26 17:43 ` Srivathsa L Rao
2026-08-27 0:10 ` Gavin Shan
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=948381d2-8ba7-458b-b729-d5398e0a8559@trager.us \
--to=lee@trager.us \
--cc=andre.przywara@arm.com \
--cc=ben.horgan@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fenghuay@nvidia.com \
--cc=ganapatrao.kulkarni@oss.qualcomm.com \
--cc=gshan@redhat.com \
--cc=guohanjun@huawei.com \
--cc=james.morse@arm.com \
--cc=jic23@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=niyas.sait@arm.com \
--cc=rafael@kernel.org \
--cc=reinette.chatre@intel.com \
--cc=ritwick.sharma@arm.com \
--cc=sramana@qti.qualcomm.com \
--cc=srivathsa.rao@oss.qualcomm.com \
--cc=sudeep.holla@kernel.org \
--cc=tsoni@quicinc.com \
--cc=will@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