From: Bui Nguyen Nhu Quynh <kaylovefoss@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: mpe@ellerman.id.au
Subject: [QUESTION] Does PowerVM populate the rtas-sensors device-tree property?
Date: Sun, 1 Nov 2026 21:47:00 +0700 [thread overview]
Message-ID: <20261101144716.119289-1-kaylovefoss@gmail.com> (raw)
Hi,
I am trying to determine whether PowerVM firmware populates the rtas-sensors device-tree property on the /rtas node. The kernel's ppc_rtas_sensors_show() in arch/powerpc/kernel/rtas-proc.c reads it, but I have found no producer in QEMU, SLOF, or the kernel documentation.
On any PowerVM system, the answer is one command:
ls -l /proc/device-tree/rtas/rtas-sensors
od -An -tx1 /proc/device-tree/rtas/rtas-sensors
If the file exists, could you report the byte output? If it does not exist, that also answers the question.
I have a QEMU patch and a local reproducer if useful, but the firmware-side answer is the only thing I cannot determine locally.
Thanks.
reply other threads:[~2026-11-01 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261101144716.119289-1-kaylovefoss@gmail.com \
--to=kaylovefoss@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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