The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Aniruddha Rao <anrao@nvidia.com>
To: <thierry.reding@kernel.org>, <jonathanh@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Aniruddha Rao" <anrao@nvidia.com>
Subject: [PATCH 0/6] firmware: tegra: bpmp: Add Tegra410 ACPI MBWT support
Date: Mon, 15 Jun 2026 08:37:25 +0000	[thread overview]
Message-ID: <20260615083731.888055-1-anrao@nvidia.com> (raw)

Tegra410, an ACPI-based platform, provides Memory Bandwidth Throttler
(MBWT) controls for PCIe and GPU connected over chip-to-chip link
(Nv-Clink) traffic on the path to DRAM. These controls are accessible
through BPMP firmware.

The current Tegra BPMP driver depends on Device Tree based transport
setup and does not support ACPI-based platforms. This series keeps the
existing DT path unchanged, adds ACPI support to the BPMP driver,
defines the MBWT BPMP ABI, adds Tegra410 MBWT helper functions, and
exposes a narrow sysfs interface for ACPI-based Tegra410 systems when
firmware reports support for the required MBWT requests.

Aniruddha Rao (6):
  soc/tegra: Add Tegra410 SoC Kconfig symbol
  firmware: tegra: bpmp: Move channel, resource init to helper
  firmware: tegra: bpmp: Add ACPI support
  firmware: tegra: bpmp: Add the Memory Bandwidth Throttler ABI
    definitions
  firmware: tegra: bpmp: Add Tegra410 MBWT BPMP helpers
  firmware: tegra: bpmp: Add Tegra410 MBWT sysfs interface

 .../ABI/testing/sys-platform-tegra-bpmp       |  51 ++++
 drivers/firmware/tegra/Makefile               |   2 +
 drivers/firmware/tegra/bpmp-private.h         |  42 +++
 drivers/firmware/tegra/bpmp-tegra-sysfs.c     | 210 ++++++++++++++
 drivers/firmware/tegra/bpmp-tegra410.c        | 108 +++++++
 drivers/firmware/tegra/bpmp.c                 | 272 ++++++++++++++----
 drivers/soc/tegra/Kconfig                     |  10 +
 include/soc/tegra/bpmp-abi.h                  | 161 ++++++++++-
 8 files changed, 807 insertions(+), 49 deletions(-)
 create mode 100644 Documentation/ABI/testing/sys-platform-tegra-bpmp
 create mode 100644 drivers/firmware/tegra/bpmp-tegra-sysfs.c
 create mode 100644 drivers/firmware/tegra/bpmp-tegra410.c

-- 
2.43.0

             reply	other threads:[~2026-06-15  8:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15  8:37 Aniruddha Rao [this message]
2026-06-15  8:37 ` [PATCH 1/6] soc/tegra: Add Tegra410 SoC Kconfig symbol Aniruddha Rao
2026-07-10  9:34   ` Thierry Reding
2026-06-15  8:37 ` [PATCH 2/6] firmware: tegra: bpmp: Move channel, resource init to helper Aniruddha Rao
2026-07-10  9:39   ` Thierry Reding
2026-06-15  8:37 ` [PATCH 3/6] firmware: tegra: bpmp: Add ACPI support Aniruddha Rao
2026-07-10 10:08   ` Thierry Reding
2026-06-15  8:37 ` [PATCH 4/6] firmware: tegra: bpmp: Add the Memory Bandwidth Throttler ABI definitions Aniruddha Rao
2026-07-10 10:13   ` Thierry Reding
2026-06-15  8:37 ` [PATCH 5/6] firmware: tegra: bpmp: Add Tegra410 MBWT BPMP helpers Aniruddha Rao
2026-07-10 10:19   ` Thierry Reding
2026-06-15  8:37 ` [PATCH 6/6] firmware: tegra: bpmp: Add Tegra410 MBWT sysfs interface Aniruddha Rao
2026-07-10 10:46   ` Thierry Reding

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=20260615083731.888055-1-anrao@nvidia.com \
    --to=anrao@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@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