From: Mike Jones <proclivis@gmail.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: No dbus objects for phosphor-regulators
Date: Tue, 25 Jan 2022 15:15:19 -0700 [thread overview]
Message-ID: <8C9640C9-6E1B-4495-BA55-258DA1548799@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2905 bytes --]
Hi,
I need some help getting phosphor-power/phosphor-regulators to add dbus objects.
I made a config file below, and verified that it is on the target and loads without error.
When the target boots, using a I2C spy tool, the 0xDD command is being read periodically, suggesting that this service is processing the read command, and a query show the service is up.
Using dbus-monitor –system, I do not see any transactions that place these sensor read values on dbus, nor does the normal probing the chassis and inventory show values.
My bbappend is shown below, it is simple, but I wonder what is missing.
What else do I need to so that there are dbus objects?
Note I have not done anything to intentionally use open_power. My goal is to only use phosphor-regulators to expose some telemetry that hwmon does not support.
Mike
*************** phosphor-power_%.bbappend ************
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
inherit obmc-phosphor-systemd
SRC_URI += file://config.json
do_install:append(){
install -D ${WORKDIR}/config.json ${D}${datadir}/phosphor-regulators/config.json
}
FILES:${PN} += "${datadir}/phosphor-regulators/config.json"
************* config file ****************
{
"comments": [ "Config file for a ADI one-chassis system" ],
"rules": [
{
"comments": [ "Sets output voltage for a PMBus regulator rail" ],
"id": "set_voltage_rule",
"actions": [
{
"pmbus_write_vout_command": {
"format": "linear"
}
}
]
},
{
"comments": [ "Reads sensors from a PMBus regulator rail" ],
"id": "read_sensors_rule",
"actions": [
{
"comments": [ "Read output voltage from READ_VOUT." ],
"pmbus_read_sensor": {
"type": "vout",
"command": "0xDD",
"format": "linear_16"
}
}
]
}
],
"chassis": [
{
"comments": [ "Chassis number 1 containing CPUs and memory" ],
"number": 1,
"inventory_path": "system/chassis",
"devices": [
{
"comments": [ "LTC3888 regulator producing the Vdd rail" ],
"id": "vdd_regulator",
"is_regulator": true,
"fru": "system/chassis/motherboard/regulator1",
"i2c_interface": {
"bus": 11,
"address": "0x4f"
},
"rails": [
{
"comments": [ "Vdd rail" ],
"id": "vdd",
"configuration": {
"volts": 1.10,
"rule_id": "set_voltage_rule"
},
"sensor_monitoring": {
"rule_id": "read_sensors_rule"
}
}
]
}
]
}
]
}
Mike
Sent from my iPad
[-- Attachment #2: Type: text/html, Size: 19173 bytes --]
next reply other threads:[~2022-01-25 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 22:15 Mike Jones [this message]
2022-01-26 22:43 ` No dbus objects for phosphor-regulators Shawn McCarney
-- strict thread matches above, loose matches on Subject: below --
2022-01-31 22:25 Mike
2022-02-01 17:37 ` Shawn McCarney
2022-02-09 22:30 ` Mike Jones
2022-02-11 15:32 ` Shawn McCarney
2022-02-11 15:42 ` Mike Jones
2022-02-11 16:06 ` Shawn McCarney
2022-02-11 20:20 ` Ed Tanous
2022-02-11 22:56 ` Mike Jones
2022-02-11 20:53 ` Patrick Williams
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=8C9640C9-6E1B-4495-BA55-258DA1548799@gmail.com \
--to=proclivis@gmail.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.