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

2015-10-23 Thread Paul Walmsley
On Thu, 15 Oct 2015, 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 Thanks, queued. - Paul -- To unsubscribe from this list: send the line

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Grygorii Strashko
On 10/23/2015 07:48 PM, Felipe Balbi wrote: > > Hi, > > Tony Lindgren writes: >> From: Tony Lindgren >> Date: Fri, 23 Oct 2015 09:03:22 -0700 >> Subject: [PATCH] usb: musb: omap2430: Fix regression caused by driver core >> change >> >> Commit ddef08dd00f5

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Alan Stern
On Fri, 23 Oct 2015, Grygorii Strashko wrote: > Reviewed-by: Grygorii Strashko > > It always fun when DD/PM core is updated to fix some driver/subsystem's > specific PM issue :( > > > > >> --- a/drivers/usb/musb/omap2430.c > >> +++ b/drivers/usb/musb/omap2430.c > >>

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

2015-10-23 Thread Paul Walmsley
On Thu, 15 Oct 2015, 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 The OMAP4 DTS files don't have the ELM address space declared. I'm going

[PATCH 1/5] Make am35x helper function declarations accessible

2015-10-23 Thread Rolf Peukert
To be able to call these four helper functions from the M-USB AM35xx glue code, their declarations need to be moved to a header file in the kernels include hierarchy. Signed-off-by: Rolf Peukert --- arch/arm/mach-omap2/usb.h | 5 -

[PATCH 3/5] Add device tree support for M-USB on AM35xx SOCs

2015-10-23 Thread Rolf Peukert
Add a function that sets up necessary data structures. In older kernels this was done in a board_ file. To support initialization via a DT, this now needs to be included in the probe() function. Also declare a new device 'compatible' name (am35x-musb) to differentiate it from omap3-musb.

[PATCH 0/5] Device tree support for AM35xx M-USB driver

2015-10-23 Thread Rolf Peukert
The M-USB drivers glue code for AM35xx SOCs does not yet support device trees. In legacy kernels, it was left to the respective board_ file to set up some necessary data structures before calling am35x_probe(). To support initialization using a DT, this now needs to be done in am35x.c. These

[PATCH 2/5] Export am35x helper functions

2015-10-23 Thread Rolf Peukert
To be able to call these four helper functions from a M-USB AM35x driver module, their name symbols need to be exported. Signed-off-by: Rolf Peukert --- arch/arm/mach-omap2/omap_phy_internal.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH 4/5] Use new MUSB device name in AM3517 device tree.

2015-10-23 Thread Rolf Peukert
Use new MUSB device name in AM3517 device tree and add name declarations for interface and function clock, so the am35x drivers clk_get() calls can find them. Signed-off-by: Rolf Peukert --- arch/arm/boot/dts/am3517.dtsi | 4 +++- 1 file changed, 3 insertions(+), 1

[PATCH 5/5] Add information about the new DT device name

2015-10-23 Thread Rolf Peukert
Add some information about the new device name to the DT documentation. Signed-off-by: Rolf Peukert --- Documentation/devicetree/bindings/usb/omap-usb.txt | 35 ++ 1 file changed, 35 insertions(+) diff --git

[PATCH] ARM: dts: Change I2C2 and I2C3 to 400KHz for LogicPD Torpedo DM3730 devkit

2015-10-23 Thread Adam Ford
When used with the Logic PD development kit, this makes the I2C buses match the BSP released by Logic PD. --- arch/arm/boot/dts/logicpd-torpedo-som.dtsi | 8 1 file changed, 8 insertions(+) diff --git a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi

Re: [PATCH] ARM: dts: am335x-boneblack: Use pinctrl constants

2015-10-23 Thread Andrew F. Davis
On 10/22/2015 04:23 PM, Tony Lindgren wrote: * Andrew F. Davis [151022 09:21]: Using constants for pinctrl allows better readability and removes redundancy with comments. You should use the include/dt-bindings/pinctrl/omap.h macro AM33XX_IOPAD(pa, val) while at it. Otherwise

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Grygorii Strashko
On 10/23/2015 02:01 AM, Tony Lindgren wrote: * Tony Lindgren [151022 11:03]: * Tony Lindgren [151021 16:44]: Hi all, I noticed a regresssino in v4.3-rc series to day with MUSB gadgets and DMA. Doing a git bisect between v4.2..v4.3-rc1 on it pointed to:

