kernel/linux.git/include/linux/mfd/samsung, branch v6.6.132

rtc: s5m: Drop S5M8763 support

2023-04-26T10:40:26+00:00

The S5M8763 MFD has no device tree compatible, and since board file support for it was removed, there's no way to use this MFD. After removing the remaining code for it from the MFD driver, also remove support for it in the s5m RTC driver, and all remaining references to it. Signed-off-by: David Virag Acked-by: Alexandre Belloni Reviewed-by: Krzysztof Kozlowski Signed-off-by: Lee Jones Link: https://lore.kernel.org/r/20230131183008.4451-3-virag.david003@gmail.com

mfd: sec: Remove PMICs without compatibles

2023-04-26T10:40:26+00:00

The S5M8751 and S5M8763 PMIC chips have no corresponding compatible values, so since board file support was removed for this driver, there is no way to specify these PMICs as present in boards anymore. Remove leftovers of these chips since it's dead code. Signed-off-by: David Virag Reviewed-by: Krzysztof Kozlowski Signed-off-by: Lee Jones Link: https://lore.kernel.org/r/20230131183008.4451-2-virag.david003@gmail.com

mfd: sec: Remove unused platform data members

2021-06-02T09:51:18+00:00

The Samsung PMIC drivers for early chipsets like S5M8767 stored quite a lot in platform data (struct sec_platform_data). The s5m8767 regulator driver currently references only some of its fields. Newer regulator drivers (e.g. s2mps11) use even less platform data fields. Clean up the structure to reduce memory footprint and source code size. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Lee Jones

mfd: sec: Enable wakeup from suspend via devicetree property

2021-06-02T09:51:18+00:00

Set device wakeup capability from devicetree property (done by drivers core), instead of always setting it to 0 (because value in platform data is not assigned). This should not have visible effect on actual resuming from suspend because the child device - S5M RTC driver - is responsible for waking up and sets device wakeup unconditionally. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Lee Jones

mfd: sec: Remove unused irq_base in platform data

2021-06-02T09:51:18+00:00

The 'irq_base' field of platform data structure is not assigned, therefore its default value of 0 has no impact and can be safely dropped. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Lee Jones

mfd: sec: Remove unused device_type in platform data

2021-06-02T09:51:18+00:00

The 'device_type' field of platform data structure is not used and can be safely dropped. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Lee Jones

mfd: sec: Remove unused cfg_pmic_irq in platform data

2021-06-02T09:51:18+00:00

The 'cfg_pmic_irq' field of platform data structure is not used and can be safely dropped. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Lee Jones

Merge branch 'regulator-5.3' into regulator-next

2019-07-04T16:34:32+00:00

regulator: s2mps11: Adjust supported buck voltages to real values

2019-07-02T11:43:25+00:00

The driver was registering buck regulators with unsupported range of voltages for S2MPS11 devices. Basically it assumed that all 256 values are possible for a single 8-bit I2C register controlling buck's voltage. This is not true, as datasheet describes subset of these which can be used. For example for buck[12346] the minimum voltage is 650 mV which corresponds to register value of 0x8. The driver was however registering regulator starting at 600 mV, so for a step of 6.25 mV this gave the same result. However this allowed to try to configure regulators to unsupported values. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Mark Brown

regulator: s2mps11: Add support for disabling S2MPS11 regulators in suspend

2019-06-24T16:26:57+00:00

The driver supported turning off regulators in suspend only for S2MPS14 device. However this makes also sense for S2MPS11 and can reduce the power consumption during suspend to RAM. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Mark Brown