class Status0Reg
Defined at line 963 of file ../../src/devices/power/drivers/fusb302/registers.h
STATUS0
This is a read-only register.
Rev 5 datasheet: Table 37 on page 27
Public Members
field_vbusok_978 field_activity_987 field_comp_993 field_crc_chk_999 field_alert_1008 field_wake_1017 field_bc_lvl_1027Public Methods
template <, >SelfType & set_vbusok (typename SelfType::ValueType val)If true, the VBUS voltage exceeds the minimum power supply voltage.
Changes in this value trigger the `vbusok_change` interrupt
request in the Interrupt register.
This bit is only valid (and generates interrupts) if the measure block is
powered on, which is gated by the `pwr2` field in
`PowerReg`.
The Rev 5 datasheet defines the "vVBUSthr" as 4.0 V in Table 10 "Type-C CC
Switch" on page 15. typec2.2 4.4.2 "VBUS" defers to usb3.2 for the valid
VBUS ranges. usb3.2 11.4.5 "VBUS Electrical Characteristics" states that
the minimum VBUS voltage at an upstream connector Port is 4.0 V.
Defined at line 978 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >typename SelfType::ValueType vbusok ()If true, the VBUS voltage exceeds the minimum power supply voltage.
Changes in this value trigger the `vbusok_change` interrupt
request in the Interrupt register.
This bit is only valid (and generates interrupts) if the measure block is
powered on, which is gated by the `pwr2` field in
`PowerReg`.
The Rev 5 datasheet defines the "vVBUSthr" as 4.0 V in Table 10 "Type-C CC
Switch" on page 15. typec2.2 4.4.2 "VBUS" defers to usb3.2 for the valid
VBUS ranges. usb3.2 11.4.5 "VBUS Electrical Characteristics" states that
the minimum VBUS voltage at an upstream connector Port is 4.0 V.
Defined at line 978 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >typename SelfType::ValueType activity ()If true, the BMC activity detector for the CC wire was triggered.
The BMC activity detector triggers after 3 voltage transitions, and remains
triggered while there are BMC transitions.
The BMC activity detector uses the CC wire connected to ?? (what is
"active CC line"?)
Defined at line 987 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >SelfType & set_activity (typename SelfType::ValueType val)If true, the BMC activity detector for the CC wire was triggered.
The BMC activity detector triggers after 3 voltage transitions, and remains
triggered while there are BMC transitions.
The BMC activity detector uses the CC wire connected to ?? (what is
"active CC line"?)
Defined at line 987 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >typename SelfType::ValueType comp ()If true, the variable voltage comparator's input exceeds the reference.
Changes in this value trigger the `variable_comparator_result_pending`
interrupt request in the `Interrupt` register.
Defined at line 993 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >SelfType & set_comp (typename SelfType::ValueType val)If true, the variable voltage comparator's input exceeds the reference.
Changes in this value trigger the `variable_comparator_result_pending`
interrupt request in the `Interrupt` register.
Defined at line 993 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >typename SelfType::ValueType crc_chk ()If true, the last message received by the BMC PHY had a correct CRC.
This bit becomes valid after CRC comparison completes, and becomes invalid
(is reset) when the BMC PHY receives the SOP* of a new message.
Defined at line 999 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >SelfType & set_crc_chk (typename SelfType::ValueType val)If true, the last message received by the BMC PHY had a correct CRC.
This bit becomes valid after CRC comparison completes, and becomes invalid
(is reset) when the BMC PHY receives the SOP* of a new message.
Defined at line 999 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >typename SelfType::ValueType alert ()If true, the BMC PHY has encountered an error.
The errors signaled are surfaced by the `tx_full` and
`rx_full` bits in `Status1Reg.
Despite the name used by the datasheet, this seems unrelated to the PD
message defined in usbpd3.1 6.4.6 "Alert Message".
Defined at line 1008 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >SelfType & set_alert (typename SelfType::ValueType val)If true, the BMC PHY has encountered an error.
The errors signaled are surfaced by the `tx_full` and
`rx_full` bits in `Status1Reg.
Despite the name used by the datasheet, this seems unrelated to the PD
message defined in usbpd3.1 6.4.6 "Alert Message".
Defined at line 1008 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >SelfType & set_wake (typename SelfType::ValueType val)If true, the Wake Detector was triggered.
The Wake Detector triggers if the voltage of any of the CC pins is between
0.25 V (WAKE_low) and 1.45V (WAKE_high).
The Wake Detector only works if its power gate is enabled, via the
`pwr0` bit in `PowerReg`.
Defined at line 1017 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >typename SelfType::ValueType wake ()If true, the Wake Detector was triggered.
The Wake Detector triggers if the voltage of any of the CC pins is between
0.25 V (WAKE_low) and 1.45V (WAKE_high).
The Wake Detector only works if its power gate is enabled, via the
`pwr0` bit in `PowerReg`.
Defined at line 1017 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >FixedComparatorResult bc_lvl ()The result of the fixed comparators in the measure block.
This result is only meaningful when the measure block's input is connected
to one of the CC pins. The driver is responsible for handling the CC pin
voltage variation produced by BMC communication.
Also, the result is only meaningful when power gates 1-3 are enabled, via
the `pwr0`, `pwr1`, and `pwr2` bits in `PowerReg`.
Defined at line 1027 of file ../../src/devices/power/drivers/fusb302/registers.h
template <, >SelfType & set_bc_lvl (FixedComparatorResult val)The result of the fixed comparators in the measure block.
This result is only meaningful when the measure block's input is connected
to one of the CC pins. The driver is responsible for handling the CC pin
voltage variation produced by BMC communication.
Also, the result is only meaningful when power gates 1-3 are enabled, via
the `pwr0`, `pwr1`, and `pwr2` bits in `PowerReg`.
Defined at line 1027 of file ../../src/devices/power/drivers/fusb302/registers.h
hwreg::I2cRegisterAddr<Status0Reg> Get ()Defined at line 1029 of file ../../src/devices/power/drivers/fusb302/registers.h