- 30 Oct, 2015 39 commits
-
-
Andy Shevchenko authored
Intel Broxton has the same LPSS block than Intel Sunrisepoint so add Broxton PCI IDs to the list. Signed-off-by:
Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
Lee Jones <lee.jones@linaro.org>
-
Mika Westerberg authored
Intel Broxton has the same LPSS block than Intel Sunrisepoint so add Broxton ACPI IDs to the list. Signed-off-by:
-
Dan Carpenter authored
The "jd_active" variable needs to be signed for the error handling to work. Fixes: 143e5887ae57 ('mfd: arizona: factor out checking of jack detection state') Signed-off-by:Dan Carpenter <dan.carpenter@oracle.com> Acked-by:
Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Signed-off-by:
-
Borun Fu authored
This patch adds the mfd cell info for axp288 power key device. Signed-off-by:
Borun Fu <borun.fu@linux.intel.com> Signed-off-by:
Fei Yang <fei.yang@intel.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Document a new Device Tree property 'samsung,s2mps11-wrstbi-ground' indicating that WRSTBI pin of S2MPS13 PMIC is pulled down so corresponding buck warm reset function should be disabled. Signed-off-by:
Krzysztof Kozlowski <k.kozlowski@samsung.com> Signed-off-by:
-
Krzysztof Kozlowski authored
The WRSTBI bit (disabled by default but enabled by bootloader), when set, is responsible for resetting voltages to default values of certain bucks on falling edge of Warm Reset Input pin from AP. However on some boards (with S2MPS13) the pin is pulled down so any suspend will effectively trigger the reset of bucks supplying the power to the little and big cores. In the same time when resuming, these bucks must provide voltage greater or equal to voltage before suspend to match the frequency chosen by cpufreq. If voltage (default value of voltage after reset) is lower than one set by cpufreq before suspend, then system will hang during resuming. Signed-off-by:
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Tested-by:
-
Krzysztof Kozlowski authored
There are different revisions of the same chipset. For example S2MPS13 has more than 2 revisions. They differ slightly in regulator constraints. Print the revision number to easily find which PMIC is used on the board. Signed-off-by:
-
Richard Fitzgerald authored
In the case of a device tree config the code uses the device ID from the DT entry to check which codec is required but when storing the ID into struct arizona it was always using the non-DT SPI device table to get an ID. This patch changes the code to store the correct ID into struct arizona. Signed-off-by:
Richard Fitzgerald <rf@opensource.wolfsonmicro.com> Acked-by:
-
Richard Fitzgerald authored
Remove the use of #ifdefs around each case statement of the chip ID and type validation switches. We must ensure that the contained code still compiles to nothing if support for that codec was not built into the kernel, to prevent creation of link references to missing functions. So the ifdefs are replaced with a use of the IS_ENABLED() macro. Signed-off-by:
-
Richard Fitzgerald authored
The code was using a switch on the code type to execute one of several mfd_add_devices() calls. We're already switching on the code type earlier in the function to select the correct patch function so we can roll selection of the mfd device table into the same switch. Signed-off-by:
-
Richard Fitzgerald authored
If the declared codec type doesn't match the detected type we issue a log message but carry on registering the device, so a dev_warn() is appropriate rather than a dev_err() Signed-off-by:
-
Richard Fitzgerald authored
Currently runtime_suspend will fully power off the codec if the jack detection is not enabled. Not all future codecs will have jack detection so to prepare for these codecs this patch factors out the check so that it be called as needed in the existing codec-specific switch cases. Signed-off-by:
-
Richard Fitzgerald authored
Currently DCVDD isolation is enabled and disabled for runtime_suspend and runtime_resume. Future codecs will not have the isolation control so to prepare for these codecs this patch factors out the isolation control allowing it to be called as needed in the existing codec-specific switch cases. Signed-off-by:
-
Axel Lin authored
This is required since commit 7e507119 ("mfd: tps6105x: Use i2c regmap to access registers"). Signed-off-by:
Axel Lin <axel.lin@ingics.com> Signed-off-by:
-
Sudip Mukherjee authored
We were getting build warning about unused variable 'ret'. The commit c749db571dcf has removed the use of ret but missed removing the variable which is unused now. Fixes: c749db571dcf ("mfd: lm3533: Simplify function return logic") Signed-off-by:Sudip Mukherjee <sudip@vectorindia.org> Signed-off-by:
-
Micky Ching authored
rts522a(rts5227s) is derived from rts5227, and mainly same with rts5227. Add it to file mfd/rts5227.c to support this chip. Signed-off-by:
Micky Ching <micky_ching@realsil.com.cn> Signed-off-by:
-
Axel Lin authored
Rename get_device_type() to da9062_get_device_type(). This function is only used in this file so make it static. Signed-off-by:
-
Luis de Bethencourt authored
The driver depends on ARCH_NOMADIK but there isn't a build dependency so it's a good idea to allow the driver to always be built when the COMPILE_TEST option is enabled. That way, the driver can be built with a config generated by make allyesconfig and check if a patch would break the build. Signed-off-by:
Luis de Bethencourt <luisbg@osg.samsung.com> Signed-off-by:
-
Steve Twiss authored
Definitions for GPIO registers 8, 9, 10, 11, 12 and 13 are added into the register header file. - DA9052_GPIO_8_9_REG 25 - DA9052_GPIO_10_11_REG 26 - DA9052_GPIO_12_13_REG 27 A modification is also made to the MFD core code to define these registers as readable and writable. The functions for da9052_reg_readable() and da9052_reg_writeable() have had their case statements altered to include these new registers. Signed-off-by:
Steve Twiss <stwiss.opensource@diasemi.com> Signed-off-by:
-
Cyrille Pitchen authored
This driver supports the new Atmel Flexcom. The Flexcom is a wrapper which integrates one SPI controller, one I2C controller and one USART. Only one function can be enabled at a time. This driver selects the function once for all, when the Flexcom is probed, according to the value of the new "atmel,flexcom-mode" device tree property. This driver has chosen to present the Flexcom to the system as a MFD so the implementation is seamless for the existing Atmel SPI, I2C and USART drivers. Also the Flexcom embeds FIFOs: the latest patches of the SPI, I2C and USART drivers take advantage of this new feature. Signed-off-by:
Cyrille Pitchen <cyrille.pitchen@atmel.com> Acked-by:
Boris Brezillon <boris.brezillon@free-electrons.com> Acked-by:
Alexandre Belloni <alexandre.belloni@free-electrons.com> Acked-by:
Nicolas Ferre <nicolas.ferre@atmel.com> Signed-off-by:
-
Cyrille Pitchen authored
This patch documents the DT bindings for the Atmel Flexcom which will be introduced by sama5d2x SoCs. These bindings will be used by the actual Flexcom driver to be sent in another patch. Signed-off-by:
-
Cyrille Pitchen authored
This patch defines some macros to be used as value for the "atmel,flexcom-mode" DT property. This value is then written into the Operating Mode (OPMODE) bit field of the Flexcom Mode Register. Signed-off-by:
-
Dan Carpenter authored
The call to kstrtoul() will corrupt memory on 64 bit systems because an int is 4 bytes and a long is 8. Also it's not a good idea to let users trigger a dev_err() because it just ends up flooding /var/log/messages so I removed the printk. Fixes: 2ddd2086ea9c ('mfd: add Intel Broxton Whiskey Cove PMIC driver') Signed-off-by: -
Javier Martinez Canillas authored
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 <javier@osg.samsung.com> Acked-by:
Adam Thomson <Adam.Thomson.Opensource@diasemi.com> Signed-off-by:
-
Javier Martinez Canillas authored
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 authored
The invoked function already returns 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 authored
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 authored
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 authored
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 authored
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 authored
The ret variable is not needed since is not used in the function. Remove the variable and just return 0 instead. Signed-off-by:
-
Grigoryev Denis authored
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 <grigoryev@fastwel.ru> Signed-off-by:
-
Sudeep Holla authored
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 <sudeep.holla@arm.com> Signed-off-by:
-
Lee Jones authored
Signed-off-by: -
Lee Jones authored
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 <rdunlap@infradead.org> Signed-off-by:
-
Emilio López authored
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 <emilio.lopez@collabora.co.uk> Reviewed-by:
-
Aaron Sierra authored
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 <asierra@xes-inc.com> Acked-by:
-
Qipeng Zha authored
Add MFD core driver for Intel Broxton Whiskey Cove PMIC, which is specially accessed by hardware IPC, not a generic I2C device Signed-off-by:
Qipeng Zha <qipeng.zha@intel.com> Signed-off-by:
-
Qipeng Zha authored
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:
-
- 26 Oct, 2015 1 commit
-
-
Javier Martinez Canillas authored
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:
-
