[PATCH v02 1/2] 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 v02 2/2] 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

[PATCH v02 0/2] ARM: DTS: am33xx/am437x: Use the new eDMA bindings

Hi, Changes since v1: - Updated to use the non 16bit arrays [1] - send the two patch as a series [1] As it has been discussed earlier: https://www.mail-archive.com/linux-omap@vger.kernel.org/msg122117.html the DT bindings has been changes compared to what we had in 4.4-rc1: the arrays now don't

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

Hi Thierry, On 12/16/2015 05:27 PM, Thierry Reding wrote: > I've applied this with some coding style bikeshedding applied. Also I > think there's a timer leak in the probe function: Indeed, the coding style had some root for ameliorations ! Thanks ! I also missed this timer leak, thanks for the

Re: [PATCH V2] ARM: OMAP2+: LogicPD Torpedo + Wireless: Add Bluetooth

* Adam Ford [151216 13:34]: > Bindings for the WL1283 Bluetooth was removed from the shared transport > driver in commit c0bd1b9e5895 ("Revert ti-st: add device tree support") > Until we havea better binding, we need to use the platform data to > initialize Bluetooth. Yeah I

Re: [PATCH v2 2/3] ARM: dts: DRA72-EVM: Add regulator-allow-bypass property for ldo1 and ldo2

* Keerthy [151213 22:38]: > Add regulator-allow-bypass property for ldo1 and ldo2. Are patches 2 and 3 safe to apply separately already or do we need to wait for the regulator patch to go in first? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH v02 0/2] ARM: DTS: am33xx/am437x: Use the new eDMA bindings

* Peter Ujfalusi [151217 05:33]: > Hi, > > Changes since v1: > - Updated to use the non 16bit arrays [1] > - send the two patch as a series > > [1] > As it has been discussed earlier: > https://www.mail-archive.com/linux-omap@vger.kernel.org/msg122117.html > > the DT

Re: [PATCH] ARM: OMAP2+: LogicPD Torpedo: Add LCD Type 15 Support

* Adam Ford [151216 19:18]: > Add basic support for Logic PD type 15 display for older development kits. > This uses GPIO for the backlight. > > Signed-off-by: Adam Ford Applying into omap-for-v4.5/dt thanks. Tony -- To unsubscribe from this list: send

Re: [PATCH 09/19] ARM: dts: am335x: replace gpio-key,wakeup with wakeup-source property

* Sudeep Holla [151215 08:33]: > > > On 21/10/15 11:10, Sudeep Holla wrote: > >Though the keyboard driver for GPIO buttons(gpio-keys) will continue to > >check for/support the legacy "gpio-key,wakeup" boolean property to > >enable gpio buttons as wakeup source,

Re: [PATCH 2/5] ARM: dts: cm-t335: add support for SBC-T335

* Rob Herring [151213 17:26]: > On Sun, Dec 13, 2015 at 10:55:36AM +0200, Uri Mashiach wrote: > > Add basic support for the SBC-T335. > > > > CompuLab SBC-T335 is a single baseboard computer. > > The SBC-T335 is based on the Texas Instruments Cortex-A8 Sitara AM3354 > > SoC. > >

Re: [PATCH 15/19] ARM: dts: omap: replace legacy *,wakeup property with wakeup-source

* Sudeep Holla [151215 08:37]: > > > On 21/10/15 11:10, Sudeep Holla wrote: > >Though the keyboard and other driver will continue to support the legacy > >"gpio-key,wakeup", "linux,wakeup" boolean property to enable the wakeup > >source, "wakeup-source" is the new standard

Re: [PATCH 0/2] ARM: OMAP1/2+: DO not create omap-pcm-audio device

* Peter Ujfalusi [151211 04:51]: > Hi, > > The ASoC omap-pcm has been converted to be non platform device a long time > ago, > so it is no longer needed to create the device for it since there will be no > driver to be loaded for it. OK, applying into

Re: [PATCH] ARM: OMAP2+: LogicPD Torpedo + Wireless: Revert duplicative DTS entries

