Re: [PATCH RFC v4 4/8] drm/i2c: tda998x: Add support of a DT graph of ports

On Mon, 21 Sep 2015 10:19:18 -0500 Rob Herring wrote: > On 09/18/2015 06:06 AM, Jyri Sarha wrote: > > From: Jean-Francois Moine > > > > Two kinds of ports may be declared in a DT graph of ports: video and audio. > > This patch accepts the port value from a

Re: [PATCH 28/38] video/omap: remove invalid check

On 21/09/15 16:34, Andrzej Hajda wrote: > regno is unsigned so it cannot be negative. > > The problem has been detected using proposed semantic patch > scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci [1]. > > [1]: http://permalink.gmane.org/gmane.linux.kernel/2038576 > >

Re: [PATCH v2] fbdev: omap2: connector-dvi: use of_get_i2c_adapter_by_node interface

On 15/09/15 16:12, Vladimir Zapolskiy wrote: > This change is needed to properly lock I2C bus driver, which serves DDC. > > Prior to this change i2c_put_adapter() is misused, which may lead to > an overflow over zero of I2C bus driver user counter. > > Signed-off-by: Vladimir Zapolskiy

Re: [PATCH v3 10/24] ARM: davinci: Add set dma_mask to eDMA devices

On 09/23/2015 08:25 PM, Tony Lindgren wrote: > * Peter Ujfalusi [150922 03:01]: >> The upcoming change to merge the arch/arm/common/edma.c into >> drivers/dma/edma.c will need this change when booting daVinci devices in >> no DT mode. >> >> Signed-off-by: Peter Ujfalusi

[PATCH v4 01/25] ARM: common: edma: Fix channel parameter for irq callbacks

In case when the interrupt happened for the second eDMA the channel number was incorrectly passed to the client driver. Signed-off-by: Peter Ujfalusi CC: --- arch/arm/common/edma.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff

[PATCH v4 00/25] dmaengine/ARM: Merge the edma drivers into one

Hi, Changes since v3: - Separated the two (patch 10/11 in v2 patch 10 in v3) patch which got squashed by accident for v3 - Added Tony's Acked-by to patch 11 (for mach-oamp2 part) Changes since v2: - devm_kasprintf format string fixed - Additional patch to enable dynamic paRAM slot usage when

[PATCH v4 05/25] ARM/dmaengine: edma: Move of_dma_controller_register to the dmaengine driver

If the of_dma_controller is registered in the non dmaengine driver we could have race condition: the of_dma_controller has been registered, but the dmaengine driver is not yet probed. Drivers requesting DMA channels during this window will fail since we do not yet have dmaengine drivers

[PATCH v4 03/25] dmaengine: edma: Simplify and optimize the edma_execute path

The code path in edma_execute() and edma_callback() can be simplified and make it more optimal. There is not need to call in to edma_execute() when the transfer has been finished for example. Also the handling of missed/first or next batch of paRAMs can be done in a more optimal way.

[PATCH v4 17/25] dmaengine: edma: Use the edma_write_slot instead open coded memcpy_toio

edma_write_slot() is for writing an entire paRAM slot. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index fe8cde21b497..d759abc80bef 100644 ---

[PATCH v4 16/25] dmaengine: edma: Use dev_dbg instead pr_debug

We have access to dev, so it is better to use the dev_dbg for debug prints. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index

[PATCH v4 15/25] dmaengine: edma: Cleanup regarding the use of dev around the code

Be consistent and do not mix the use of dev, >dev, etc in the functions. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index

[PATCH v4 18/25] dmaengine: edma: Print warning when linking slots from different eDMA

Warning message in case of linking between paRAM slots in different eDMA controllers. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index d759abc80bef..b0102984e98d

[PATCH v4 08/25] ARM/dmaengine: edma: Remove limitation on the number of eDMA controllers

Since the driver stack no longer depends on lookup with id number in a global array of pointers, the limitation for the number of eDMAs are no longer needed. We can handle as many eDMAs in legacy and DT boot as we have memory for them to allocate the needed structures. Signed-off-by: Peter

[PATCH v4 07/25] ARM/dmaengine: edma: Public API to use private struct pointer

Instead of relying on indexes pointing to edma private date in the global pointer array, pass the private data pointer via the public API. Signed-off-by: Peter Ujfalusi --- arch/arm/common/edma.c | 305 ++--- drivers/dma/edma.c

[PATCH v4 02/25] ARM: common: edma: Remove unused functions

