mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-11-24 05:50:53 +07:00
9e347728c4
If a chip is write protected, we can not change any limits, and we can not clear status flags. This may be the reason why clearing status flags is reported to not work for some chips. Detect the condition in the pmbus core. If the chip is write protected, set limit attributes as read-only, and set the flag indicating that the status flag should be ignored. Signed-off-by: Guenter Roeck <linux@roeck-us.net>
46 lines
1.2 KiB
C
46 lines
1.2 KiB
C
/* SPDX-License-Identifier: GPL-2.0-or-later */
|
|
/*
|
|
* Hardware monitoring driver for PMBus devices
|
|
*
|
|
* Copyright (c) 2010, 2011 Ericsson AB.
|
|
*/
|
|
|
|
#ifndef _PMBUS_H_
|
|
#define _PMBUS_H_
|
|
|
|
#include <linux/bits.h>
|
|
|
|
/* flags */
|
|
|
|
/*
|
|
* PMBUS_SKIP_STATUS_CHECK
|
|
*
|
|
* During register detection, skip checking the status register for
|
|
* communication or command errors.
|
|
*
|
|
* Some PMBus chips respond with valid data when trying to read an unsupported
|
|
* register. For such chips, checking the status register is mandatory when
|
|
* trying to determine if a chip register exists or not.
|
|
* Other PMBus chips don't support the STATUS_CML register, or report
|
|
* communication errors for no explicable reason. For such chips, checking
|
|
* the status register must be disabled.
|
|
*/
|
|
#define PMBUS_SKIP_STATUS_CHECK BIT(0)
|
|
|
|
/*
|
|
* PMBUS_WRITE_PROTECTED
|
|
* Set if the chip is write protected and write protection is not determined
|
|
* by the standard WRITE_PROTECT command.
|
|
*/
|
|
#define PMBUS_WRITE_PROTECTED BIT(1)
|
|
|
|
struct pmbus_platform_data {
|
|
u32 flags; /* Device specific flags */
|
|
|
|
/* regulator support */
|
|
int num_regulators;
|
|
struct regulator_init_data *reg_init_data;
|
|
};
|
|
|
|
#endif /* _PMBUS_H_ */
|