* Adam Ford [151216 18:39]: > Revert commit 6f0f6c40b66 ("ARM: dts: Set VAUX1 and VAUX4 on Logic PD > Torpedo") > because it It was already done and it's just a duplicate. See: > commit 2d11961f3e55 ("ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V > respectively") Care to

Re: [PATCH v5 4/5] ARM: dts: DRA7: add entry for qspi mmap region

* Rob Herring [151211 07:10]: > On Fri, Dec 11, 2015 at 09:39:59AM +0530, Vignesh R wrote: > > Add qspi memory mapped region entries for DRA7xx based SoCs. Also, > > update the binding documents for the controller to document this change. > > > > Signed-off-by: Vignesh R

Re: [PATCH v2 0/3] drivers: net: cpsw: Fix bugs in fixed-link PHY DT parsing

From: "David Rivshin (Allworx)" Date: Wed, 16 Dec 2015 23:02:08 -0500 > I have tested on the following hardware configurations: > - (EVMSK) dual emac with two real MDIO-connected phys using RGMII-TXID > - single emac with fixed-link using RGMII > Testing of other

Re: [PATCH] dmaengine: edma: Add probe callback to edma_tptc_driver

On Wed, Dec 16, 2015 at 03:19:05PM +0200, Peter Ujfalusi wrote: > Due to changes in device and platform code drivers w/o probe will fail to > load. This means that the devices for eDMA TPTCs are goign to be without > driver and omap hwmod code will turn them off after the kernel finished >

Re: [PATCH V03 0/5] dmaengine: New 'universal' API for requesting channel

On Mon, Dec 14, 2015 at 10:47:37PM +0200, Peter Ujfalusi wrote: > Hi, > > As it has been discussed in the following thread: > http://www.gossamer-threads.com/lists/linux/kernel/2181487#2181487 > > With this series I have taken a path which would result two new API, which can > be used to convert

Re: [PATCH v5 4/5] ARM: dts: DRA7: add entry for qspi mmap region

On 12/18/2015 12:15 AM, Tony Lindgren wrote: > * Rob Herring [151211 07:10]: >> On Fri, Dec 11, 2015 at 09:39:59AM +0530, Vignesh R wrote: >>> Add qspi memory mapped region entries for DRA7xx based SoCs. Also, >>> update the binding documents for the controller to document this

[PATCH V2] ARM: OMAP2+: LogicPD Torpedo: Revert Duplicative Entries

Revert 6f0f6c40b66 ("ARM: dts: Set VAUX1 and VAUX4 on Logic PD Torpedo") because it It was already done and it's just a duplicate. See: 2d11961f3e55 ("ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V respectively") Signed-off-by: Adam Ford ---

Re: [PATCH V2] ARM: OMAP2+: LogicPD Torpedo: Revert Duplicative Entries

* Adam Ford [151217 16:52]: > Revert 6f0f6c40b66 ("ARM: dts: Set VAUX1 and VAUX4 on Logic PD Torpedo") > because it It was already done and it's just a duplicate. See: > 2d11961f3e55 ("ARM: dts: Set VAUX1 and VAUX4 to 3.0V and 1.8V respectively") > > Signed-off-by: Adam Ford

Re: [PATCH v2 2/3] ARM: dts: DRA72-EVM: Add regulator-allow-bypass property for ldo1 and ldo2

Hi Tony, On Friday 18 December 2015 12:14 AM, Tony Lindgren wrote: * Keerthy [151213 22:38]: Add regulator-allow-bypass property for ldo1 and ldo2. Are patches 2 and 3 safe to apply separately already or do we need to wait for the regulator patch to go in first? Yes they

Re: [PATCH v02 0/2] ARM: DTS: am33xx/am437x: Use the new eDMA bindings

On Thu, Dec 17, 2015 at 09:48:44AM -0800, Tony Lindgren wrote: > * Peter Ujfalusi [151217 05:33]: > > Hi, > > > > Changes since v1: > > - Updated to use the non 16bit arrays [1] > > - send the two patch as a series > > > > [1] > > As it has been discussed earlier: > >