Re: [PATCH v3] ARM: OMAP: Change all cpu_is_* occurences to soc_is_*

Hi, * Keerthy [151013 22:47]: > --- a/arch/arm/mach-omap2/soc.h > +++ b/arch/arm/mach-omap2/soc.h > @@ -155,6 +155,13 @@ static inline int soc_is_omap(void) > * cpu_is_omap443x():True for OMAP4430 > * cpu_is_omap446x():True for OMAP4460 > *

Re: [PATCH v2 1/3] ARM: OMAP2: DRA7: Modify optimize string comparisons in soc_is calls

* Keerthy [151014 22:14]: > Currently everytime soc_is calls are made, firstly device tree nodes > are parsed and then string comparisons are made to determine the > soc version. Optimizing it to be done one time and store the result. > Use the stored value in all the subsequent

Re: [PATCH v2 3/3] ARM: OMAP2: AM43XX: Modify optimize string comparisons in soc_is calls

* Keerthy [151014 22:14]: > Currently everytime soc_is calls are made, firstly device tree nodes > are parsed and then string comparisons are made to determine the > soc version. Optimizing it to be done one time and store the result. > Use the stored value in all the subsequent

Re: [PATCH v2 0/3] ARM: handle imprecise aborts from firmware in common code

u: remove the workaround imprecise abort fault handler) > as it has already been applied. I have build and boot tested the three patches in this series on top of next-20151016 with the kernelci.org system[1][2]. It found no new build/boot regressions and also I can confirm it fixes the

Re: [PATCH] ARM: OMAP2+: Fix oops with LPAE and more than 2GB of memory

* Lokesh Vutla [151015 08:21]: > +Richard > > On Thursday 15 October 2015 07:35 PM, Tony Lindgren wrote: > > * Lokesh Vutla [151015 01:02]: > >> Hi Tony, > >> > >> On Wednesday 14 October 2015 09:32 PM, Tony Lindgren wrote: > >>> * Lokesh Vutla

Re: [PATCH 00/11] arm: omap: timer cleanups

* Felipe Balbi [151016 09:27]: > Hi Tony, > > Here's the a series of timer cleanups (and a new 32k clocksource driver > which is safe to apply during v4.3 merge window. We're only missing, > now, two changes to enable TWD timer for AM437x. > > All patches are also available in a

[PATCH] clocksource: ti-32k: make it depend on GENERIC_CLOCKSOURCE

the new ti 32k clocksource driver should depend on GENERIC_CLOCKSOURCE because of its reliance on sched_clock_register(). Let's enable that to avoid any possible build errors and/or warnings on randbuilds. Signed-off-by: Felipe Balbi --- drivers/clocksource/Kconfig | 1 + 1 file

Re: [PATCH] clocksource: ti-32k: make it depend on GENERIC_CLOCKSOURCE

* Felipe Balbi [151016 14:17]: > the new ti 32k clocksource driver should depend on > GENERIC_CLOCKSOURCE because of its reliance on > sched_clock_register(). > > Let's enable that to avoid any possible build errors > and/or warnings on randbuilds. Thanks applying this on

Re: [PATCH v3 00/27] memory: omap-gpmc: mtd: nand: Support GPMC NAND on non-OMAP platforms

* Roger Quadros [151006 04:13]: > > Fine. The updated series is now at > > g...@github.com:rogerq/linux.git > * [new branch] for-v4.4/gpmc-v4 Looks like it produces some build errors, this with RMKs 3430 and 4430 only .configs: drivers/memory/omap-gpmc.c:2035:43: error:

