- 25 Nov, 2014 30 commits
-
-
Dmitry Eremin-Solenikov authored
Change clk_enable/disable() calls to clk_prepare_enable() and clk_disable_unrepapre(). Signed-off-by:
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by:
Lee Jones <lee.jones@linaro.org>
-
Lee Jones authored
First spotted pointless (incorrect) indent of 'if (ret)', then double indentations of a struct attribute 'mask'. Decided to go through the whole file and make amendments instead and this is the result. Signed-off-by: -
Dmitry Eremin-Solenikov authored
Some boards with TC6393XB chip require full state restore during system resume thanks to chip's VCC being cut off during suspend (Sharp SL-6000 tosa is one of them). Failing to do so would result in ohci Oops on resume due to internal memory contentes being changed. Fail ohci suspend on tc6393xb is full state restore is required. Recommended workaround is to unbind tmio-ohci driver before suspend and rebind it after resume. Cc: stable@vger.kernel.org Signed-off-by:
-
Andy Shevchenko authored
MFD core already cares about failing registration. It will remove successfully registered devices in case of error. Thus, no need to repeatedly call mfd_remove_devices(). Fixes: 5829e9b6 (mfd: lpc_sch: Accomodate partial population of the MFD devices) Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by:
-
Joe Perches authored
Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by:
Joe Perches <joe@perches.com> Acked-by:
Charles Keepax <ckeepax@opensource.wolfsonmicro.com> Signed-off-by:
-
Guenter Roeck authored
ab8500_restart is not called from anywhere in the kernel, so drop it. Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Acked-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Lee Jones authored
Also rid superfluous gotos and label. Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: -
Pramod Gurav authored
Error check around return value of devm_ioremap is missing. Add the same to avoid NULL pointer dereference. Signed-off-by:
Pramod Gurav <pramod.gurav@smartplayin.com> Acked-by:
-
Tony Lindgren authored
Commit e7cd1d1e ("mfd: twl4030-power: Add generic reset configuration") accidentally removed the compatible flag for "ti,twl4030-power" that should be there as documented in the binding. If "ti,twl4030-power" only the poweroff configuration is done by the driver. Fixes: e7cd1d1e ("mfd: twl4030-power: Add generic reset configuration") Cc: stable@vger.kernel.org # v3.16+ Reported-by:
"Dr. H. Nikolaus Schaller" <hns@goldelico.com> Signed-off-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
-
Micky Ching authored
Fix rts5227&5249 failed send buffer cmd after suspend, PM_CTRL3 should reset before send any buffer cmd after suspend. Otherwise, buffer cmd will failed, this will lead resume fail. Signed-off-by:
Micky Ching <micky_ching@realsil.com.cn> Signed-off-by:
-
Krzysztof Kozlowski authored
Add information which regulators can be disabled during system suspend. Suggested-by:
Javier Martinez Canillas <javier.martinez@collabora.co.uk> Signed-off-by:
Krzysztof Kozlowski <k.kozlowski@samsung.com> Signed-off-by:
-
Javier Martinez Canillas authored
This reverts commit b7cde707 ("mfd: sec-core: Prepare regulators for suspend state to reduce power-consumption") Commit b7cde707 called regulator_suspend_prepare() to prepare the regulators for a suspend state. But it did from the device pm suspend handler while the regulator suspend prepare function iterates over all regulators and not only the one managed by this device so it doesn't seems to be correct to call it from within a device driver. It is better to call the regulator suspend prepare/finish functions from platform code instead so this patch reverts the mentioned commit. Suggested-by:
Doug Anderson <dianders@chromium.org> Signed-off-by:
Chanwoo Choi <cw00.choi@samsung.com> Reviewed-by:
-
Krzysztof Kozlowski authored
Add a "maxim,max77693-charger" of_compatible to the mfd_cell so the MFD child device (the charger) will have its own of_node set. This will be used by the max77693 charger driver in next patches to obtain battery configuration from DTS. Signed-off-by:
-
Will Sheppard authored
This was found whilst running checkpatch.pl on arizona-spi. WARNING: Missing a blank line after declarations + struct arizona *arizona = spi_get_drvdata(spi); + arizona_dev_exit(arizona); Signed-off-by:
Will Sheppard <wsheppard@embedded-bits.co.uk> Signed-off-by:
-
Krzysztof Kozlowski authored
Remove old MAX77693_NUM_IRQ_MUIC_REGS define. Not used anywhere. Signed-off-by:
-
Boris Brezillon authored
The HLCDC IP available on some Atmel SoCs (i.e. at91sam9n12, at91sam9x5 family or sama5d3 family) exposes 2 subdevices: - a display controller (controlled by a DRM driver) - a PWM chip This patch adds documentation for atmel-hlcdc DT bindings. Signed-off-by:
Boris Brezillon <boris.brezillon@free-electrons.com> Tested-by:
Anthony Harivel <anthony.harivel@emtrion.de> Tested-by:
Ludovic Desroches <ludovic.desroches@atmel.com> Signed-off-by:
-
Boris Brezillon authored
The HLCDC IP available on some Atmel SoCs (i.e. at91sam9n12, at91sam9x5 family or sama5d3 family) exposes 2 subdevices: - a display controller (controlled by a DRM driver) - a PWM chip The MFD device provides a regmap and several clocks (those connected to this hardware block) to its subdevices. This way concurrent accesses to the iomem range are handled by the regmap framework, and each subdevice can safely access HLCDC registers. Signed-off-by:
-
Johan Hovold authored
Make sure to always honour multi-function devices registered with PLATFORM_DEVID_NONE (-1) or PLATFORM_DEVID_AUTO (-2) as id base. In this case it does not make sense to append the cell id to the mfd-id base and potentially change the requested behaviour. Specifically this will allow multi-function devices to be registered with PLATFORM_DEVID_AUTO while still having non-zero cell ids. Signed-off-by:
Johan Hovold <johan@kernel.org> Signed-off-by:
-
Johan Hovold authored
Use mfd_add_hotplug_devices() helper to register the subdevices. Compile-only tested. Signed-off-by:
Jiri Kosina <jkosina@suse.cz> Signed-off-by:
-
Johan Hovold authored
Use mfd_add_hotplug_devices helper to register the subdevices. Signed-off-by:
-
Pankaj Dubey authored
Currently a syscon entity can be only registered directly through a platform device that binds to a dedicated syscon driver. However in certain use cases it is desirable to make a device used with another driver a syscon interface provider. For example, certain SoCs (e.g. Exynos) contain system controller blocks which perform various functions such as power domain control, CPU power management, low power mode control, but in addition contain certain IP integration glue, such as various signal masks, coprocessor power control, etc. In such case, there is a need to have a dedicated driver for such system controller but also share registers with other drivers. The latter is where the syscon interface is helpful. In case of DT based platforms, this patch decouples syscon object from syscon platform driver, and allows to create syscon objects first time when it is required by calling of syscon_regmap_lookup_by APIs and keep a list of such syscon objects along with syscon provider device_nodes and regmap handles. For non-DT based platforms, this patch keeps syscon platform driver structure so that syscon can be probed and such non-DT based drivers can use syscon_regmap_lookup_by_pdev API and access regmap handles. Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based, we can completely remove platform driver of syscon, and keep only helper functions to get regmap handles. Suggested-by:
Arnd Bergmann <arnd@arndb.de> Suggested-by:
Tomasz Figa <tomasz.figa@gmail.com> Tested-by:
Vivek Gautam <gautam.vivek@samsung.com> Tested-by:
Pankaj Dubey <pankaj.dubey@samsung.com> Reviewed-by:
Heiko Stuebner <heiko@sntech.de> Reviewed-by:
-
Jaewon Kim authored
This patch add haptic DT binding documentation and example to support haptic driver in max77693 Multifunction device. Signed-off-by:
Jaewon Kim <jaewon02.kim@samsung.com> Acked-by:
-
Jaewon Kim authored
This patch add haptic of_compatible in order to use the haptic device driver using Devicetree. Signed-off-by:
-
Jaewon Kim authored
This patch add regmap_haptic initialization to use haptic register map in haptic device driver. Signed-off-by:
-
Johannes Pointner authored
Adds of_compatible strings to mfd_cells for sub devices of the tps65217. Signed-off-by:
Johannes Pointner <johannes.pointner@br-automation.com> Signed-off-by:
-
Lee Jones authored
Merge branches 'ib-mfd-gpio-i2c-3.19', 'ib-mfd-iio-3.19' and 'ib-mfd-regulator-v3.19', tag 'ib-mfd-regulator-clk-v3.19' into ibs-for-mfd-merged Immutable branch between MFD, Regulator and Clk, due for v3.19
-
Chanwoo Choi authored
This patch adds the binding documentation for Samsung S2MPS13 PMIC which is similiar with existing S2MPS14 PMIC. S2MPS13 has the different number of regulators from S2MPS14 and RTC/Clock is the same with the S2MPS14. Signed-off-by:
Sangbeom Kim <sbkim73@samsung.com> Reviewed-by:
-
Chanwoo Choi authored
This patch adds the support for S2MPS13 PMIC clock which is same with existing S2MPS14 RTC IP. But, S2MPS13 uses all of clocks (32khz_{ap|bt|cp}). Signed-off-by:Michael Turquette <mturquette@linaro.org> Signed-off-by:
-
Chanwoo Choi authored
This patch adds S2MPS13 regulator device to existing S2MPS11 device driver. The S2MPS13 has just different number of regulators from S2MPS14. The S2MPS13 regulator device includes LDO[1-40] and BUCK[1-10]. Signed-off-by:
Mark Brown <broonie@kernel.org> Reviewed-by:
-
Chanwoo Choi authored
This patch adds the support for Samsung S2MPS13 PMIC device to the sec-core MFD driver. The S2MPS13 is very similar with existing S2MPS14 and includes PMIC/ RTC/CLOCK devices. Signed-off-by:
-
- 19 Nov, 2014 4 commits
-
-
Dan Carpenter authored
Sparse catches a couple endian bugs. Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Acked-by:
Octavian Purdila <octavian.purdila@intel.com> Signed-off-by:
-
Octavian Purdila authored
The echo field in dln2_transfer_complete comes directly from an USB transfer and we should not trust it is valid. Reported-by:
-
Octavian Purdila authored
This fixes the following kbuild test robot warning: >> drivers/i2c/busses/i2c-dln2.c:70:1-4: WARNING: end returns can be simplified if negative or 0 value Reported-by:
kbuild test robot <fengguang.wu@intel.com> Reported-by:
Julia Lawall <julia.lawall@lip6.fr> Signed-off-by:
Wolfram Sang <wsa@the-dreams.de> Signed-off-by:
-
Octavian Purdila authored
If wait_for_completion_interruptible_timeout returns a positive value it may be propagated as the return value of _dln2_transfer. This contradicts the documentation of the function and exposes unnecessary internals to the callers. This patch makes sure to set the return value to 0 in that case. Reported-by:
-
- 18 Nov, 2014 3 commits
-
-
Jacob Pan authored
This is no longer needed in that platform driver_register will do it. Signed-off-by:
Jacob Pan <jacob.jun.pan@linux.intel.com> Acked-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
-
Jacob Pan authored
IRQ numbers in axp20x devices are defined with high-order bit first in each IRQ enable/status registers. On Intel platforms it is more common to number IRQs with least significant bit first. Therefore, sharing IRQ# between the two is very difficult. Since AXP288 is a customized PMIC for Intel platform and the amount of shared IRQs are very small, we use separate IRQ numbering. This also fixes collision and a duplicate in WBTO interrupt. e.g. For the 16 interrupts controlled in IRQ enabled registers 1 & 2, on axp20x for ARM, the PMIC local IRQ numbers and register bits are mapped as: IRQ#: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 --------------------------------------------------------- ARM: 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 Intel: 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 Signed-off-by:
Todd Brandt <todd.e.brandt@linux.intel.com> Signed-off-by:
-
Aaron Lu authored
Add the module device id table so that the driver can be automatically loaded once the platform device is created. Signed-off-by:
Aaron Lu <aaron.lu@intel.com> Signed-off-by:
-
- 10 Nov, 2014 3 commits
-
-
Daniel Baluta authored
This patch adds GPIO and IRQ support for the Diolan DLN-2 GPIO module. Information about the USB protocol interface can be found in the Programmer's Reference Manual [1], see section 2.9 for the GPIO module commands and responses. [1] https://www.diolan.com/downloads/dln-api-manual.pdfSigned-off-by:
Daniel Baluta <daniel.baluta@intel.com> Signed-off-by:
-
Laurentiu Palcu authored
This patch adds support for the Diolan DLN-2 I2C master module. Due to hardware limitations it does not support SMBUS quick commands. Information about the USB protocol interface can be found in the Programmer's Reference Manual [1], see section 6.2.2 for the I2C master module commands and responses. [1] https://www.diolan.com/downloads/dln-api-manual.pdfSigned-off-by:
Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by:
-
Octavian Purdila authored
This patch implements the USB part of the Diolan USB-I2C/SPI/GPIO Master Adapter DLN-2. Details about the device can be found here: https://www.diolan.com/i2c/i2c_interface.html. Information about the USB protocol can be found in the Programmer's Reference Manual [1], see section 1.7. Because the hardware has a single transmit endpoint and a single receive endpoint the communication between the various DLN2 drivers and the hardware will be muxed/demuxed by this driver. Each DLN2 module will be identified by the handle field within the DLN2 message header. If a DLN2 module issues multiple commands in parallel they will be identified by the echo counter field in the message header. The DLN2 modules can use the dln2_transfer() function to issue a command and wait for its response. They can also register a callback that is going to be called when a specific event id is generated by the device (e.g. GPIO interrupts). The device uses handle 0 for sending events. [1] https://www.diolan.com/downloads/dln-api-manual.pdfSigned-off-by:
-
