Re: [PATCH] gpio: omap: fix debounce time calculation

On 11/12/2015 11:33 AM, Felipe Balbi wrote: Hi, Grygorii Strashko writes: On 11/12/2015 08:09 PM, Felipe Balbi wrote: Hi, Grygorii Strashko writes: On 11/12/2015 07:50 PM, Felipe Balbi wrote: According to TRM, debounce is measured in

Re: Minimal support for dm814x

On 11 November 2015 at 18:40, Tony Lindgren wrote: > Well we do first try to set the rate using the divider only at least for > drivers/clk/ti/fapll.c used on dm816x. I'm thinking about doing a similar > driver for the dm814x adpll where we have a PLL and separate output clocks

Re: [PATCH] PCI: dra7xx: mark dra7xx_pcie_msi irq as IRQF_NO_THREAD

On 11/06/2015 08:59 PM, Grygorii Strashko wrote: > Hi Sebastian, Hi Grygorii, > - IRQF_NO_THREAD is the first considered option for such kind of issues. > But: Now in LKML there are ~60 occurrences of IRQF_NO_THREAD - most of > them are used by Arch code. And It's only used by 6 drivers

[3.19.y-ckt stable] Patch "clk: ti: fix dual-registration of uart4_ick" has been added to staging queue

This is a note to let you know that I have just added a patch titled clk: ti: fix dual-registration of uart4_ick to the linux-3.19.y-queue branch of the 3.19.y-ckt extended stable tree which can be found at: http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.19.y-queue This

[PATCH 3.19.y-ckt 049/155] clk: ti: fix dual-registration of uart4_ick

3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me know. -- From: Ben Dooks commit 19e79687de22f23bcfb5e79cce3daba20af228d1 upstream. On the OMAP AM3517 platform the uart4_ick gets registered twice, causing any power

Re: [BISECTED] v4.3-rc5: OMAP1 boot hang

On Wed, Nov 11, 2015 at 11:44:44PM +0200, Aaro Koskinen wrote: > Hi, > > Any suggestions how to debug this further? This happens also with v4.3 > final. Is the CPU_SW_DOMAIN_PAN supposed to work with this CPU? > > I tried to disable various drivers (e.g. NAND, USB) and it still > hangs... And it

[PATCH 38/39] ARM: dts: omap5-cm-t54: Use OMAP5_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 37/39] ARM: dts: omap5-board-common: Use OMAP5_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 39/39] ARM: dts: omap5-uevm.dts: Use OMAP5_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 35/39] ARM: dts: omap4-sdp-es23plus: Use OMAP4_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 19/39] ARM: dts: am43x-epos-evm: Use AM4372_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 16/39] ARM: dts: am437x-gp-evm: Use AM4372_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 17/39] ARM: dts: am437x-idk-evm: Use AM4372_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 15/39] ARM: dts: am3517-craneboard: Use OMAP3_CORE1_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 13/39] ARM: dts: am335x-phycore-som: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 14/39] ARM: dts: am335x-wega: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

Re: Minimal support for dm814x

On 12 November 2015 at 18:41, Tony Lindgren wrote: > Does the old TI kernel tree driver correctly handle that? It seems this is how the old TI kernel handles them: http://goo.gl/3I3OEL -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a

[PATCH 31/39] ARM: dts: omap4-panda-a4: Use OMAP4_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 32/39] ARM: dts: omap4-panda-common: Use OMAP4_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 33/39] ARM: dts: omap4-panda-es: Use OMAP4_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 34/39] ARM: dts: omap4-sdp: Use OMAP4_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 36/39] ARM: dts: twl6030: Use OMAP4_IOPAD pinmux macro

Use the pinmux IOPAD macros to define the register as an offset from the padconf physical address instead of the offset from padconf base. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 30/39] ARM: dts: twl4030: Use OMAP3_CORE1_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 28/39] ARM: dts: omap3-n9: Use OMAP3_CORE1_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH] PCI: designware: bail out if host_init failed

There's no reason to continue the initialization such as configure register, scan root bus etc. if customized host_init() failed. This patch tries to check the host_init result, bail out if failed. Signed-off-by: Jisheng Zhang --- drivers/pci/host/pci-dra7xx.c | 4

[PATCH v2 0/5] arm: dts: complete dm816x device tree