Re: [PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

Hi Felipe, [auto build test ERROR on omap/for-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base] url: https://github.com/0day-ci/linux/commits/Felipe-Balbi/arm-omap-timer-cleanups/20151017-002649 config: i386-allmodconfig (attached as .config)

[PATCH v2 07/14] dmaengine: edma: Refactor the dma device and channel struct initialization

Move all code under one function to do the dma device and eDMA channel related setup so they are not scattered around the driver. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 79 +- 1 file changed, 37

[PATCH v2 09/14] dmaengine: edma: Merge the of parsing functions

Instead of nesting functions just merge them since the resulting function is still small and readable. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 24 1 file changed, 8 insertions(+), 16 deletions(-) diff --git a/drivers/dma/edma.c

[PATCH v2 10/14] dmaengine: ti-dma-crossbar: Add support for crossbar on AM33xx/AM43xx

The DMA event crossbar on AM33xx/AM43xx is different from the one found in DRA7x family. Instead of a single event crossbar it has 64 identical mux attached to each eDMA event line. When the 0 event mux is selected, the default mapped event is going to be routed to the corresponding eDMA event

Re: [PATCH 3/3] ARM: dts: Add basic support for isee igepv5

Hi Tony, Many thanks for the patch 2015-10-13 19:18 GMT+02:00 Tony Lindgren : > With omap5-board-common.dtsi, we can now easily add support for various omap5 > board variants. Let's add minimal support for isee igepv5. > > So far I've tested that basic things work, such as

[PATCH v2 12/14] dmaengine: edma: New device tree binding

With the old binding and driver architecture we had many issues: No way to assign eDMA channels to event queues, thus not able to tune the system by moving specific DMA channels to low/high priority servicing. We moved the cyclic channels to high priority within the code, but that was just a

[PATCH v2 11/14] dmaengine: Kconfig: edma: Select TI_DMA_CROSSBAR in case of ARCH_OMAP

Since the crossbar is needed for eDMA when it is used on OMAP like platforms (am335x/am437x and later DRA7xx), select the crossbar to be built if ARCH_OMAP is set. Signed-off-by: Peter Ujfalusi --- drivers/dma/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 13/14] ARM: DTS: am33xx: Use the new DT bindings for the eDMA3

Switch to use the ti,edma3-tpcc and ti,edma3-tptc binding for the eDMA3 and enable the DMA even crossbar with ti,am335x-edma-crossbar. With the new bindings boards can customize and tweak the DMA channel priority to match their needs. With the new binding the memcpy is safe to be used since with

[PATCH v2 06/14] dmaengine: edma: Get qDMA channel information from HW also

Query the number of qDMA channels from CCCFG register. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index eaf1f9e4bde0..ea851ab05c8e 100644 --- a/drivers/dma/edma.c

[PATCH v2 03/14] dmaengine: edma: Simplify function parameter list for channel operations

Instead of passing a pointer to struct edma_cc and the channel number, pass only the pointer to the edma_chan structure for the given channel. This struct contains all the information needed by the functions and the use of this makes it obvious that most of the sanity checks can be removed from

[PATCH v2 08/14] dmaengine: edma: Do not allocate memory for edma_rsv_info in case of DT boot

The channel/slot reservation is not supported when booted with DT so there is not need to allocate memory. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c index

Re: [PATCH v2 0/5] mtd: nand: Fix support for NAND DMA prefetch

On 15/10/15 20:37, Franklin S Cooper Jr wrote: > NAND DMA prefetch has been broken for awhile and seems to have only > worked for SDMA based devices > > This patchset fixes DMA prefetch to work on both EDMA and SDMA devices > > Test on: > am335x gp evm > am437x gp evm > am37x gp evm > > This

[PATCH v2 14/14] ARM: DTS: am437x: Use the new DT bindings for the eDMA3

Switch to use the ti,edma3-tpcc and ti,edma3-tptc binding for the eDMA3 and enable the DMA even crossbar with ti,am335x-edma-crossbar. With the new bindings boards can customize and tweak the DMA channel priority to match their needs. With the new binding the memcpy is safe to be used since with

Re: [PATCH 2/2 v2] ARM: DRA7/335x/437x: hwmod: Remove gpmc address space from hwmod data

On 15/10/15 19:27, Franklin S Cooper Jr wrote: > GPMC address information is provided by device tree. No longer need > to include this information within hwmod. > > Signed-off-by: Franklin S Cooper Jr Acked-by: Roger Quadros -- cheers, -roger -- To unsubscribe

Re: [PATCH 1/2 v2] ARM: DRA7/335x/437x/OMAP4: hwmod: Remove elm address space from hwmod data