We no longer have users for these functions so they can be removed. Remove also unused enums from the header file. Signed-off-by: Peter Ujfalusi --- arch/arm/common/edma.c | 376 - include/linux/platform_data/edma.h | 33

[PATCH v4 12/25] dmaengine: edma: Allocate memory dynamically for bitmaps and structures

Instead of using defines to specify the size of different arrays and bitmaps, allocate the memory for them based on the information we get from the HW itself. Since these defines are set based on the worst case, there are devices where they are not valid. Signed-off-by: Peter Ujfalusi

[PATCH v4 04/25] ARM: davinci/common: Convert edma driver to handle one eDMA instance per driver

Currently we have one device created to handle all (maximum 2) eDMAs in the system. With this change all eDMA instance will have it's own device/driver. This change is needed for further cleanups in the eDMA driver stack since the one device/driver to handle all eDMAs in the system was not

[PATCH v4 14/25] dmaengine: edma: Use devm_kcalloc when possible

When allocating a memory for number of items it is better (looks better) to use devm_kcalloc. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index

[PATCH v4 22/25] dmaengine: edma: Simplify and optimize ccerr interrupt handler

No need to run through the bits in QEMR and CCERR events since they will not trigger any action, so just clearing the errors there is fine. In case of the missed event the loop can be optimized so we spend less time to handle the event. Signed-off-by: Peter Ujfalusi ---

[PATCH v4 20/25] dmaengine: edma: Simplify the interrupt handling

With the merger of the arch/arm/common/edma.c code into the dmaengine driver, there is no longer need to have per channel callback/data storage for interrupt events. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 447

[PATCH v4 21/25] dmaengine: edma: Move the pending error check into helper function

In the ccerr interrupt handler the code checks for pending errors in the error status registers in two different places. Move the check out to a helper function. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 20 1 file changed, 12

[PATCH v4 11/25] ARM/dmaengine: edma: Merge the two drivers under drivers/dma/

Move the code out from arch/arm/common and merge it inside of the dmaengine driver. This change is done with as minimal change to the code as possible to avoid any possibilities to introducing regression. Signed-off-by: Peter Ujfalusi Acked-by: Tony Lindgren

[PATCH v4 25/25] dmaengine: edma: Dynamic paRAM slot handling if HW supports it

If the eDMA3 has support for channel paRAM slot mapping we can utilize it to allocate slots on demand and save precious slots for real transfers. On am335x the eDMA has 64 channels which means we can unlock 64 paRAM slots out from the available 256. Signed-off-by: Peter Ujfalusi

[PATCH v4 19/25] dmaengine: edma: Consolidate the comments for functions

Remove or rewrite the comments for the internal functions. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 86 +++--- 1 file changed, 11 insertions(+), 75 deletions(-) diff --git a/drivers/dma/edma.c

[PATCH v4 24/25] dmaengine: edma: Rename bitfields for slot and channel usage tracking

The names chosen for the bitfields were quite confusing and given no real information on what they are used for... edma_inuse -> slot_inuse: tracks the slot usage/availability edma_unused -> channel_unused: tracks the channel usage/availability Signed-off-by: Peter Ujfalusi

[PATCH v4 13/25] dmaengine: edma: Parameter alignment and long line fixes

Makes the code a bit more readable. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 84 -- 1 file changed, 44 insertions(+), 40 deletions(-) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index

[PATCH v4 23/25] dmaengine: edma: Read channel mapping support only once from HW

Instead of directly reading it from CCCFG register take the information out once when we set up the configuration from the HW. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git

[PATCH v4 10/25] ARM: davinci: Add dma_mask to eDMA devices

The upcoming change to merge the arch/arm/common/edma.c into drivers/dma/edma.c will need this change when booting daVinci devices in no DT mode. Signed-off-by: Peter Ujfalusi --- arch/arm/mach-davinci/devices-da8xx.c | 2 ++ arch/arm/mach-davinci/dm355.c | 1 +

[PATCH v4 06/25] ARM: common: edma: Internal API to use pointer to 'struct edma'

Merge the iomem into the 'struct edma' and change the internal (static) functions to use pointer to the edma_cc instead of the ctlr number. Signed-off-by: Peter Ujfalusi --- arch/arm/common/edma.c | 400 - 1 file changed,

[PATCH v4 09/25] ARM: davinci: Use platform_device_register_full() to create pdev for eDMA