In order to fix support for the dm816x platform, add missing bits in the dm816x dtsi and cleanup OCP. The last patch adds support for the omap4-hwspinlock. v2: add ocp hwmod cleanup Neil Armstrong (5): arm: dts: add dm816x missing #mbox-cells arm: dts: add dm816x missing spi DT dma handles

[PATCH v2 1/5] arm: dts: add dm816x missing #mbox-cells

Add missing #mbox-cells for dm816x mbox DT node. Cc: Brian Hutchinson Signed-off-by: Neil Armstrong --- arch/arm/boot/dts/dm816x.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/dm816x.dtsi b/arch/arm/boot/dts/dm816x.dtsi

[PATCH v2 5/5] arm: dts: Add omap4-hwspinlock support in dm816x

Add dm816x DT entries for omap4-hwspinlock support as hwmod spinbox. Cc: Brian Hutchinson Signed-off-by: Neil Armstrong --- arch/arm/boot/dts/dm816x.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/dm816x.dtsi

[PATCH v2 4/5] arm: dts: remove dm816x invalid DT l3_main hwmod

Remove invalid l3_main hwmod entry from dm816x DT ocp node. Cc: Brian Hutchinson Signed-off-by: Neil Armstrong --- arch/arm/boot/dts/dm816x.dtsi | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/arm/boot/dts/dm816x.dtsi

[PATCH v2 3/5] arm: dts: add dm816x pwm property to timers

Adds ti,timer-pwm property to timers 4 to 7 to permit usage of their PWM output fonctionnality via the dmtimer driver. Cc: Brian Hutchinson Signed-off-by: Neil Armstrong --- arch/arm/boot/dts/dm816x.dtsi | 4 1 file changed, 4 insertions(+)

Re: [PATCH v2] regulator: tps65217: remove tps65217.dtsi file

On Tue, Oct 27, 2015 at 01:36:36PM +0100, Heiko Schocher wrote: > remove tps65217.dtsi and adapt all boards, which > used it. > > Signed-off-by: Heiko Schocher > Tested-by: Keerthy > Acked-by: Mark Brown Acked-by: Rob Herring

Re: [PATCH 1/4] arm: omap2+: add missing HWMOD_NO_IDLEST in 81xx hwmod data

On 10/24/2015 12:09 PM, Neil Armstrong wrote: > Hi, > > 2015-10-24 3:21 GMT+02:00 Tony Lindgren : >> >> Hi, >> >> * Neil Armstrong [151022 02:19]: >>> Add missing HWMOD_NO_IDLEST hwmod flag for entries no >>> having omap4 clkctrl values. >> >> Have you

Re: [PATCH v2 2/3] ARM: OMAP2+: remove custom abort handler for t410

Tony, can you please take this patch through the OMAP tree for 4.4? The first patch in this series went in through Russells tree, so the below code now has the possibility to hide a real abort later during boot. Regards, Lucas Am Donnerstag, den 15.10.2015, 12:32 +0200 schrieb Lucas Stach: >

[PATCH v2 2/5] arm: dts: add dm816x missing spi DT dma handles

Add the missing SPI controller DMA handler in the dm816x DT node, only properties for the two channels on four were present. Cc: Brian Hutchinson Signed-off-by: Neil Armstrong --- arch/arm/boot/dts/dm816x.dtsi | 7 +-- 1 file changed, 5

Re: [PATCH] gpio: omap: fix debounce time calculation

On 11/12/2015 08:09 PM, Felipe Balbi wrote: Hi, Grygorii Strashko writes: On 11/12/2015 07:50 PM, Felipe Balbi wrote: According to TRM, debounce is measured in periods of the functional clock of the GPIO IP. This means that What TRM? link pls.

Re: [PATCH] gpio: omap: fix debounce time calculation

Hi, Grygorii Strashko writes: > On 11/12/2015 08:09 PM, Felipe Balbi wrote: >> >> Hi, >> >> Grygorii Strashko writes: >>> On 11/12/2015 07:50 PM, Felipe Balbi wrote: According to TRM, debounce is measured in periods of the

[PATCH 00/39] ARM: dts: Convert OMAP boards to use IOPAD pinmux macros

Hello Tony, This series converts all the remaining OMAP boards that didn't use the IOPAD macros to specify the padconf register addresses. The only board that I left was arch/arm/boot/dts/am335x-boneblack.dts because Andrew already posted a patch for that DTS [0]. I built tested all the DTBs