On 15/10/15 19:27, Franklin S Cooper Jr wrote: > ELM address information is provided by device tree. No longer need > to include this information within hwmod. > > Signed-off-by: Franklin S Cooper Jr Acked-by: Roger Quadros -- cheers, -roger -- To unsubscribe

Re: [PATCH v2 1/3] ARM: catch pending imprecise abort on unmask

Am Donnerstag, den 15.10.2015, 16:32 +0100 schrieb Russell King - ARM Linux: > On Thu, Oct 15, 2015 at 12:32:20PM +0200, Lucas Stach wrote: > > Install a non-faulting handler just before unmasking imprecise aborts > > and switch back to the regular one after unmasking is done. > > > > This

[PATCH v2 05/14] dmaengine: edma: Merge map_dmach_to_queue into assign_channel_eventq

edma_assign_channel_eventq() is a wrapper around edma_map_dmach_to_queue() We can merge the content of the later so we will have only one function to be used for mapping channels to given eventq Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 56

[PATCH v2 01/14] dmaengine: edma: Remove alignment constraint for memcpy

Despite the claim by the original commit adding the memcpy support, eDMA does not have constraint on the alignment of src, dst or length in increment mode. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 13 ++--- 1 file changed, 6 insertions(+), 7

[PATCH v2 00/14] dmaenigne: edma/ti-crossbar: fixes, new bindings

Hi, Changes since v1: - Comments in the memcpy optimization patch extended - The crossbar patch has been improved: - debug prints changed - fallback xbar parameters now type specific as the fallback values for DRA7 are not valid for AM33xx crossbar. - New patch for Kconfig to select the

[PATCH v2 04/14] dmaengine: edma: Correct PaRAM access function names (_parm_ to _param_)

These inline functions are designed to modify parts of the PaRAM in eDMA. Change the names accordingly. Signed-off-by: Peter Ujfalusi --- drivers/dma/edma.c | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/drivers/dma/edma.c

[PATCH v2 02/14] dmaengine: edma: Optimize memcpy operation

If the transfer is shorted then 64K we can complete it with one ACNT burst by configuring ACNT to the length of the copy, this require one paRAM slot. Otherwise we use two paRAM slots for the copy: slot1: will copy (length / 32767) number of 32767 byte long blocks slot2: will be configured to copy

Re: [GIT PULL 2/2] omap device tree changes for v4.4

On Thursday 15 October 2015 14:04:26 Tony Lindgren wrote: > * Arnd Bergmann [151015 13:40]: > > On Wednesday 14 October 2015 14:38:59 Tony Lindgren wrote: > > > > > Note that this branch is against v4.3-rc4 as that contains critical > > > MMC related fixes to boot with MMC working

Re: DM3730 vs 3630 DSS Cock dividers

On 16/10/15 13:23, Tomi Valkeinen wrote: > Ok, so the clock data in the DT and the data in the dss are in sync and > according to the TRM. So the patch in this thread is not correct. > > How about 3730? Are we sure the dpll clocks are the same for 3730 and 3630? > > So both 3730 and 3630 are

Re: DM3730 vs 3630 DSS Cock dividers

On 13/10/15 10:55, Tero Kristo wrote: > TRMs are correct, 3630 does not have x2 multiplier after DPLL4. > > In the clock data, dpll4_m4x2 path is an x1 multiplier on omap3630, it > is easier to represent this in DT than completely remove the dpll4_*x2 > nodes for omap36xx. This is how it was

[RFC PATCH 3/3] arm: plat-omap: Add PWM dmtimer platforma data quirks

In order to set the currently platform dependent dmtimer functions pointers as platform data for the pwm-omap-dmtimer platform driver, add it to plat-omap auxdata_lookup table. Suggested-by: Tony Lindgren Signed-off-by: Neil Armstrong ---

[RFC PATCH 2/3] pwm: Add PWM driver for OMAP using dual-mode timers

Adds support for using a OMAP dual-mode timer with PWM capability as a Linux PWM device. The driver controls the timer by using the dmtimer API. Add a platform_data structure for each pwm-omap-dmtimer nodes containing the dmtimers functions in order to get driver not rely on platform specific