Convert the eDMA platform device creation to use struct platform_device_info XX __initconst and platform_device_register_full() This will allow us to cleanly specify the dma_mask for the devices in an upcoming patch. Signed-off-by: Peter Ujfalusi ---

Re: [PATCH] omapdss: acx565akm: Fix module autoload for OF platform driver

On 18/09/15 21:44, Luis de Bethencourt wrote: > 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 > --- > > Hello, > > This patch adds the missing

Re: [PATCH] omapdss: acx565akm: Fix module autoload for OF platform driver

On 24/09/15 13:17, Tomi Valkeinen wrote: > > > On 18/09/15 21:44, Luis de Bethencourt wrote: >> 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

[PATCHv2 2/2] power_supply: Add support for tps65217-charger.

This patch adds support for the tps65217 charger driver. This driver is responsible for controlling the charger aspect of the tps65217 mfd. Currently, this mainly consists of turning on and off the charger, but some other features of the charger can be supported through this driver.

Re: [PATCH 1/3] iio:adc: add iio driver for Palmas (twl6035/7) gpadc

Am 23.09.2015 um 15:26 schrieb Peter Meerwald : > >> This driver code was found as: >> >> https://android.googlesource.com/kernel/tegra/+/aaabb2e045f31e5a970109ffdaae900dd403d17e/drivers/staging/iio/adc >> >> Fixed various compilation issues and test this driver on omap5

[PATCHv2 0/2] Add support for tps65217 charger

Hi all, The following series add initial support for tps65217 battery charger. Changes since v1: - Requested by Sebastian Reichel - Set prev_ac_online at the beginning of the tps56217_charger_irq() - Use devm_power_supply_register call. - Fix style problems reported by checkpatch.pl

[PATCHv2 1/2] devicetree: Add TPS65217 charger binding.

The TPS65217 charger is a subnode of the TPS65217 MFD. Signed-off-by: Enric Balletbo i Serra --- .../devicetree/bindings/power_supply/tps65217_charger.txt| 12 1 file changed, 12 insertions(+) create mode 100644

Re: Linux 4.2.0-rc5: am335x: musb warnings

Hi Felipe, On Tue, Sep 8, 2015 at 5:45 PM, Felipe Balbi wrote: > On Mon, Sep 07, 2015 at 12:32:10PM +0200, Yegor Yefremov wrote: >> On Mon, Aug 31, 2015 at 7:41 PM, Felipe Balbi wrote: >> > Hi, >> > >> > On Mon, Aug 31, 2015 at 11:41:59AM -0500, Felipe Balbi wrote:

Re: AM3517 usb host issue

On 22/05/15 14:50, Felipe Balbi wrote: > Hi, > > On Fri, May 22, 2015 at 11:04:33AM +0300, Ben Dooks wrote: >> I am trying to get the full-speed USB host working on an custom >> AM3517 device with the 3.18.12 kernel. The hardware works (a >> 2.6.37 kernel has been used for testing). >> >> Does

[PATCH 09/17] ARM: dts: OMAP24xx: add reset data

Add iva, dsp and system reset control as DT data.. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/omap2420.dtsi | 24 arch/arm/boot/dts/omap2430.dtsi | 17 + 2 files changed, 41 insertions(+) diff --git

[PATCH 14/17] ARM: OMAP2: hwmod: AMx3xx: remove redundant reset info

AMx3xx reset info is now parsed from DT, so the data under hwmod database can be removed. Signed-off-by: Tero Kristo --- .../mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c | 30 arch/arm/mach-omap2/omap_hwmod_33xx_data.c |8 --

[PATCH 10/17] ARM: OMAP2+: hwmod: parse reset information from DT

DT can now be used to provide reset information, so parse this to avoid the need to have reset info under hwmod data. This patch disables the support for existing reset data under hwmod data, so shall be applied only after the DT reset conversion. Signed-off-by: Tero Kristo ---

[PATCH 08/17] ARM: dts: am33xx: add reset data

Add reset data for pruss, gfx, wkup-m3, and system reset. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/am33xx.dtsi | 24 1 file changed, 24 insertions(+) diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi index

[PATCH 01/17] ARM: OMAP2+: PRM: add support for reset controller

PRM driver now supports reset controller for the defined reset lines. Reset configurations are provided through device tree. Later, functionality like hwmod and system reboot will be changed to use the generic framework. Signed-off-by: Tero Kristo ---

[PATCH 04/17] ARM: dts: omap4: add reset data

