| /openbmc/witherspoon-pfault-analysis/ |
| H A D | pmbus.hpp | 112 class PMBus class
115 PMBus() = delete;
116 ~PMBus() = default;
117 PMBus(const PMBus&) = default;
118 PMBus& operator=(const PMBus&) = default;
119 PMBus(PMBus&&) = default;
120 PMBus& operator=(PMBus&&) = default;
127 PMBus(const std::string& path) : basePath(path) in PMBus() function in witherspoon::pmbus::PMBus
142 PMBus(const std::string& path, const std::string& driverName, in PMBus() function in witherspoon::pmbus::PMBus
|
| H A D | pmbus.cpp | 47 std::string PMBus::insertPageNum(const std::string& templateName, size_t page) in insertPageNum()
61 fs::path PMBus::getPath(Type type) in getPath()
88 std::string PMBus::getDeviceName() in getDeviceName()
110 bool PMBus::readBitInPage(const std::string& name, size_t page, Type type) in readBitInPage()
116 bool PMBus::readBit(const std::string& name, Type type) in readBit()
164 bool PMBus::exists(const std::string& name, Type type) in exists()
171 uint64_t PMBus::read(const std::string& name, Type type) in read()
202 std::string PMBus::readString(const std::string& name, Type type) in readString()
233 std::vector<uint8_t> PMBus::readBinary(const std::string& name, Type type, in readBinary()
276 void PMBus::write(const std::string& name, int value, Type type) in write()
[all …]
|
| /openbmc/phosphor-power/ |
| H A D | pmbus.hpp | 208 class PMBus : public PMBusBase class
211 PMBus() = delete;
212 virtual ~PMBus() = default;
213 PMBus(const PMBus&) = default;
214 PMBus& operator=(const PMBus&) = default;
215 PMBus(PMBus&&) = default;
216 PMBus& operator=(PMBus&&) = default;
223 PMBus(const std::string& path) : basePath(path) in PMBus() function in phosphor::pmbus::PMBus
238 PMBus(const std::string& path, const std::string& driverName, in PMBus() function in phosphor::pmbus::PMBus
|
| H A D | pmbus.cpp | 47 std::string PMBus::insertPageNum(const std::string& templateName, size_t page) in insertPageNum()
61 fs::path PMBus::getPath(Type type) in getPath()
88 std::string PMBus::getDeviceName() in getDeviceName()
112 bool PMBus::readBitInPage(const std::string& name, size_t page, Type type) in readBitInPage()
118 bool PMBus::readBit(const std::string& name, Type type) in readBit()
170 bool PMBus::exists(const std::string& name, Type type) in exists()
177 uint64_t PMBus::read(const std::string& name, Type type, bool errTrace) in read()
218 std::string PMBus::readString(const std::string& name, Type type) in readString()
251 std::vector<uint8_t> PMBus::readBinary(const std::string& name, Type type, in readBinary()
296 void PMBus::write(const std::string& name, int value, Type type) in write()
[all …]
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | pmbus-core.rst | 2 PMBus core driver and internal API
8 [from pmbus.org] The Power Management Bus (PMBus) is an open standard
18 promoted by the PMBus Implementers Forum (PMBus-IF), comprising 30+ adopters
21 Unfortunately, while PMBus commands are standardized, there are no mandatory
27 Despite all those difficulties, a generic PMBus device driver is still useful
29 device specific extensions in addition to the core PMBus driver, since it is
30 simply unknown what new device specific functionality PMBus device developers
34 to modify the core PMBus driver repeatedly for new devices, the PMBus driver was
37 provides support for generic PMBus devices. Device specific code is responsible
43 PMBus device capabilities auto-detection
[all …]
|
| H A D | max34440.rst | 16 PMBus 5-Channel Power-Supply Manager and Intelligent Fan Controller
26 PMBus Power-Supply Data Logger
36 PMBus 16-Channel V/I Monitor and 12-Channel Sequencer/Marginer
46 PMBus 12-Channel Voltage Monitor & Sequencer
56 PMBus 16-Channel Voltage Monitor & Sequencer
70 This driver supports hardware monitoring for Maxim MAX34440 PMBus 6-Channel
71 Power-Supply Manager, MAX34441 PMBus 5-Channel Power-Supply Manager
72 and Intelligent Fan Controller, and MAX34446 PMBus Power-Supply Data Logger.
73 It also supports the MAX34451, MAX34460, and MAX34461 PMBus Voltage Monitor &
78 The driver is a client driver to the core PMBus driver. Please see
[all …]
|
| H A D | bel-pfe.rst | 29 which support PMBus Protocol:
34 PMBus Communication Manual is not publicly available.
39 PMBus Communication Manual is not publicly available.
41 The driver is a client driver to the core PMBus driver. Please see
42 Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
62 The driver supports standard PMBus driver platform data.
|
| H A D | max20751.rst | 22 This driver supports MAX20751 Multiphase Master with PMBus Interface
25 The driver is a client driver to the core PMBus driver.
26 Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
40 The driver supports standard PMBus driver platform data.
|
| H A D | tps40422.rst | 21 Controller with PMBus
23 The driver is a client driver to the core PMBus driver.
24 Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
38 The driver supports standard PMBus driver platform data.
|
| H A D | ucd9000.rst | 35 The UCD90124 is a 12-rail PMBus/I2C addressable power-supply sequencer and
43 The UCD90160 is a 16-rail PMBus/I2C addressable power-supply sequencer and
50 The UCD90320 is a 32-rail PMBus/I2C addressable power-supply sequencer and
56 The UCD9090 is a 10-rail PMBus/I2C addressable power-supply sequencer and
63 The UCD90910 is a ten-rail I2C / PMBus addressable power-supply sequencer and
67 This driver is a client driver to the core PMBus driver. Please see
68 Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
82 The driver supports standard PMBus driver platform data. Please see
|
| H A D | adm1266.rst | 20 integrated 12 bit SAR ADC, accessed using a PMBus interface.
22 The driver is a client driver to the core PMBus driver. Please see
23 Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
|
| H A D | max16064.rst | 21 Controller with Active-Voltage Output Control and PMBus Interface.
23 The driver is a client driver to the core PMBus driver.
24 Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
38 The driver supports standard PMBus driver platform data.
|
| H A D | max8688.rst | 21 Controller/Monitor with PMBus Interface.
23 The driver is a client driver to the core PMBus driver. Please see
24 Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
38 The driver supports standard PMBus driver platform data.
|
| H A D | q54sj108a2.rst | 25 with PMBus support.
27 The driver is a client driver to the core PMBus driver.
28 Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
|
| H A D | ltc4286.rst | 36 converter (ADC), accessed using a PMBus interface.
38 The driver is a client driver to the core PMBus driver. Please see
39 Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
57 The driver supports standard PMBus driver platform data. Please see
|
| H A D | dps920ab.rst | 22 power supply with PMBus support.
24 The driver is a client driver to the core PMBus driver.
25 Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
|
| H A D | adm1275.rst | 68 PMBus interface.
70 The driver is a client driver to the core PMBus driver. Please see
71 Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
81 The ADM1075, unlike many other PMBus devices, does not support internal voltage
92 The driver supports standard PMBus driver platform data. Please see
|
| H A D | max20730.rst | 47 Integrated, Step-Down Switching Regulators with PMBus support.
49 The driver is a client driver to the core PMBus driver.
50 Please see Documentation/hwmon/pmbus.rst for details on PMBus client drivers.
|
| H A D | pim4328.rst | 43 The driver is a client driver to the core PMBus driver. Please see
45 on PMBus client drivers.
59 The driver supports standard PMBus driver platform data.
|
| H A D | max15301.rst | 25 The driver is a client driver to the core PMBus driver. Please see
27 on PMBus client drivers.
41 The driver supports standard PMBus driver platform data.
|
| H A D | stpddc60.rst | 25 The driver is a client driver to the core PMBus driver. Please see
27 on PMBus client drivers.
49 The driver supports standard PMBus driver platform data.
|
| H A D | lineage-pem.rst | 25 Lineage CPL power entry modules are nominally PMBus compliant. However, most
26 standard PMBus commands are not supported. Specifically, all hardware monitoring
28 PMBus driver can not be used.
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | pmbus_read_sensor.md | 5 Reads one sensor for a PMBus regulator rail. Communicates with the device
30 - Some of these sensor types are not part of the PMBus specification and must be
35 Currently the following PMBus data formats are supported:
46 If the device supports the PMBus VOUT_MODE command, the exponent value can be
94 peak/valley values are read over PMBus, the regulator will often clear its
105 | command | yes | string | PMBus command code expressed in hexadecimal. Must be prefixed with…
|
| H A D | pmbus_write_vout_command.md | 5 Writes the value of VOUT_COMMAND to set the output voltage of a PMBus regulator
14 The PMBus specification defines four modes/formats for the value of
29 If the device supports the PMBus VOUT_MODE command, the exponent value can be
47 were written to VOUT_COMMAND. The PMBus specification permits a device to have
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| H A D | services.hpp | 37 using PMBus = phosphor::pmbus::PMBus; typedef
204 return std::make_unique<PMBus>(path, driverName, instance); in createPMBus()
|