[RFC PATCH 1/3] arm: plat-omap: dmtimer: Add clock source from DT

Add a function which sets the timer source from the clocks binding on dm_timer_prepare call. In case the clocks property is not valid, it falls back to the set_source() with 32_KHZ clock as default. Suggested-by: Tony Lindgren Signed-off-by: Neil Armstrong

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

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 evm. Signed-off-by: Pradeep Goudagunta Signed-off-by: H.

[PATCH v3 3/3] ARM: dts: omap5-uevm: enable iio gpadc for Palmas

Signed-off-by: H. Nikolaus Schaller --- arch/arm/boot/dts/omap5-uevm.dts | 10 ++ 1 file changed, 10 insertions(+) diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts index 0e8128b..63f81bb 100644 --- a/arch/arm/boot/dts/omap5-uevm.dts

[PATCH v3 2/3] iio:adc:palmas: add DT support

From: Marek Belisko Code was found at: https://android.googlesource.com/kernel/tegra/+/a90856a6626d502d42c6e7abccbdf9d730b36270%5E%21/#F1 Signed-off-by: Laxman Dewangan Signed-off-by: Marek Belisko [Fixed minor typos + add

[PATCH v3 0/3] Add Palmas iio gpadc

H. Nikolaus Schaller (2): iio:adc: add iio driver for Palmas (twl6035/7) gpadc ARM: dts: omap5-uevm: enable iio gpadc for Palmas Marek Belisko (1): iio:adc:palmas: add DT support .../devicetree/bindings/iio/adc/palmas-gpadc.txt | 48 ++ arch/arm/boot/dts/omap5-uevm.dts

[RFC PATCH 0/3] pwm: omap: Add PWM support using dual-mode timers

This patch is based on an earlier patch by NeilBrown which is based on a older patch from Grant Erickson which provided PWM devices using the 'legacy' interface. The pwm driver was renamed to not be confused with the OMAP4 PWM dedicated hardware and was cleaned with the review from Thierry

Re: [RFC PATCH 1/3] arm: plat-omap: dmtimer: Add clock source from DT

Hi, Neil Armstrong writes: > Add a function which sets the timer source from the clocks > binding on dm_timer_prepare call. > > In case the clocks property is not valid, it falls back to > the set_source() with 32_KHZ clock as default. > > Suggested-by: Tony Lindgren

Re: [PATCH 3/3] ARM: dts: Add basic support for isee igepv5

* Enric Balletbo Serra [151016 01:26]: > Hi Tony, > > Many thanks for the patch > > 2015-10-13 19:18 GMT+02:00 Tony Lindgren : > > With omap5-board-common.dtsi, we can now easily add support for various > > omap5 > > board variants. Let's add minimal

Re: [PATCH] gpio: omap: fix static checker warning

On Fri, Sep 25, 2015 at 9:06 PM, Grygorii Strashko wrote: > This patch fixes below static checker warning by changing > type of irq field in struct gpio_bank from u16 to int. Nobody's saying anything, I'll just apply this. Yours, Linus Walleij -- To unsubscribe from

Re: [GIT PULL 2/2] omap device tree changes for v4.4

* Arnd Bergmann [151016 02:50]: > On Thursday 15 October 2015 14:04:26 Tony Lindgren wrote: > > * Arnd Bergmann [151015 13:40]: > > > On Wednesday 14 October 2015 14:38:59 Tony Lindgren wrote: > > > > > > > Note that this branch is against v4.3-rc4 as that contains

Re: DM3730 vs 3630 DSS Cock dividers

* Adam Ford [151016 04:12]: > I will do that this weekend. I only have one DM3730 board but based on the > patch and the dialog, I don't appear to be the only one. OK great. My guess this same issue applies to all 36xx meaning 3630, 3703, 3715 and 3730. No idea where the

Re: [RFC PATCH 2/3] pwm: Add PWM driver for OMAP using dual-mode timers

Hi, Neil Armstrong writes: > Adds support for using a OMAP dual-mode timer with PWM capability > as a Linux PWM device. The driver controls the timer by using the > dmtimer API. > > Add a platform_data structure for each pwm-omap-dmtimer nodes containing > the dmtimers