Copy over the reset data from hwmod database to DT. After this is taken into use, the data in hwmod database can be removed. A new node has been also added for ipu to support ipu resets. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/omap4.dtsi | 27

[PATCH 16/17] ARM: OMAP2+: hwmod: remove obsolete support for some hardreset logic

OMAP4+ prcm struct no longer requires the support for the rstctrl / rstst offsets, as the data is parsed from DT for all platforms. Remove also the obsolete hardreset support functions from the hwmod code. Signed-off-by: Tero Kristo --- arch/arm/mach-omap2/omap_hwmod.c | 108

[PATCH 06/17] ARM: dts: dra7: add reset data

Copy over the reset data from kernel to DT. Currently, only system reset has been defined, but rest can be added later once needed. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/dra7.dtsi |7 +++ 1 file changed, 7 insertions(+) diff --git

[PATCH 00/17] ARM: OMAP2+: reset controller support

Hi, This series adds reset controller support on top of the existing PRM/PRCM code. All the currently defined reset sources in hwmod databases are moved over to DT, and all except OMAP3 hwmod resets are also removed. OMAP3 hwmod reset data can be removed once OMAP3 is DT only. Reboot support is

[PATCH 02/17] ARM: OMAP2+: hwmod: parse also soc hierarchy for hwmod compatible nodes

Previously the code was only parsing ocp hierarchy, which misses mpu and iva/dsp nodes at least, which still contain hwmod support. Parse also the soc hierarchy to include these. Signed-off-by: Tero Kristo --- arch/arm/mach-omap2/omap_hwmod.c | 15 --- 1 file

[PATCH 05/17] ARM: dts: omap5: add reset data

Copy over the reset data from hwmod database to DT. After this is taken into use, the data in hwmod database can be removed. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/omap5.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH 07/17] ARM: dts: am4372: add reset data

Add reset data for pruss, gfx, wkup-m3 and system reset. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/am4372.dtsi | 24 1 file changed, 24 insertions(+) diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi index

[PATCH 03/17] ARM: dts: omap3: add reset data

Copy over the reset data from hwmod database to DT. After this is taken into use, the data in hwmod database can be removed. A new node has been also added for sad2d to support sad2d resets. Signed-off-by: Tero Kristo --- arch/arm/boot/dts/omap3.dtsi | 21

[PATCH 13/17] ARM: OMAP5: hwmod_data: remove reset data

This is provided via DT, and no longer needed in the hwmod database. Signed-off-by: Tero Kristo --- arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 14 -- 1 file changed, 14 deletions(-) diff --git a/arch/arm/mach-omap2/omap_hwmod_54xx_data.c

[PATCH 17/17] ARM: OMAP2+: PRM: remove redundant system reset code

This is now handled via the reset controller and the provided information from DT, so the legacy support code is no longer needed. OMAP3 version shall be removed once OMAP3 is also DT only. Signed-off-by: Tero Kristo --- arch/arm/mach-omap2/prm2xxx.c | 15 ---

[PATCH 11/17] ARM: OMAP2+: use system reset info from device tree data

System reset mapping used by reboot is now provided through DT data and a reset controller. Use this instead of the hardcoded PRM API. Signed-off-by: Tero Kristo --- arch/arm/mach-omap2/Makefile |6 -- arch/arm/mach-omap2/am33xx-restart.c | 27

[PATCH 12/17] ARM: OMAP4: hwmod_data: remove reset data

This is provided via DT and no longer needed under the hwmod database. Signed-off-by: Tero Kristo --- arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 48 +++- 1 file changed, 5 insertions(+), 43 deletions(-) diff --git

[PATCH 15/17] ARM: OMAP24xx: hwmod: remove reset data from hwmod database

These are now parsed from DT, so not needed under the hwmod database anymore. Signed-off-by: Tero Kristo --- arch/arm/mach-omap2/omap_hwmod_2420_data.c | 13 - arch/arm/mach-omap2/omap_hwmod_2430_data.c |7 --- 2 files changed, 20 deletions(-) diff --git

Re: [PATCHv2 2/2] power_supply: Add support for tps65217-charger.

Hi, On Thu, Sep 24, 2015 at 09:23:25AM +0200, Enric Balletbo i Serra wrote: > This patch adds support for the tps65217 charger driver. This driver is > responsible for controlling the charger aspect of the tps65217 mfd. > Currently, this mainly consists of turning on and off the charger, but >