[PATCH] drivers: net: cpsw: use module_platform_driver

2015-10-23 Thread Grygorii Strashko
There is no reasons to probe cpsw from late_initcall level and it's not recommended. Hence, use module_platform_driver() to register and probe cpsw driver from module_init() level. Cc: Tony Lindgren Acked-by: Mugunthan V N Signed-off-by: Grygorii Strashko

[PATCH] ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V respectively

2015-10-23 Thread Adam Ford
The development kit schematic expects VAUX1 to be 3.0V. Most users use the development kit as a reference. The development kit schematic expects VAUX4 to be 1.8V. VAUX4 powers VDDS_CSI2 on processor. If the voltage is too high it could damage the processor. If it's too low, it won't work. ---

Re: [PATCH] drivers: net: cpsw: use module_platform_driver

2015-10-23 Thread David Miller
From: Grygorii Strashko Date: Fri, 23 Oct 2015 14:41:12 +0300 > There is no reasons to probe cpsw from late_initcall level > and it's not recommended. Hence, use module_platform_driver() > to register and probe cpsw driver from module_init() level. > > Cc: Tony

[PATCH] ARM: dts: Add audio support for LogicPD Torpedo DM3730 devkit

2015-10-23 Thread Adam Ford
Use the TWL4030 Codec with mcbsp2 on Torpedo. Signed-off-by: Adam Ford --- arch/arm/boot/dts/logicpd-torpedo-37xx-devkit.dts | 10 ++ arch/arm/boot/dts/logicpd-torpedo-som.dtsi| 13 + 2 files changed, 23 insertions(+) diff --git

OMAP baseline test results for v4.3-rc6