[PATCH 00/11] arm: omap: timer cleanups

Hi Tony, Here's the a series of timer cleanups (and a new 32k clocksource driver which is safe to apply during v4.3 merge window. We're only missing, now, two changes to enable TWD timer for AM437x. All patches are also available in a branch which you can pull should you choose. Pull request

[PATCH 02/11] arm: omap2: timer: get rid of obfuscating macros

those macros just make it a lot more difficult to grep around and actually find similarities. In this patch, we will simply remove them and replace with actual functions and later commits will come to further clean this up. Signed-off-by: Felipe Balbi ---

[PATCH 03/11] arm: omap2: timer: add a gptimer argument to sync32k_timer_init()

as it turns out, __omap_gptimer_init() and __omap_sync32k_timer_init() are essentially the same thing, but __omap_gptimer_init() wants to always use gptimer. Instead of forcing all those devices to pass a use_gptimer cmdline argument, we add a new function argument to __omap_sync32k_timer_init()

[PATCH 06/11] arm: omap2: timer: move realtime_counter_init() around

no functional changes, just moving that function closer to its calling location. Signed-off-by: Felipe Balbi --- arch/arm/mach-omap2/timer.c | 114 ++-- 1 file changed, 56 insertions(+), 58 deletions(-) diff --git

[PATCH 04/11] arm: omap2: timer: remove __omap_gptimer_init()

__omap_sync32k_timer_init(), now takes the clock source as a parameter. This means we no longer need __omap_gptimer_init(). Note that __omap_sync32k_timer_init() will be renamed in a follow-up patch as it's not longer 32k source specific. Signed-off-by: Felipe Balbi ---

[PATCH 05/11] arm: omap2: timer: provide generic sync32k_timer_init function

instead of constantly defining a small wrapper around __omap_sync32k_timer_init(), let's define a generic one which can be used by all OMAPs. Signed-off-by: Felipe Balbi --- arch/arm/mach-omap2/board-generic.c | 10 +- arch/arm/mach-omap2/board-ldp.c | 2 +-

[PATCH 07/11] arm: omap2: timer: always call clocksource_of_init() when DT

If booting with DT, let's make sure to always call clocksource_of_init() as this will make it easier to move timer code to drivers/clocksource in the future. Signed-off-by: Felipe Balbi --- arch/arm/mach-omap2/timer.c | 3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH 10/11] arm: omap2+: select 32k clocksource driver

Now that we have a 32k clocksource driver, let's select it for OMAP2PLUS builds. Signed-off-by: Felipe Balbi --- arch/arm/mach-omap2/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig index

[PATCH 01/11] arm: omap2: timer: always define omap4_local_timer_init

omap4_local_timer_init() can be used by other platforms as is. At least AM437x wants to use it. Instead of making omap4-only and providing a stub for builds without OMAP4, we can just make sure that function is always available for all SoCs that need it. Reported-by: Nishanth Menon

[PATCH 09/11] clocksource: add TI 32.768 Hz counter driver

Introduce a new clocksource driver for Texas Instruments 32.768 Hz device which is available on most OMAP-like devices. Cc: Daniel Lezcano Cc: Thomas Gleixner Cc: linux-ker...@vger.kernel.org Acked-by: Daniel Lezcano

[PATCH 11/11] arm: omap2: timer: limit hwmod usage to non-DT boots

now that we have a working 32k clocksource driver, we can limit HWMOD usage to non-DT boots and rely on clocksource_of_init() every time we boot with DT. While at that, also make sure that we don't disable the 32-counter device so it gets probed by its driver. Signed-off-by: Felipe Balbi

[PATCH 08/11] arm: omap2: timer: rename omap_sync32k_timer_init()

this function is not only about the 32k sync timer, it's OMAP's generic init_time implementation. Let's rename it to make that detail easier to notice. Signed-off-by: Felipe Balbi --- arch/arm/mach-omap2/board-generic.c | 10 +- arch/arm/mach-omap2/board-ldp.c | 2 +-