Re: [PATCHv2 2/2] power_supply: Add support for tps65217-charger.

Hi, 2015-09-24 17:45 GMT+02:00 Sebastian Reichel : > Hi, > > On Thu, Sep 24, 2015 at 09:23:25AM +0200, Enric Balletbo i Serra wrote: >> This patch adds support for the tps65217 charger driver. This driver is >> responsible for controlling the charger aspect of the tps65217 mfd.

Re: [PATCH RFC v4 4/8] drm/i2c: tda998x: Add support of a DT graph of ports

On Thu, Sep 24, 2015 at 5:36 AM, Jean-Francois Moine wrote: > On Mon, 21 Sep 2015 10:19:18 -0500 > Rob Herring wrote: > >> On 09/18/2015 06:06 AM, Jyri Sarha wrote: >> > From: Jean-Francois Moine >> > >> > Two kinds of ports may be declared in

Re: [PATCH 0/3] ARM: dts: dra7-evm: enable leds and gpio-keys support

Hi Tony, On 08/27/2015 08:20 AM, Grygorii Strashko wrote: This series enables support for leds and gpio-keys which is available on dra7-evm. It also adds pcf8575 gpio expander (i2c1 addr 20) Grygorii Strashko (3): ARM: dts: dra7-evm: add pcf8575 gpio expander (i2c1 addr 20) ARM: dts:

[PATCHv3 0/2] Add support for tps65217 charger

Hi all, The following series add initial support for tps65217 battery charger. Changes since v2: - Requested by Sebastian Reichel - Assign prev_ac_online to ac_online is no longer needed at this place. - Remove power_supply_unregistersince it wouldb be called by managed resources.

[PATCHv3 2/2] power_supply: Add support for tps65217-charger.

This patch adds support for the tps65217 charger driver. This driver is responsible for controlling the charger aspect of the tps65217 mfd. Currently, this mainly consists of turning on and off the charger, but some other features of the charger can be supported through this driver.

[PATCHv3 1/2] devicetree: Add TPS65217 charger binding.

The TPS65217 charger is a subnode of the TPS65217 MFD. Signed-off-by: Enric Balletbo i Serra --- .../devicetree/bindings/power_supply/tps65217_charger.txt| 12 1 file changed, 12 insertions(+) create mode 100644

Re: [PATCHv3 0/2] Add support for tps65217 charger

Hi, On Thu, Sep 24, 2015 at 09:44:19PM +0200, Enric Balletbo i Serra wrote: > The following series add initial support for tps65217 battery charger. Thanks, queued. -- Sebastian signature.asc Description: Digital signature

Re: [RFC PATCH 6/7] gpio: omap: move pm runtime in irq_chip.irq_bus_lock/sync_unlock

On 09/24/2015 03:28 PM, Linus Walleij wrote: On Tue, Aug 18, 2015 at 4:10 AM, Grygorii Strashko wrote: The PM runtime API can't be used in atomic contex on -RT even if it's configured as irqsafe. As result, below error report can be seen when PM runtime API called

Re: [RFC PATCH 6/7] gpio: omap: move pm runtime in irq_chip.irq_bus_lock/sync_unlock

On Tue, Aug 18, 2015 at 4:10 AM, Grygorii Strashko wrote: > The PM runtime API can't be used in atomic contex on -RT even if > it's configured as irqsafe. As result, below error report can > be seen when PM runtime API called from IRQ chip's callbacks >

Re: [PATCH v2] ARM: dts: >: fix address translation for pbias

* Kishon Vijay Abraham I [150904 05:12]: > "ARM: dts: : add minimal l4 bus > layout with control module support" moved pbias_regulator dt node > from being a child node of ocp to be the child node of > 'syscon'. Since 'syscon' doesn't have the 'ranges' property, > address

Re: [PATCH] clk: ti: fix dual-registration of uart4_ick

On 09/23/2015 08:30 PM, Tony Lindgren wrote: * Ben Dooks [150923 07:53]: On the OMAP AM3517 platform the uart4_ick gets registered twice, causing any power managment to /dev/ttyO3 to fail when trying to wake the device up. This solves the following oops: []

Re: All OMAP platforms: MMC is broken

* Tony Lindgren [150924 16:42]: > * Russell King - ARM Linux [150924 02:04]: > > Nightly testing has revealed that both the OMAP3430 LDP and the OMAP4430 > > SDP fail to boot due to lack of working MMC. Both platforms fail to > > find their rootfs,