[PATCH 03/39] ARM: dts: am335x-baltos-ir5221: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Also, use the mux defines instead of magic numbers for the

[PATCH 07/39] ARM: dts: am335x-chilisom: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 06/39] ARM: dts: am335x-chiliboard: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 02/39] ARM: dts: am335x-baltos-ir5221: Remove leftover pinctrl lines

When the Device Tree source file got merged, some commented pinctrl lines were left in the file. These are already defined so seems to be a cleanup that was missed. Delete the unneeded lines from the file. Signed-off-by: Javier Martinez Canillas ---

[PATCH 01/39] pinctrl: Move am4372 and dra7 macros to the the SoC header files

The header file defines a set of macros for different SoCs families that falls under the OMAP sub-arch, that allow to define the padconf register physical address instead of the register offset from the padconf base. But the am43xx and dra7xx SoCs families have their own pinctrl header file so

[PATCH 04/39] ARM: dts: am335x-bone-common: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 05/39] ARM: dts: am335x-bonegreen: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 22/39] ARM: dts: dra72-evm: Use DRA7XX_CORE_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 20/39] ARM: dts: am57xx-beagle-x15: Use DRA7XX_CORE_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 21/39] ARM: dts: dra7-evm: Use DRA7XX_CORE_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 18/39] ARM: dts: am437x-sk-evm: Use AM4372_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 24/39] ARM: dts: omap3-beagle-xm: Use OMAP3_*_IOPAD pinmux macros

Use the pinmux IOPAD macros to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 25/39] ARM: dts: omap3-evm-37xx: Use OMAP3_*_IOPAD pinmux macros

Use the pinmux IOPAD macros to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 23/39] ARM: dts: omap3-beagle: Use OMAP3_*_IOPAD pinmux macros

Use the pinmux IOPAD macros to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 26/39] ARM: dts: omap3-ldp: Use OMAP3_CORE1_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 29/39] ARM: dts: omap3-zoom3: Use OMAP3_*_IOPAD pinmux macros

Use the pinmux IOPAD macros to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 27/39] ARM: dts: omap3-n900: Use OMAP3_CORE1_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 12/39] ARM: dts: am335x-pepper: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 10/39] ARM: dts: am335x-lxm: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 11/39] ARM: dts: am335x-nano: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Signed-off-by: Javier Martinez Canillas

[PATCH 08/39] ARM: dts: am335x-evm: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Also, use the mux defines instead of magic numbers for the

[PATCH 09/39] ARM: dts: am335x-evmsk: Use AM33XX_IOPAD pinmux macro

Use the pinmux IOPAD macro to define the register absolute physical address instead of the offset from the padconf base address. This makes the DTS easier to read since matches the addresses listed in the Technical Reference Manual. Also, use the mux defines instead of magic numbers for the

am35xx memory management issues

Hello everyone, We have am3517 based board and are experiencing sporadic corruption of mm structures. We've had this problem for months now and haven't really got bottom of it. Our board is currently using 3.18.20, but with am3517-evm we've tried pretty much everything between v3.14 and v4.2.

Re: [PATCH v2 0/5] arm: dts: complete dm816x device tree

* Neil Armstrong [151112 06:08]: > In order to fix support for the dm816x platform, add missing bits in > the dm816x dtsi and cleanup OCP. Which ones are needed as fixes for the v4.4-rc kernel? Regards, Tony > The last patch adds support for the omap4-hwspinlock. > >

Re: [PATCH v2 2/3] ARM: OMAP2+: remove custom abort handler for t410

* Lucas Stach [151112 05:33]: > Tony, > > can you please take this patch through the OMAP tree for 4.4? The first > patch in this series went in through Russells tree, so the below code > now has the possibility to hide a real abort later during boot. OK will do thanks.

[PATCH] gpio: omap: fix debounce time calculation

According to TRM, debounce is measured in periods of the functional clock of the GPIO IP. This means that we should divide by the rate of functional clock. Signed-off-by: Felipe Balbi --- drivers/gpio/gpio-omap.c | 24 +--- 1 file changed, 17 insertions(+), 7

[PATCH 1/2] arm: boot: dts: beaglex15: Remove ID GPIO