2015-10-23 Thread Paul Walmsley
Here are some basic OMAP test results for Linux v4.3-rc6. Logs and other details at: http://www.pwsan.com/omap/testlogs/test_v4.3-rc6/20151018200945/ Test summary Build: uImage: Pass ( 3/ 3): omap1_defconfig, omap1_defconfig_1510innovator_only,

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Tony Lindgren
* Grygorii Strashko [151023 05:50]: > On 10/23/2015 02:01 AM, Tony Lindgren wrote: > >* Tony Lindgren [151022 11:03]: > >>* Tony Lindgren [151021 16:44]: > >>>Hi all, > >>> > >>>I noticed a regresssino in v4.3-rc series to day with

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Felipe Balbi
Hi, Tony Lindgren writes: > From: Tony Lindgren > Date: Fri, 23 Oct 2015 09:03:22 -0700 > Subject: [PATCH] usb: musb: omap2430: Fix regression caused by driver core > change > > Commit ddef08dd00f5 ("Driver core: wakeup the parent device before trying >

[GIT PULL] ARM: OMAP2+: hwmod cleanup for v4.4

2015-10-23 Thread Paul Walmsley
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Tony The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46: Linux 4.3-rc4 (2015-10-04 16:57:17 +0100) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git

Re: [GIT PULL] omap dts changes for v4.4 merge window, part 2

2015-10-23 Thread Arnd Bergmann
On Tuesday 20 October 2015 12:35:02 Tony Lindgren wrote: > Few more omap dts changes for v4.4 merge window, mostly to fix and clean > up some omap5 issues to allow adding other omap5 boards. Also some other > fixes and clean-up: > > - Fix SDIO WLAN for omap5 that's been broken for a while. As

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Tony Lindgren
* Alan Stern [151023 11:27]: > On Fri, 23 Oct 2015, Grygorii Strashko wrote: > > > Reviewed-by: Grygorii Strashko > > > > It always fun when DD/PM core is updated to fix some driver/subsystem's > > specific PM issue :( > > > > > > > >> ---

Re: [PATCH 5/5] Add information about the new DT device name

2015-10-23 Thread Sergei Shtylyov
Hello. On 10/23/2015 06:57 PM, Rolf Peukert wrote: Add some information about the new device name to the DT documentation. Signed-off-by: Rolf Peukert --- Documentation/devicetree/bindings/usb/omap-usb.txt | 35 ++ 1 file changed, 35 insertions(+)

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Tony Lindgren
* Alan Stern [151023 13:34]: > On Fri, 23 Oct 2015, Tony Lindgren wrote: > > > > Thus the sequence of events should be: > > > > > > Allocate the musb device; > > > Runtime-enable the omap2430 (since it is now safe to do so); > > > Runtime-enable the musb and

Re: MUSB peripheral DMA regression caused by driver core runtime PM change

2015-10-23 Thread Alan Stern
On Fri, 23 Oct 2015, Tony Lindgren wrote: > > Thus the sequence of events should be: > > > > Allocate the musb device; > > Runtime-enable the omap2430 (since it is now safe to do so); > > Runtime-enable the musb and declare it irq_safe (this will > > automatically

Re: [GIT PULL] ARM: OMAP2+: hwmod cleanup for v4.4

2015-10-23 Thread Tony Lindgren
* Paul Walmsley [151023 12:58]: > Hi Tony > > The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46: > > Linux 4.3-rc4 (2015-10-04 16:57:17 +0100) > > are available in the git repository at: > >

Re: [PATCH 2/4] clk: ti816x: Add missing dmtimer clkdev entries

2015-10-23 Thread Tony Lindgren
* Neil Armstrong [151022 02:19]: > Add missing clkdev dmtimer related entries for dm816x. > 32Khz and ext sources were missing. > > Cc: Brian Hutchinson > Signed-off-by: Neil Armstrong Tero should queue this one:

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

2015-10-23 Thread Tony Lindgren
Hi, * Neil Armstrong [151022 02:19]: > Add missing HWMOD_NO_IDLEST hwmod flag for entries no > having omap4 clkctrl values. Have you checked this is the case both in dm814x and dm816x TRM? Also the documentation may not be complete FYI, might be also worth checking the

Re: [PATCH 2/5] Export am35x helper functions

2015-10-23 Thread Tony Lindgren
* Rolf Peukert [151023 08:46]: > To be able to call these four helper functions from a M-USB AM35x driver > module, their name symbols need to be exported. I'd rather get rid of this file completely.. How about just do a minimal drivers/phy driver? Maybe take a look at the

Re: [PATCH] ARM: dts: am335x-boneblack: Use pinctrl constants

2015-10-23 Thread Javier Martinez Canillas
Hello Andrew, On Fri, Oct 23, 2015 at 3:08 PM, Andrew F. Davis wrote: > On 10/22/2015 04:23 PM, Tony Lindgren wrote: >> >> * Andrew F. Davis [151022 09:21]: >>> >>> Using constants for pinctrl allows better readability and removes >>> redundancy with comments. >> >> >>

Re: [PATCH] ARM: dts: am335x-boneblack: Use pinctrl constants

2015-10-23 Thread Andrew F. Davis
On 10/23/2015 09:29 AM, Javier Martinez Canillas wrote: Hello Andrew, On Fri, Oct 23, 2015 at 3:08 PM, Andrew F. Davis wrote: On 10/22/2015 04:23 PM, Tony Lindgren wrote: * Andrew F. Davis [151022 09:21]: Using constants for pinctrl allows better readability and

Re: [PATCH] ARM: dts: am335x-boneblack: Use pinctrl constants

2015-10-23 Thread Javier Martinez Canillas
Hello Andrew, On Fri, Oct 23, 2015 at 4:36 PM, Andrew F. Davis wrote: > On 10/23/2015 09:29 AM, Javier Martinez Canillas wrote: >> >> Hello Andrew, >> >> On Fri, Oct 23, 2015 at 3:08 PM, Andrew F. Davis wrote: >>> >>> On 10/22/2015 04:23 PM, Tony Lindgren wrote:

[PATCH] rtc: ds1307: Fix alarm programming for mcp794xx

2015-10-23 Thread Tero Kristo
mcp794xx alarm registers must be written in BCD format. However, the alarm programming logic neglected this by adding one to the value after bin2bcd conversion has been already done, writing bad values to month register in case the alarm being set is in October. In this case, the alarm month value

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

2015-10-23 Thread Roger Quadros
On 21/10/15 18:20, Tony Lindgren wrote: > * Roger Quadros [151021 01:31]: >> On 19/10/15 10:08, Roger Quadros wrote: >>> On 17/10/15 00:25, Tony Lindgren wrote: * Roger Quadros [151006 04:13]: > > Fine. The updated series is now at > >

Re: [PATCH] clk: ti: drop locking code from mux/divider drivers

2015-10-23 Thread Grygorii Strashko
On 10/01/2015 10:20 PM, Grygorii Strashko wrote: TI's mux and divider clock drivers do not require locking and they do not initialize internal spinlocks. This code was occasionally copy-posted from generic mux/divider drivers. So remove it. Cc: Tony Lindgren Cc: Sekhar Nori