31 Oct, 2015
13 commits
-
The invoked functions already return zero on success or a negative
errno code so there is no need to open code the logic in the caller.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
The invoked functions already return zero on success or a negative
errno code so there is no need to open code the logic in the caller.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
The ret variable is not needed since is not used in the
function. Remove the variable and just return 0 instead.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
The ret variable is not needed since is not used in the
function. Remove the variable and just return 0 instead.Signed-off-by: Javier Martinez Canillas
Acked-by: Charles Keepax
Signed-off-by: Lee Jones -
The ret variable is not needed since is not used in the
function. Remove the variable and just return 0 instead.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
tps6105 driver provides two cells. One is for GPIO and another one is
for selected mode depending on platform data. When tps6105x is used in
GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell
.name == NULL. This value causes an oops in platform_device_register()
later.The following patch adds a mfd_cell for each possible mode thereby
excluding .name assignment in runtime.Signed-off-by: Denis Grigoryev
Signed-off-by: Lee Jones -
The driver handles wakeup irq correctly using irq_set_irq_wake. There's
no need to use IRQF_NO_SUSPEND while registering the interrupt.This patch removes the use of IRQF_NO_SUSPEND flag.
Signed-off-by: Sudeep Holla
Signed-off-by: Lee Jones -
Signed-off-by: Lee Jones
-
This patch solves:
on x86_64:
when CONFIG_ACPI is not enabled:
../drivers/mfd/intel_soc_pmic_bxtwc.c: In function 'bxtwc_probe':
../drivers/mfd/intel_soc_pmic_bxtwc.c:342:2:
error: implicit declaration of function 'acpi_evaluate_integer' [-Werror=implicit-function-declaration]
status = acpi_evaluate_integer(handle, "_HRV", NULL, &hrv);
^Reported-by: Randy Dunlap
Signed-off-by: Lee Jones -
Some EC implementations include a small nvram space used to store
verified boot context data. This boolean property lets us indicate
whether this space is available or not on a specific EC implementation.Signed-off-by: Emilio López
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
The lpc_ich_cells array gives the wrong impression about the
relationship between the watchdog and GPIO devices. They are
completely distinct devices, so this patch separates the
array into distinct mfd_cell structs per device.A side effect of removing the array, is that the lpc_cells enum
is no longer needed.Signed-off-by: Aaron Sierra
Acked-by: Andy Shevchenko
Signed-off-by: Lee Jones -
Add MFD core driver for Intel Broxton Whiskey Cove PMIC,
which is specially accessed by hardware IPC, not a generic
I2C deviceSigned-off-by: Qipeng Zha
Signed-off-by: Lee Jones -
IRQ control registers of Intel Broxton Whisky Cove PMIC are
separated in two parts, so add secondary IRQ chip.
And the new member of device will be used in PMC IPC regmap APIs.Signed-off-by: Qipeng Zha
Signed-off-by: Lee Jones
26 Oct, 2015
23 commits
-
The driver has a I2C device id table that is used to create the module
aliases which already contains a "rt5033". So the alias is not needed.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
The driver has a I2C device id table that is used to create the module
aliases and also "bcm590xx" isn't a supported I2C id, so it's never used.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
Add tps65217 battery charger subdevice.
Signed-off-by: Enric Balletbo i Serra
Signed-off-by: Lee Jones -
Remove defaults for a bunch of volatile registers and remove
ARIZONA_CTRL_IF_SPI_CFG_1 from the readable list since it doesn't exist
on wm8998 which is I2C only.Signed-off-by: Charles Keepax
Signed-off-by: Lee Jones -
Some Arizona devices have a hardware ANC block present. This patch adds
the registers necessary to configure this hardware block.Signed-off-by: Charles Keepax
Signed-off-by: Lee Jones -
The type of the data for the main Arizona IRQ chip should be struct
arizona not struct regmap_irq_chip_data. The bug is harmless but should
probably be corrected anyway.Signed-off-by: Charles Keepax
Signed-off-by: Lee Jones -
The driver always checks for pdata being NULL except in one place.
Add a check to prevent a possible NULL pointer deference error.Signed-off-by: Javier Martinez Canillas
Acked-by: Charles Keepax
Signed-off-by: Lee Jones -
On Odroid XU3 board (with S2MPS11 PMIC) the PWRHOLD bit in CTRL1
register must be manually set to 0 before initiating power off sequence.One of usual power down methods for Exynos based devices looks like:
1. PWRHOLD pin of PMIC is connected to PSHOLD of Exynos SoC.
2. Exynos holds up this pin during system operation.
3. ACOKB pin of PMIC is pulled up to VBATT and optionally to pin in
other device.
4. When PWRHOLD/PSHOLD goes low, the PMIC will turn off the power if
ACOKB goes high.On Odroid XU3 family the difference is in (3) - the ACOKB is grounded.
This means that PMIC must manually set PWRHOLD field to low and then
wait for signal from Application Processor (the usual change in
PWRHOLD/PSHOLD pin will actually cut off the power).The patch adds respective binding allowing Odroid XU3 device to be
powered off.Signed-off-by: Krzysztof Kozlowski
Reported-by: Anand Moon
Tested-by: Anand Moon
Reviewed-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
There are already helper functions to do 64-bit I/O on 32-bit machines, thus we
don't need to reinvent the wheel. In our case we can't use readq() / writeq()
even on 64-bit kernel since there is a hardware limitation (OCP bus is a 32-bit
bus).Signed-off-by: Andy Shevchenko
Signed-off-by: Lee Jones -
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.Signed-off-by: Luis de Bethencourt
Signed-off-by: Lee Jones -
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.Signed-off-by: Luis de Bethencourt
Signed-off-by: Lee Jones -
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.Signed-off-by: Luis de Bethencourt
Signed-off-by: Lee Jones -
This platform driver has a OF device ID table but the OF module
alias information is not created so module autoloading won't work.Signed-off-by: Luis de Bethencourt
Signed-off-by: Lee Jones -
Introduced by:
commit 8019ff6cfc04 ("regmap: Use reg_sequence for multi_reg_write / register_patch")Interacting with:
commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")Signed-off-by: Nariman Poushin
Acked-by: Geert Uytterhoeven
Signed-off-by: Charles Keepax
Signed-off-by: Lee Jones -
On the STMPE2401 and STMPE2401 altfunction 1 corresponds to the
PWM channels. This oneliner was missing in the case-switch, making
it impossible to enable the PWM channel output.Signed-off-by: Linus Walleij
Signed-off-by: Lee Jones -
Commit 68bab8662f49 ("mfd: twl6040: Optional clk32k clock handling")
added clock handling for the 32k clock from palmas-clk. However, that
patch did not consider a typical situation where twl6040 is built-in,
and palmas-clk is a loadable module like we have in omap2plus_defconfig.If palmas-clk is not loaded before twl6040 probes, we will get a
"clk32k is not handled" warning during booting. This means that any
drivers relying on this clock will mysteriously fail, including
omap5-uevm WLAN and audio.Note that for WLAN, we probably should also eventually get
the clk32kgaudio for MMC3 directly as that's shared between
audio and WLAN SDIO at least for omap5-uevm. It seems the
WLAN chip cannot get it as otherwise MMC3 won't get properly
probed.Fixes: 68bab8662f49 ("mfd: twl6040: Optional clk32k clock handling")
Signed-off-by: Tony Lindgren
Reviewed-by: Felipe Balbi
Signed-off-by: Lee Jones -
Add chip identification support for 88PM860 device
to the pm80x_chip_mapping table.Signed-off-by: Vaibhav Hiremath
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Lee Jones -
The Documentation/devicetree/bindings/mfd/cros-ec.txt DT binding doc lists
"google,cros-ec-i2c" as a compatible string but the corresponding driver
does not have an OF match table. Add the table to the driver so the I2C
core can do an OF style match.Signed-off-by: Javier Martinez Canillas
Signed-off-by: Lee Jones -
…fd-regmap-4.4' and 'ib-mfd-regulator-4.4' into ibs-for-mfd-merged
-
There is a 24c08 chip connected to i2c bus on Intel Galileo Gen2 board. Enable
it via ACPI ID INT3499.Signed-off-by: Andy Shevchenko
Signed-off-by: Wolfram Sang -
On Intel Galileo Gen2 the GPIO expanders are connected to the i2c bus. For
those devices the ACPI table has specific parameters that refer to an actual
i2c host controller. Since MFD now copes with that specific configuration we
have to provide a necessary information how to distinguish devices in ACPI
namespace. Here the _ADR values are provided.Acked-by: Lee Jones
Signed-off-by: Andy Shevchenko
Signed-off-by: Wolfram Sang -
On Intel Galileo boards the GPIO expander is connected to i2c bus. Moreover it
is able to generate interrupt, but interrupt line is connected to GPIO. That's
why we have to have GPIO driver in place when we will probe i2c host with
device connected to it.Acked-by: Lee Jones
Signed-off-by: Andy Shevchenko
Signed-off-by: Wolfram Sang -
There is at least one board on the market, i.e. Intel Galileo Gen2, that uses
_ADR to distinguish the devices under one actual device. Due to this we have to
improve the quirk in the MFD core to handle that board.Acked-by: Rafael J. Wysocki
Acked-by: Lee Jones
Signed-off-by: Andy Shevchenko
Signed-off-by: Wolfram Sang
13 Oct, 2015
4 commits
-
Suggested-by: Lee Jones
Signed-off-by: Adam Thomson
Signed-off-by: Lee Jones -
When referencing other DT bindings documentation, use relative
path rather than absolute.Suggested-by: Lee Jones
Signed-off-by: Adam Thomson
Signed-off-by: Lee Jones -
Signed-off-by: Adam Thomson
Acked-by: Sebastian Reichel
Signed-off-by: Lee Jones -
This adds power supply driver support for the Fuel-Gauge part of
the DA9150 combined Charger and Fuel-Gauge device.Signed-off-by: Adam Thomson
Acked-by: Sebastian Reichel
Signed-off-by: Lee Jones