According to latest schematics [1], this board leaves ID pin floating. It's not connected to anything at all. So let's remove it. [1] https://github.com/beagleboard/beagleboard-x15/blob/master/BeagleBoard-X15_RevA2.pdf Signed-off-by: Felipe Balbi ---

[PATCH 0/2] arm: beaglex15: fix USB Gadget

Hi, with the following patches I can get USB Gadget working with my beagle x15 with today's Linus' tree. regards Felipe Balbi (2): arm: boot: dts: beaglex15: Remove ID GPIO arm: boot: beaglex15: pass correct interrupt arch/arm/boot/dts/am57xx-beagle-x15.dts | 3 +-- 1 file changed, 1

[PATCH 2/2] arm: boot: beaglex15: pass correct interrupt

According to latest schematics [1], GPIO_1/VBUSDET on TPS659038 is tied to AM57x GPIO4_21. We can use that as a VBUS interrupt, instead of relying on PMIC's VBUS interrupts which don't seem to be firing on x15 at all. A follow up patch will add support for using this GPIO-based interrupt

Re: [PATCH 0/2] arm: beaglex15: fix USB Gadget

Hi, Felipe Balbi writes: > Hi, > > with the following patches I can get USB Gadget working > with my beagle x15 with today's Linus' tree. > > regards > > Felipe Balbi (2): > arm: boot: dts: beaglex15: Remove ID GPIO > arm: boot: beaglex15: pass correct interrupt actually, one

[PATCH] extcon: palmas: add support for using VBUSDET output

TPS659038 can remux its GPIO_1 as VBUSDET output, which can be tied to a SoC GPIO and used as a VBUS interrupt. Beagle X15 uses that, in fact, and without it, I could not get USB peripheral working with that board. Signed-off-by: Felipe Balbi --- drivers/extcon/extcon-palmas.c |

Re: [PATCH v4 0/3] ARM: OMAP2+ McASP(3) support for DRA7xx family

* Peter Ujfalusi [15 23:33]: > Hi Tony, > > Changes since v3: > - rebased on mainline's HEAD > - Added Tested-by from Felipe > - Added Acked-by from Paul for the hwmod patches > > Changes since v2: > - DTS patch added which is needed because of the clock handling

[PATCH] arm: omap2: Kconfig: select TWD and global timer on AM43xx devices

Make sure to tell the kernel that AM437x has TWD and global timers. Signed-off-by: Felipe Balbi --- Hi Tony, now that all dependencies are in place, we can finally enable twd and global_timer for AM437x. cheers arch/arm/mach-omap2/Kconfig | 3 +++ 1 file changed, 3

Re: [PATCH] gpio: omap: fix debounce time calculation

On 11/12/2015 07:50 PM, Felipe Balbi wrote: > According to TRM, debounce is measured in periods of > the functional clock of the GPIO IP. This means that What TRM? link pls. http://www.ti.com/lit/ug/spruhl7d/spruhl7d.pdf 28.4.1.24 GPIO_DEBOUNCINGTIME Register (offset = 154h) [reset = 0h] The

Re: [PATCH] gpio: omap: fix debounce time calculation

Hi, Grygorii Strashko writes: > On 11/12/2015 07:50 PM, Felipe Balbi wrote: >> According to TRM, debounce is measured in periods of >> the functional clock of the GPIO IP. This means that > > > What TRM? link pls. > > http://www.ti.com/lit/ug/spruhl7d/spruhl7d.pdf > >

Re: am35xx memory management issues

Hi, * Markku Ahvenjärvi [151112 07:26]: > Hello everyone, > > We have am3517 based board and are experiencing sporadic corruption of mm > structures. We've had this problem for months now and haven't really got > bottom of it. > > Our board is currently using

Re: Minimal support for dm814x

* Matthijs van Duin [151112 01:21]: > On 11 November 2015 at 18:40, Tony Lindgren wrote: > > Well we do first try to set the rate using the divider only at least for > > drivers/clk/ti/fapll.c used on dm816x. I'm thinking about doing a similar > >

[3.16.y-ckt stable] Patch "clk: ti: fix dual-registration of uart4_ick" has been added to staging queue

This is a note to let you know that I have just added a patch titled clk: ti: fix dual-registration of uart4_ick to the linux-3.16.y-queue branch of the 3.16.y-ckt extended stable tree which can be found at: http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.16.y-queue This