Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] soc: bcm2835: raspberrypi-firmware: Add voltage domain IDs
Date: Sat, 16 May 2026 22:14:05 +0530	[thread overview]
Message-ID: <20260516164407.25255-1-chakrabortyshubham66@gmail.com> (raw)

Add firmware voltage domain identifiers for the Raspberry Pi
mailbox property interface.

These IDs are used by firmware clients to query voltage rails
through the RPI_FIRMWARE_GET_VOLTAGE property.

Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
---
 include/soc/bcm2835/raspberrypi-firmware.h | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/include/soc/bcm2835/raspberrypi-firmware.h b/include/soc/bcm2835/raspberrypi-firmware.h
index e1f87fbfe554..fd2e051ce05b 100644
--- a/include/soc/bcm2835/raspberrypi-firmware.h
+++ b/include/soc/bcm2835/raspberrypi-firmware.h
@@ -156,6 +156,14 @@ enum rpi_firmware_clk_id {
 	RPI_FIRMWARE_NUM_CLK_ID,
 };
 
+enum rpi_firmware_volt_id {
+	RPI_FIRMWARE_VOLT_ID_RESERVED = 0,
+	RPI_FIRMWARE_VOLT_ID_CORE = 1,
+	RPI_FIRMWARE_VOLT_ID_SDRAM_C = 2,
+	RPI_FIRMWARE_VOLT_ID_SDRAM_I = 3,
+	RPI_FIRMWARE_VOLT_ID_SDRAM_P = 4,
+};
+
 /**
  * struct rpi_firmware_clk_rate_request - Firmware Request for a rate
  * @id:	ID of the clock being queried
-- 
2.54.0



             reply	other threads:[~2026-05-16 16:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16 16:44 Shubham Chakraborty [this message]
2026-05-16 16:44 ` [PATCH 2/2] hwmon: raspberrypi: Add voltage input support Shubham Chakraborty
2026-05-16 17:13   ` Guenter Roeck
2026-05-16 18:24     ` Guenter Roeck
2026-05-16 19:15 ` [PATCH v2 0/2] raspberrypi: firmware and hwmon voltage support Shubham Chakraborty
2026-05-16 19:15   ` [PATCH v2 1/2] soc: bcm2835: raspberrypi-firmware: Add voltage domain IDs Shubham Chakraborty
2026-05-16 23:09     ` Guenter Roeck
2026-05-16 19:15   ` [PATCH v2 2/2] hwmon: raspberrypi: Add voltage input support Shubham Chakraborty
2026-05-16 23:20     ` Guenter Roeck
2026-05-17  8:04 ` [PATCH v3 0/3] raspberrypi-hwmon voltage support and teardown fix Shubham Chakraborty
2026-05-17  8:04   ` [PATCH v3 1/3] soc: bcm2835: raspberrypi-firmware: Add voltage domain IDs Shubham Chakraborty
2026-05-18 22:17     ` Guenter Roeck
2026-05-19 15:29     ` Florian Fainelli
2026-05-20 13:35     ` Guenter Roeck
2026-05-17  8:04   ` [PATCH v3 2/3] hwmon: raspberrypi: Add voltage input support Shubham Chakraborty
2026-05-19 15:28     ` Florian Fainelli
2026-05-20 13:37     ` Guenter Roeck
2026-05-17  8:04   ` [PATCH v3 3/3] hwmon: raspberrypi: Fix delayed-work teardown race Shubham Chakraborty
2026-05-20 13:39     ` 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=20260516164407.25255-1-chakrabortyshubham66@gmail.com \
    --to=chakrabortyshubham66@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=rjui@broadcom.com \
    --cc=sbranden@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