hwmon: (pmbus/ibm-cffps) Add clear_faults debugfs entry
PATCH v2 1/1 hwmon: (pmbus/ibm-cffps) Add clear_faults debugfs entry
Add a clear_faults write-only debugfs entry for the ibm-cffps device driver.
Certain IBM power supplies require clearing some latched faults in order to indicate that the fault has indeed been observed/noticed.
---
V1 -> V2: Explain why this change is needed
drivers/hwmon/pmbus/ibm-cffps.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
drivers/hwmon/pmbus/ibm-cffps.c +11 -0
@@ -67,6 +67,7 @@ enum {CFFPS_DEBUGFS_CCIN ,CFFPS_DEBUGFS_FW ,CFFPS_DEBUGFS_ON_OFF_CONFIG , +CFFPS_DEBUGFS_CLEAR_FAULTS , CFFPS_DEBUGFS_NUM_ENTRIES };
@@ -274,6 +275,13 @@ static ssize_t ibm_cffps_debugfs_write(struct file *file,if (rc)return rc; + rc =1 ; +break ; +case CFFPS_DEBUGFS_CLEAR_FAULTS : + rc =i2c_smbus_write_byte (psu->client,PMBUS_CLEAR_FAULTS ); +if (rc <0 ) +return rc; + rc =1 ;break ;default :
@@ -607,6 +615,9 @@ static int ibm_cffps_probe(struct i2c_client *client)debugfs_create_file ("on_off_config" ,0644 , ibm_cffps_dir, &psu->debugfs_entries[CFFPS_DEBUGFS_ON_OFF_CONFIG ], &ibm_cffps_fops); +debugfs_create_file ("clear_faults" ,0200 , ibm_cffps_dir, + &psu->debugfs_entries[CFFPS_DEBUGFS_CLEAR_FAULTS ], + &ibm_cffps_fops);return 0 ; }
Signature · 1 line
2.25.1
Guenter Roeck
maintainerQuoted 6 lines · Brandon Wyman
Add a
clear_faultswrite-only debugfs entry for the ibm-cffps device driver.Certain IBM power supplies require clearing some latched faults in order to indicate that the fault has indeed been observed/noticed.
That is insufficient, sorry. Please provide the affected power supplies as well as the affected faults, and confirm that the problem still exists in v5.17-rc6 or later kernels - or, more specifically, in any kernel which includes commit 35f165f08950 ("hwmon: (pmbus) Clear pmbus fault/warning bits after read").
Thanks,
Guenter
Quoted 43 lines
Signed-off-by Brandon Wyman <[email protected]>---
V1 -> V2: Explain why this change is neededdrivers/hwmon/pmbus/ibm-cffps.c | 11 +++++++++++ 1 file changed, 11 insertions(+)drivers/hwmon/pmbus/ibm-cffps.c +11
-0@@ -67,6 +67,7 @@ enum {CFFPS_DEBUGFS_CCIN ,CFFPS_DEBUGFS_FW ,CFFPS_DEBUGFS_ON_OFF_CONFIG , +CFFPS_DEBUGFS_CLEAR_FAULTS , CFFPS_DEBUGFS_NUM_ENTRIES };@@ -274,6 +275,13 @@ static ssize_t ibm_cffps_debugfs_write(struct file *file,if (rc)return rc; + rc =1 ; +break ; +case CFFPS_DEBUGFS_CLEAR_FAULTS : + rc =i2c_smbus_write_byte (psu->client,PMBUS_CLEAR_FAULTS ); +if (rc <0 ) +return rc; + rc =1 ;break ;default :@@ -607,6 +615,9 @@ static int ibm_cffps_probe(struct i2c_client *client)debugfs_create_file ("on_off_config" ,0644 , ibm_cffps_dir, &psu->debugfs_entries[CFFPS_DEBUGFS_ON_OFF_CONFIG ], &ibm_cffps_fops); +debugfs_create_file ("clear_faults" ,0200 , ibm_cffps_dir, + &psu->debugfs_entries[CFFPS_DEBUGFS_CLEAR_FAULTS ], + &ibm_cffps_fops);return 0 ; }
Quoted 9 lines · Guenter Roeck
Quoted 6 lines · Brandon Wyman
Add a
clear_faultswrite-only debugfs entry for the ibm-cffps device driver.Certain IBM power supplies require clearing some latched faults in order to indicate that the fault has indeed been observed/noticed.
Quoted 8 lines
That is insufficient, sorry. Please provide the affected power supplies as well as the affected faults, and confirm that the problem still exists in v5.17-rc6 or later kernels - or, more specifically, in any kernel which includes commit
35f165f08950("hwmon: (pmbus) Clear pmbus fault/warning bits after read").Thanks,
Guenter
Sorry for the delay in responding. I did some testing with commit 35f165f08950. I could not get that code to send the CLEAR_FAULTS command to the power supplies.
I can update the commit message to be more specific about which power supplies need this CLEAR_FAULTS sent, and which faults. It is observed with the 1600W power supplies (2B1E model). The faults that latch are the VIN_UV and INPUT faults in the STATUS_WORD. The corresponding STATUS_INPUT fault bits are VIN_UV_FAULT and Unit is Off.
Quoted 45 lines
Quoted 44 lines
Signed-off-by Brandon Wyman <[email protected]>---
V1 -> V2: Explain why this change is neededdrivers/hwmon/pmbus/ibm-cffps.c | 11 +++++++++++ 1 file changed, 11 insertions(+)drivers/hwmon/pmbus/ibm-cffps.c +11
-0@@ -67,6 +67,7 @@ enum {CFFPS_DEBUGFS_CCIN ,CFFPS_DEBUGFS_FW ,CFFPS_DEBUGFS_ON_OFF_CONFIG , +CFFPS_DEBUGFS_CLEAR_FAULTS , CFFPS_DEBUGFS_NUM_ENTRIES };@@ -274,6 +275,13 @@ static ssize_t ibm_cffps_debugfs_write(struct file *file,if (rc)return rc; + rc =1 ; +break ; +case CFFPS_DEBUGFS_CLEAR_FAULTS : + rc =i2c_smbus_write_byte (psu->client,PMBUS_CLEAR_FAULTS ); +if (rc <0 ) +return rc; + rc =1 ;break ;default :@@ -607,6 +615,9 @@ static int ibm_cffps_probe(struct i2c_client *client)debugfs_create_file ("on_off_config" ,0644 , ibm_cffps_dir, &psu->debugfs_entries[CFFPS_DEBUGFS_ON_OFF_CONFIG ], &ibm_cffps_fops); +debugfs_create_file ("clear_faults" ,0200 , ibm_cffps_dir, + &psu->debugfs_entries[CFFPS_DEBUGFS_CLEAR_FAULTS ], + &ibm_cffps_fops);return 0 ; }
Guenter Roeck
maintainerQuoted 23 lines · Brandon Wyman
Quoted 9 lines · Guenter Roeck
Quoted 6 lines · Brandon Wyman
Add a
clear_faultswrite-only debugfs entry for the ibm-cffps device driver.Certain IBM power supplies require clearing some latched faults in order to indicate that the fault has indeed been observed/noticed.
Quoted 8 lines
That is insufficient, sorry. Please provide the affected power supplies as well as the affected faults, and confirm that the problem still exists in v5.17-rc6 or later kernels - or, more specifically, in any kernel which includes commit
35f165f08950("hwmon: (pmbus) Clear pmbus fault/warning bits after read").Thanks,
GuenterSorry for the delay in responding. I did some testing with commit
35f165f08950. I could not get that code to send theCLEAR_FAULTScommand to the power supplies.
Quoted 6 lines
I can update the commit message to be more specific about which power supplies need this
CLEAR_FAULTSsent, and which faults. It is observed with the 1600W power supplies (2B1E model). The faults that latch are theVIN_UVand INPUT faults in theSTATUS_WORD. The correspondingSTATUS_INPUTfault bits areVIN_UV_FAULTand Unit is Off.
The point is that the respective fault bits should be reset when the corresponding alarm attributes are read. This isn't about executing a CLEAR_FAULTS command, but about selectively resetting fault bits while ensuring that faults are reported at least once. Executing CLEAR_FAULTS is a big hammer.
With the patch I pointed to in place, input (and other) faults should be reset after the corresponding alarm attributes are read, assuming that the condition no longer exists. If that does not happen, we should fix the problem instead of deploying the big hammer.
Thanks,
Guenter
Quoted 45 lines
Quoted 45 lines
Quoted 44 lines
Signed-off-by Brandon Wyman <[email protected]>---
V1 -> V2: Explain why this change is neededdrivers/hwmon/pmbus/ibm-cffps.c | 11 +++++++++++ 1 file changed, 11 insertions(+)drivers/hwmon/pmbus/ibm-cffps.c +11
-0@@ -67,6 +67,7 @@ enum {CFFPS_DEBUGFS_CCIN ,CFFPS_DEBUGFS_FW ,CFFPS_DEBUGFS_ON_OFF_CONFIG , +CFFPS_DEBUGFS_CLEAR_FAULTS , CFFPS_DEBUGFS_NUM_ENTRIES };@@ -274,6 +275,13 @@ static ssize_t ibm_cffps_debugfs_write(struct file *file,if (rc)return rc; + rc =1 ; +break ; +case CFFPS_DEBUGFS_CLEAR_FAULTS : + rc =i2c_smbus_write_byte (psu->client,PMBUS_CLEAR_FAULTS ); +if (rc <0 ) +return rc; + rc =1 ;break ;default :@@ -607,6 +615,9 @@ static int ibm_cffps_probe(struct i2c_client *client)debugfs_create_file ("on_off_config" ,0644 , ibm_cffps_dir, &psu->debugfs_entries[CFFPS_DEBUGFS_ON_OFF_CONFIG ], &ibm_cffps_fops); +debugfs_create_file ("clear_faults" ,0200 , ibm_cffps_dir, + &psu->debugfs_entries[CFFPS_DEBUGFS_CLEAR_FAULTS ], + &ibm_cffps_fops);return 0 ; }
Quoted 38 lines · Guenter Roeck
Quoted 23 lines · Brandon Wyman
Quoted 9 lines · Guenter Roeck
Quoted 6 lines · Brandon Wyman
Add a
clear_faultswrite-only debugfs entry for the ibm-cffps device driver.Certain IBM power supplies require clearing some latched faults in order to indicate that the fault has indeed been observed/noticed.
Quoted 8 lines
That is insufficient, sorry. Please provide the affected power supplies as well as the affected faults, and confirm that the problem still exists in v5.17-rc6 or later kernels - or, more specifically, in any kernel which includes commit
35f165f08950("hwmon: (pmbus) Clear pmbus fault/warning bits after read").Thanks,
GuenterSorry for the delay in responding. I did some testing with commit
35f165f08950. I could not get that code to send theCLEAR_FAULTScommand to the power supplies.Quoted 6 lines
I can update the commit message to be more specific about which power supplies need this
CLEAR_FAULTSsent, and which faults. It is observed with the 1600W power supplies (2B1E model). The faults that latch are theVIN_UVand INPUT faults in theSTATUS_WORD. The correspondingSTATUS_INPUTfault bits areVIN_UV_FAULTand Unit is Off.The point is that the respective fault bits should be reset when the corresponding alarm attributes are read. This isn't about executing a
CLEAR_FAULTScommand, but about selectively resetting fault bits while ensuring that faults are reported at least once. ExecutingCLEAR_FAULTSis a big hammer.
Quoted 7 lines
With the patch I pointed to in place, input (and other) faults should be reset after the corresponding alarm attributes are read, assuming that the condition no longer exists. If that does not happen, we should fix the problem instead of deploying the big hammer.
Thanks,
Guenter
Okay, I see what you are pointing out there. I had been mostly looking at the "files" in the debugfs paths. Those do not end up running through that pmbus_get_boolean() function, so the individual fault clearing was not being attempted. The fault I was interested in appears to be associated with in1_lcrti_alarm. Reading that will give me a 1 if there is a VIN_UV fault, and then it sends 0x10 to STATUS_INPUT. That clears out VIN_UV, but the STATUS_INPUT command was returning 0x18. Nothing appears to handle clearing BIT(3), that 0x08 mask.
Should there be some kind of define for BIT(3) over in pmbus.h? Something like PB_VOLTAGE_OFF? Somehow we need something using that in sbit of the attributes. I had a quick hack that just OR'ed BIT(3) with BIT(4) for that PB_VOLTAGE_UV_FAULT. That resulted in a clear of both bits in STATUS_INPUT, and the faults clearing in STATUS_WORD.
It is not clear if there should be a separate alarm for that "Unit Off For Insufficient Input Voltage", or if the one for in1_lcrit_alarm could just be the two bits OR'ed into one mask. I can send a patch with a proposal on how to fix this one bit not getting cleared.
Quoted 47 lines
Quoted 46 lines
Quoted 46 lines
Quoted 45 lines
Signed-off-by Brandon Wyman <[email protected]>---
V1 -> V2: Explain why this change is neededdrivers/hwmon/pmbus/ibm-cffps.c | 11 +++++++++++ 1 file changed, 11 insertions(+)drivers/hwmon/pmbus/ibm-cffps.c +11
-0@@ -67,6 +67,7 @@ enum {CFFPS_DEBUGFS_CCIN ,CFFPS_DEBUGFS_FW ,CFFPS_DEBUGFS_ON_OFF_CONFIG , +CFFPS_DEBUGFS_CLEAR_FAULTS , CFFPS_DEBUGFS_NUM_ENTRIES };@@ -274,6 +275,13 @@ static ssize_t ibm_cffps_debugfs_write(struct file *file,if (rc)return rc; + rc =1 ; +break ; +case CFFPS_DEBUGFS_CLEAR_FAULTS : + rc =i2c_smbus_write_byte (psu->client,PMBUS_CLEAR_FAULTS ); +if (rc <0 ) +return rc; + rc =1 ;break ;default :@@ -607,6 +615,9 @@ static int ibm_cffps_probe(struct i2c_client *client)debugfs_create_file ("on_off_config" ,0644 , ibm_cffps_dir, &psu->debugfs_entries[CFFPS_DEBUGFS_ON_OFF_CONFIG ], &ibm_cffps_fops); +debugfs_create_file ("clear_faults" ,0200 , ibm_cffps_dir, + &psu->debugfs_entries[CFFPS_DEBUGFS_CLEAR_FAULTS ], + &ibm_cffps_fops);return 0 ; }
Guenter Roeck
maintainerQuoted 63 lines · Brandon Wyman
Quoted 38 lines · Guenter Roeck
Quoted 23 lines · Brandon Wyman
Quoted 9 lines · Guenter Roeck
Quoted 6 lines · Brandon Wyman
Add a
clear_faultswrite-only debugfs entry for the ibm-cffps device driver.Certain IBM power supplies require clearing some latched faults in order to indicate that the fault has indeed been observed/noticed.
Quoted 8 lines
That is insufficient, sorry. Please provide the affected power supplies as well as the affected faults, and confirm that the problem still exists in v5.17-rc6 or later kernels - or, more specifically, in any kernel which includes commit
35f165f08950("hwmon: (pmbus) Clear pmbus fault/warning bits after read").Thanks,
GuenterSorry for the delay in responding. I did some testing with commit
35f165f08950. I could not get that code to send theCLEAR_FAULTScommand to the power supplies.Quoted 6 lines
I can update the commit message to be more specific about which power supplies need this
CLEAR_FAULTSsent, and which faults. It is observed with the 1600W power supplies (2B1E model). The faults that latch are theVIN_UVand INPUT faults in theSTATUS_WORD. The correspondingSTATUS_INPUTfault bits areVIN_UV_FAULTand Unit is Off.The point is that the respective fault bits should be reset when the corresponding alarm attributes are read. This isn't about executing a
CLEAR_FAULTScommand, but about selectively resetting fault bits while ensuring that faults are reported at least once. ExecutingCLEAR_FAULTSis a big hammer.Quoted 7 lines
With the patch I pointed to in place, input (and other) faults should be reset after the corresponding alarm attributes are read, assuming that the condition no longer exists. If that does not happen, we should fix the problem instead of deploying the big hammer.
Thanks,
GuenterOkay, I see what you are pointing out there. I had been mostly looking at the "files" in the debugfs paths. Those do not end up running through that
pmbus_get_boolean()function, so the individual fault clearing was not being attempted. The fault I was interested in appears to be associated within1_lcrti_alarm. Reading that will give me a 1 if there is aVIN_UVfault, and then it sends0x10toSTATUS_INPUT. That clears outVIN_UV, but theSTATUS_INPUTcommand was returning0x18. Nothing appears to handle clearing BIT(3), that0x08mask.Should there be some kind of define for BIT(3) over in
pmbus.h? Something likePB_VOLTAGE_OFF? Somehow we need something using that in sbit of the attributes. I had a quick hack that just OR'ed BIT(3) with BIT(4) for thatPB_VOLTAGE_UV_FAULT. That resulted in a clear of both bits inSTATUS_INPUT, and the faults clearing inSTATUS_WORD.
Quoted 5 lines
It is not clear if there should be a separate alarm for that "Unit Off For Insufficient Input Voltage", or if the one for
in1_lcrit_alarmcould just be the two bits OR'ed into one mask. I can send a patch with a proposal on how to fix this one bit not getting cleared.
We don't have a separate standard attribute. I think the best approach would be to add a mask for bit 3 and or that mask for lcrit in vin_limit_attrs with PB_VOLTAGE_UV_FAULT. I'd suggest to name the define something like PB_VOLTAGE_VIN_OFF or PB_VOLTAGE_VIN_FAULT to clarify that the bit applies to the input.
Thanks,
Guenter
Quoted 71 lines · Guenter Roeck
Quoted 63 lines · Brandon Wyman
Quoted 38 lines · Guenter Roeck
Quoted 23 lines · Brandon Wyman
Quoted 9 lines · Guenter Roeck
Quoted 6 lines · Brandon Wyman
Add a
clear_faultswrite-only debugfs entry for the ibm-cffps device driver.Certain IBM power supplies require clearing some latched faults in order to indicate that the fault has indeed been observed/noticed.
Quoted 8 lines
That is insufficient, sorry. Please provide the affected power supplies as well as the affected faults, and confirm that the problem still exists in v5.17-rc6 or later kernels - or, more specifically, in any kernel which includes commit
35f165f08950("hwmon: (pmbus) Clear pmbus fault/warning bits after read").Thanks,
GuenterSorry for the delay in responding. I did some testing with commit
35f165f08950. I could not get that code to send theCLEAR_FAULTScommand to the power supplies.Quoted 6 lines
I can update the commit message to be more specific about which power supplies need this
CLEAR_FAULTSsent, and which faults. It is observed with the 1600W power supplies (2B1E model). The faults that latch are theVIN_UVand INPUT faults in theSTATUS_WORD. The correspondingSTATUS_INPUTfault bits areVIN_UV_FAULTand Unit is Off.The point is that the respective fault bits should be reset when the corresponding alarm attributes are read. This isn't about executing a
CLEAR_FAULTScommand, but about selectively resetting fault bits while ensuring that faults are reported at least once. ExecutingCLEAR_FAULTSis a big hammer.Quoted 7 lines
With the patch I pointed to in place, input (and other) faults should be reset after the corresponding alarm attributes are read, assuming that the condition no longer exists. If that does not happen, we should fix the problem instead of deploying the big hammer.
Thanks,
GuenterOkay, I see what you are pointing out there. I had been mostly looking at the "files" in the debugfs paths. Those do not end up running through that
pmbus_get_boolean()function, so the individual fault clearing was not being attempted. The fault I was interested in appears to be associated within1_lcrti_alarm. Reading that will give me a 1 if there is aVIN_UVfault, and then it sends0x10toSTATUS_INPUT. That clears outVIN_UV, but theSTATUS_INPUTcommand was returning0x18. Nothing appears to handle clearing BIT(3), that0x08mask.Should there be some kind of define for BIT(3) over in
pmbus.h? Something likePB_VOLTAGE_OFF? Somehow we need something using that in sbit of the attributes. I had a quick hack that just OR'ed BIT(3) with BIT(4) for thatPB_VOLTAGE_UV_FAULT. That resulted in a clear of both bits inSTATUS_INPUT, and the faults clearing inSTATUS_WORD.Quoted 5 lines
It is not clear if there should be a separate alarm for that "Unit Off For Insufficient Input Voltage", or if the one for
in1_lcrit_alarmcould just be the two bits OR'ed into one mask. I can send a patch with a proposal on how to fix this one bit not getting cleared.
Quoted 5 lines
We don't have a separate standard attribute. I think the best approach would be to add a mask for bit 3 and or that mask for lcrit in
vin_limit_attrswithPB_VOLTAGE_UV_FAULT. I'd suggest to name the define something likePB_VOLTAGE_VIN_OFForPB_VOLTAGE_VIN_FAULTto clarify that the bit applies to the input.
Done. See: https://lore.kernel.org/linux-hwmon/[email protected]/T/#u
Quoted 3 lines
Thanks,
Guenter