- 14 Apr, 2021 40 commits
-
-
Wei Yongjun authored
The sparse tool complains as follows: drivers/mfd/atc260x-i2c.c:45:27: warning: symbol 'atc260x_i2c_of_match' was not declared. Should it be static? This symbol is not used outside of atc260x-i2c.c, so this commit marks it static. Fixes: f7cb7fe3 ("mfd: Add MFD driver for ATC260x PMICs") Reported-by:
Hulk Robot <hulkci@huawei.com> Signed-off-by:
Wei Yongjun <weiyongjun1@huawei.com> Reviewed-by:
Cristian Ciocaltea <cristian.ciocaltea@gmail.com> Signed-off-by:
Lee Jones <lee.jones@linaro.org>
-
Heikki Krogerus authored
From now on only accepting complete software nodes. Signed-off-by:
Heikki Krogerus <heikki.krogerus@linux.intel.com> Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
-
Heikki Krogerus authored
Software node was always created for the device if it was supplied with additional device properties, so those nodes might as well be constant. Signed-off-by:
-
Andy Shevchenko authored
There is no point to have non-constant device properties in this driver. Thus, constify them for good. Signed-off-by:
-
Heikki Krogerus authored
The old device property API is going to be removed and replaced with the newer software node API. This prepares MFD subsystem for the transition. Signed-off-by:
-
Hubert Streidl authored
By default the PMIC DA9063 2-wire interface is SMBus compliant. This means the PMIC will automatically reset the interface when the clock signal ceases for more than the SMBus timeout of 35 ms. If the I2C driver / device is not capable of creating atomic I2C transactions, a context change can cause a ceasing of the clock signal. This can happen if for example a real-time thread is scheduled. Then the DA9063 in SMBus mode will reset the 2-wire interface. Subsequently a write message could end up in the wrong register. This could cause unpredictable system behavior. The DA9063 PMIC also supports an I2C compliant mode for the 2-wire interface. This mode does not reset the interface when the clock signal ceases. Thus the problem depicted above does not occur. This patch tests for the bus functionality "I2C_FUNC_I2C". It can reasonably be assumed that the bus cannot obey SMBus timings if this functionality is set. SMBus commands most probably are emulated in this case which is prone to the latency issue described above. This patch enables the I2C bus mode if I2C_FUNC_I2C is set or otherwise keeps the default SMBus mode. Signed-off-by:
Hubert Streidl <hubert.streidl@de.bosch.com> Signed-off-by:
Mark Jonas <mark.jonas@de.bosch.com> Reviewed-by:
Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by:
-
Krzysztof Kozlowski authored
The driver was using subsys_initcall() because in old times deferred probe was not supported everywhere and specific ordering was needed. Since probe deferral works fine and specific ordering is discouraged (hides dependencies between drivers and couples their boot order), the driver can be converted to regular module_platform_driver. Signed-off-by:
Krzysztof Kozlowski <krzk@kernel.org> Tested-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Milo Kim's email in TI bounces with permanent error (550: Invalid recipient). Last email from him on LKML was in 2017. Move Milo Kim to credits and remove the separate driver entries for: - TI LP855x backlight driver, - TI LP8727 charger driver, - TI LP8788 MFD (ADC, LEDs, charger and regulator) drivers. Signed-off-by:
Sebastian Reichel <sre@kernel.org> Signed-off-by:
-
Xu Yilun authored
This patch adds maintainer info for Intel MAX 10 mfd driver. Signed-off-by:
Xu Yilun <yilun.xu@intel.com> Reviewed-by:
Tom Rix <trix@redhat.com> Signed-off-by:
-
Matthew Gerlach authored
This patch adds access tables to the MAX 10 BMC regmap. This prevents the host from accessing the unwanted I/O space. It also filters out the invalid outputs when reading the regmap debugfs interface. Signed-off-by:
Matthew Gerlach <matthew.gerlach@linux.intel.com> Signed-off-by:
-
Xu Yilun authored
The version register is the only one in the legacy I/O space to be accessed, so it is not necessary to define the legacy base & version register offset. A direct definition of the legacy version register address would be fine. Signed-off-by:
-
Xu Yilun authored
This patch fixes the max register address of MAX 10 BMC. The range 0x20000000 ~ 0x200000fc are for control registers of the QSPI flash controller, which are not accessible to host. Signed-off-by:
-
Yang Li authored
Fixes the following coccicheck warning: drivers/mfd/lm3533-core.c:361:60-61: WARNING opportunity for kobj_to_dev() Reported-by:
Abaci Robot <abaci@linux.alibaba.com> Signed-off-by:
Yang Li <yang.lee@linux.alibaba.com> Signed-off-by:
-
Luca Ceresoli authored
Document the LP8756x-Q1 and LP87524-Q1 ICs reset pin. Signed-off-by:
Luca Ceresoli <luca@lucaceresoli.net> Reviewed-by:
Rob Herring <robh@kernel.org> Signed-off-by:
-
Xu Yilun authored
This patch adds maintainer info for Intel MAX 10 mfd driver. Signed-off-by:
-
Wei Yongjun authored
The sparse tool complains as follows: drivers/mfd/ene-kb3930.c:36:15: warning: symbol 'kb3930_power_off' was not declared. Should it be static? The symbol is not used outside of this file. Reported-by:
Lubomir Rintel <lkundrak@v3.sk> Signed-off-by:
-
Arnd Bergmann authored
The ST-Ericsson U300 platform has been removed, so this driver is no longer needed. Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Reviewed-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Linus Walleij authored
Nobody is passing the module parameter to disable the battery management portions so just drop this parameter. Signed-off-by:
-
Rikard Falkeborn authored
In stmpe_devices_init(), the start and end field of these structs are modified, so they can not be const. Add a comment to those structs that lacked it to reduce the risk that this happens again. This reverts commit 8d7b3a6d. Fixes: 8d7b3a6d ("mfd: stmpe: Constify static struct resource") Reported-by:
Rikard Falkeborn <rikard.falkeborn@gmail.com> Reviewed-by:
-
Luca Ceresoli authored
This define appears incorrect, but it is completely unused so it can be removed. Signed-off-by:
-
Wei Yongjun authored
The sparse tool complains as follows: drivers/mfd/arizona-spi.c:28:31: warning: symbol 'reset_gpios' was not declared. Should it be static? drivers/mfd/arizona-spi.c:29:31: warning: symbol 'ldoena_gpios' was not declared. Should it be static? Those symbols are not used outside of arizona-spi.c, so this commit marks them static. Fixes: e9338367 ("mfd: arizona: Add support for ACPI enumeration of WM5102 connected over SPI") Reported-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Charles Keepax <ckeepax@opensource.cirrus.com> Signed-off-by:
-
Jiapeng Chong authored
Fix the following coccicheck warning: ./include/linux/mfd/db8500-prcmu.h:723:8-9: WARNING: return of 0/1 in function 'db8500_prcmu_is_ac_wake_requested' with return type bool. Reported-by:
Jiapeng Chong <jiapeng.chong@linux.alibaba.com> Signed-off-by:
-
Lee Jones authored
Signed-off-by: -
Andreas Kemnade authored
Convert the RN5T618 binding to DT schema format. Also clearly state which regulators are available. Signed-off-by:
Andreas Kemnade <andreas@kemnade.info> Reviewed-by:
-
Lee Jones authored
Immutable branch between MFD and Watchdog due for the v5.13 merge window
-
Lee Jones authored
Merge tags 'ib-mfd-clk-gpio-regulator-rtc-v5.13', 'ib-mfd-extcon-v5.13', 'ib-mfd-input-v5.13-1', 'ib-mfd-platform-x86-v5.13', 'ib-mfd-power-v5.13', 'ib-mfd-pwm-rtc-v5.13-1' and 'ib-regulator-list-ramp-helpers-v5.13' into ibs-for-mfd-merged Immutable branch between MFD, Clock, GPIO, Regulator and RTC due for the v5.13 merge window Immutable branch between MFD and Extcon due for the v5.13 merge window Immutable branch between MFD and Input due for the v5.13 merge window Immutable branch between MFD and Platform/x86 due for the v5.13 merge window Immutable branch between MFD and Power due for the v5.13 merge window Immutable branch between MFD, PWM and RTC due for the v5.13 merge window
-
Matti Vaittinen authored
Add maintainer entries for ROHM BD71815AGW drivers. New regulator and GPIO drivers were introduced for these PMICs. Signed-off-by:
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com> Signed-off-by:
-
Matti Vaittinen authored
BD71815 contains similar RTC block as BD71828. Only the address offsets seem different. Support also BD71815 RTC using rtc-bd70528. Signed-off-by:
Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by:
-
Matti Vaittinen authored
ROHM BD71815 also provide clk signal for RTC. Add control for gating this clock. Signed-off-by:
Stephen Boyd <sboyd@kernel.org> Signed-off-by:
-
Matti Vaittinen authored
Support voltage control for regulators on ROHM BD71815 PMIC. ROHM BD71815 contains 5 bucks, 7 LDOs and a boost (intended for LED). Bucks 1 and 2 support HW state based voltage level and enable states. Other regulators support HW state based enable states. All bucks and LDOs 1-5 allow voltage changes for RUN state and LDO4 can be enabled/disabled via GPIO. LDO3 does support changing between two predetermined voltages by using a GPIO but this functionality is not included in this commit. This work is derived from driver originally written by Tony Luo <luofc@embedinfo.com> - although not much of original work is left. Signed-off-by:
Mark Brown <broonie@kernel.org> Signed-off-by:
-
Matti Vaittinen authored
Use generic regamp ramp-delay helper function instead of implementing own. Signed-off-by:
-
Matti Vaittinen authored
The ROHM BD71815 supports setting voltage levels/regulator status for HW-states "RUN", "SUSPEND", "LPSR" and "SNVS". Add DT parsing helper also for SNVS state. Signed-off-by:
-
Matti Vaittinen authored
The helper for obtaining HW-state based DVS voltage levels currently only works for regulators using linear-ranges. Extend support to regulators with simple linear mappings and add also proper error path if pickable-ranges regulators call this. Signed-off-by:
-
Matti Vaittinen authored
Support GPO(s) found from ROHM BD71815 power management IC. The IC has two GPO pins but only one is properly documented in the data-sheet. The driver exposes by default only the documented GPO. The second GPO is connected to E5 pin and is marked as GND in the data-sheet. Control for this undocumented pin can be enabled using a special DT property. This driver is derived from work by Peter Yang <yanglsh@embest-tech.com> although not so much of the original is left. Signed-off-by:
Bartosz Golaszewski <bgolaszewski@baylibre.com> Acked-by:
-
Matti Vaittinen authored
Add core support for ROHM BD71815 Power Management IC. The IC integrates regulators, a battery charger with a coulomb counter, a real-time clock (RTC), clock gate and general-purpose outputs (GPO). Signed-off-by:
-
Matti Vaittinen authored
Sort the ID list so it is easier to see which ICs are present. Signed-off-by:
-
Matti Vaittinen authored
Add chip ID for ROHM BD71815 and PMIC so that drivers can identify this IC. Signed-off-by:
-
Matti Vaittinen authored
Document DT bindings for ROHM BD71815. BD71815 is a single-chip power management IC mainly for battery-powered portable devices. The IC integrates 5 bucks, 7 LDOs, a boost driver for LED, a battery charger with a Coulomb counter, a real-time clock, a 32kHz clock and two general-purpose outputs although only one is documented by the data-sheet. Signed-off-by:
-
Matti Vaittinen authored
Add binding documentation for regulators on ROHM BD71815 PMIC. 5 bucks, 7 LDOs and a boost for LED. Signed-off-by:
-
Matti Vaittinen authored
The BD71828 allows configuring the clk32kout pin mode to CMOS or open-drain. Add device-tree property for specifying the preferred mode. Signed-off-by:
-
