generic
enough to be used in different environments.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Documentation/devicetree/bindings/dma/dma.txt | 28
drivers/dma/dmaengine.c | 7 ++
drivers/dma/of-dma.c | 92
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 57 ++---
1 file changed, 33
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 12 +++-
1 file changed, 11
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific sDMA
request.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers
On 03/28/2015 03:44 AM, Arnd Bergmann wrote:
On Friday 27 March 2015, Peter Ujfalusi wrote:
+Required property:
+- dma-device: phandle of the DMA controller. The router is
modifying
+ the DMA requests for this controller.
This property seems rather specific
On 02/28/2015 06:00 PM, Paul Bolle wrote:
On Tue, 2015-02-24 at 16:21 +0200, Peter Ujfalusi wrote:
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific sDMA
request.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers
Instead of magic numbers in the code, use define for number of logical DMA
channels and DMA requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/omap-dma.c b/drivers/dma
to
be added.
The omap-dma part of changes are based on the dma property name change series:
https://lkml.org/lkml/2015/2/20/182
but the code has fallback so it is working w/o the changes in that series.
Regards,
Peter
---
Peter Ujfalusi (6):
dmaengine: of_dma: Support for DMA routers
dmaengine
generic
enough to be used in different environments.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Documentation/devicetree/bindings/dma/dma.txt | 27
drivers/dma/dmaengine.c | 7 ++
drivers/dma/of-dma.c | 92
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 11 ++-
1 file changed, 10
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 57 ++---
1 file changed, 33
channels with HW request lines will make it
harder to implement MEM_TO_MEM mode for the driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/omap-dma.c b/drivers/dma/omap-dma.c
On 02/24/2015 04:25 PM, Russell King - ARM Linux wrote:
On Tue, Feb 24, 2015 at 04:21:21PM +0200, Peter Ujfalusi wrote:
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests
On 02/24/2015 04:28 PM, Russell King - ARM Linux wrote:
On Tue, Feb 24, 2015 at 04:21:22PM +0200, Peter Ujfalusi wrote:
Do not direct map the virtual channels to sDMA request number. When the
sDMA is behind of a crossbar this direct mapping can cause situations when
certain channel can
On 01/30/2015 02:40 PM, Peter Ujfalusi wrote:
On 01/30/2015 12:37 PM, Pavel Machek wrote:
Hi!
I looked around the diff between 3.18 and 3.19, reverted these, and
audio quality is back to reasonable level.
Actually, reverting 368494093354ac613a80c2e1d77602aa12473cf0 seems
enough.
Any
On 01/30/2015 12:37 PM, Pavel Machek wrote:
Hi!
I looked around the diff between 3.18 and 3.19, reverted these, and
audio quality is back to reasonable level.
Actually, reverting 368494093354ac613a80c2e1d77602aa12473cf0 seems
enough.
Any quick patches to test? Or should we revert so
The sDMA controller is capable of performing memory copy operation. It need
to be configured to software triggered mode and without HW synchronization.
The sDMA can copy data which is aligned to 8, 16 or 32 bits.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 51
On 04/09/2015 12:35 PM, Peter Ujfalusi wrote:
Vinod: is it OK if I send the Documnetation/dmanegine/ update a bit later when
I have finished it?
Changes since v4:
- Comments from Maxime Ripard addressed:
- long line fixed in of-dma.c
- node leaks has been fixed in ti-dma-crossbar
,
resulting in lost serial data.
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com
Signed-off-by: John Ogness john.ogn...@linutronix.de
---
drivers/dma/edma.c |7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/dma/edma.c b/drivers/dma/edma.c
index bf09db7
.
By clearing the completion interrupt for the stopping channel it is
ensured that no completion event will be generated after the stop.
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com
Signed-off-by: John Ogness john.ogn...@linutronix.de
---
arch/arm/common/edma.c |3 +++
1 file changed
it be static?
drivers/clk/ti/clk-dra7-atl.c:170:39: warning: Using plain integer as NULL
pointer
Cc: Peter Ujfalusi peter.ujfal...@ti.com
Cc: Tero Kristo t-kri...@ti.com
Signed-off-by: Stephen Boyd sb...@codeaurora.org
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/clk/ti/clk
On 05/04/2015 08:38 AM, Vinod Koul wrote:
On Thu, Apr 09, 2015 at 12:35:49PM +0300, Peter Ujfalusi wrote:
+int omap_dmaxbar_init(void)
+{
+return platform_driver_register(ti_dma_xbar_driver);
+}
+arch_initcall(omap_dmaxbar_init);
All looks fine except this bit, I think I did point out
On 05/08/2015 06:41 AM, Vinod Koul wrote:
Now as far as this series is concerned, rest of it looks good so I am
willing to merge to if you plan to work on defered probe :) I think its a
fair bargain!
Deal ;)
I'll take care of the OMAP/daVinci drivers for omap-dma and edma.
--
Péter
--
To
On 05/08/2015 06:09 PM, Tony Lindgren wrote:
* Vinod Koul vinod.k...@intel.com [150508 02:04]:
On Fri, May 08, 2015 at 10:05:24AM +0300, Peter Ujfalusi wrote:
On 05/08/2015 06:41 AM, Vinod Koul wrote:
Now as far as this series is concerned, rest of it looks good so I am
willing to merge
On 05/09/2015 02:44 PM, Vinod Koul wrote:
This implementation is not tied to any DMA driver so it is possible to use
the
framework by other vendors, also ACPI version of binding can be easy enough
to
be added.
I have applied all but last change to topic/omap
I can only find 6 patches out
On 04/10/2015 10:40 AM, Maxime Ripard wrote:
On Thu, Apr 09, 2015 at 11:24:58AM +0300, Peter Ujfalusi wrote:
On 04/08/2015 06:42 PM, Maxime Ripard wrote:
---
Documentation/devicetree/bindings/dma/dma.txt | 28 +
drivers/dma/dmaengine.c | 7 +++
drivers/dma
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific sDMA
request.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific request
line of the DMA controller.
Signed-off-by: Peter Ujfalusi peter.ujfal
Instead of magic numbers in the code, use define for number of logical DMA
channels and DMA requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/omap-dma.c b/drivers/dma
the real DMA controller.
This way the router can be transparent for the system while remaining generic
enough to be used in different environments.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Documentation/devicetree/bindings/dma/dma.txt | 28 +
drivers/dma/dmaengine.c
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 57 ++---
1 file changed, 33
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 12 +++-
1 file changed, 11
channels with HW request lines will make it
harder to implement MEM_TO_MEM mode for the driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/dma/omap-dma.c b/drivers/dma/omap
Since the mapping between the hardware request lines and channels has been
removed it no longer make sense to have too many channels.
Set the number of channels to match with the number of logical channels
supported by sDMA.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma
This implementation is not tied to any DMA driver so it is possible to use the
framework by other vendors, also ACPI version of binding can be easy enough to
be added.
Regards,
Peter
---
Peter Ujfalusi (8):
dmaengine: of_dma: Support for DMA routers
Documentation: devicetree: dma: Binding
On 04/09/2015 10:01 PM, Tony Lindgren wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [150409 11:55]:
On 04/09/2015 06:18 PM, Tony Lindgren wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [150409 02:37]:
The sDMA requests are routed through the DMA crossbar and without the
crossbar only
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/dra7.dtsi | 57 ++---
1 file changed, 33
the real DMA controller.
This way the router can be transparent for the system while remaining generic
enough to be used in different environments.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Documentation/devicetree/bindings/dma/dma.txt | 28 +
drivers/dma/dmaengine.c
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific sDMA
request.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers
On 04/08/2015 06:42 PM, Maxime Ripard wrote:
---
Documentation/devicetree/bindings/dma/dma.txt | 28 +
drivers/dma/dmaengine.c | 7 +++
drivers/dma/of-dma.c | 86
+++
include/linux/dmaengine.h
On 04/09/2015 06:18 PM, Tony Lindgren wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [150409 02:37]:
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
I assume this can be merged separately from the driver
The DRA7x has more peripherals with DMA requests than the sDMA can handle:
205 vs 127. All DMA requests are routed through the DMA crossbar, which can
be configured to route selected incoming DMA requests to specific request
line of the DMA controller.
Signed-off-by: Peter Ujfalusi peter.ujfal
+static inline void ti_dma_xbar_write(void __iomem *iomem, int xbar, int val)
+{
+writew_relaxed(val, iomem + (xbar * 2));
Silently casting val (an integer) to a u16 isn't really nice I
guess. At least you could be upfront about it in the prototype.
The value in val is guarantied not
Use the dma-requests property from DT to get the number of DMA requests.
In case of legacy boot or failure to find the property, use the default
127 as number of requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 12 +++-
1 file changed, 11
/2014/3/7/199
This implementation is not tied to any DMA driver so it is possible to use the
framework by other vendors, also ACPI version of binding can be easy enough to
be added.
Regards,
Peter
---
Peter Ujfalusi (8):
dmaengine: of_dma: Support for DMA routers
Documentation: devicetree: dma
channels with HW request lines will make it
harder to implement MEM_TO_MEM mode for the driver.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/dma/omap-dma.c b/drivers/dma/omap
Since the mapping between the hardware request lines and channels has been
removed it no longer make sense to have too many channels.
Set the number of channels to match with the number of logical channels
supported by sDMA.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma
Instead of magic numbers in the code, use define for number of logical DMA
channels and DMA requests.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/omap-dma.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/omap-dma.c b/drivers/dma
: ti-dma-crossbar: Make idr xbar instance-specific
dmaengine: ti-dma-crossbar: Add support for eDMA xbar
Peter Ujfalusi (1):
dmaengine: ti-dma-crossbar: Change the compatible string to
ti,dra7-sdma-crossbar
Documentation/devicetree/bindings/dma/dma.txt | 2 +-
.../devicetree
On 06/05/2015 06:34 PM, Peter Ujfalusi wrote:
Hi,
The ti-dma-crossbar driver in it's current form can work when it is used with
sDMA (omap-dma). On DRA7x class of devices we have both sDMA and eDMA
available.
The DT bindings for sDMA has been done in a way that DMA users need to specify
From: Misael Lopez Cruz misael.lo...@ti.com
eDMA crossbar works exactly the same way as sDMA, but sDMA
requires an offset of 1, while no offset is needed for eDMA.
Signed-off-by: Misael Lopez Cruz misael.lo...@ti.com
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
.../devicetree
with the compatible.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Documentation/devicetree/bindings/dma/dma.txt | 2 +-
Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt | 4 ++--
drivers/dma/ti-dma-crossbar.c | 2 +-
3 files changed, 4 insertions(+), 4
From: Misael Lopez Cruz misael.lo...@ti.com
In preparation for supporting multiple DMA crossbar instances,
make the idr xbar instance specific.
Signed-off-by: Misael Lopez Cruz misael.lo...@ti.com
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/ti-dma-crossbar.c | 9
the offset needed
by the DMA driver.
Regards,
Peter
---
Misael Lopez Cruz (1):
dmaengine: ti-dma-crossbar: Make idr xbar instance-specific
Peter Ujfalusi (1):
dmaengine: ti-dma-crossbar: Add support for eDMA
drivers/dma/ti-dma-crossbar.c | 34 +-
1 file changed, 29
The crossbar for eDMA works exactly the same way as sDMA, but sDMA
requires an offset of 1, while no offset is needed for eDMA.
Based on the patch from Misael Lopez Cruz misael.lo...@ti.com
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Misael Lopez Cruz misael.lo...@ti.com
---
drivers
From: Misael Lopez Cruz misael.lo...@ti.com
In preparation for supporting multiple DMA crossbar instances,
make the idr xbar instance specific.
Signed-off-by: Misael Lopez Cruz misael.lo...@ti.com
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
drivers/dma/ti-dma-crossbar.c | 9
Vinod,
On 06/02/2015 03:55 PM, Vinod Koul wrote:
On Fri, May 29, 2015 at 05:32:50PM +0300, Peter Ujfalusi wrote:
On 05/29/2015 01:18 PM, Vinod Koul wrote:
On Fri, May 29, 2015 at 11:42:27AM +0200, Geert Uytterhoeven wrote:
On Fri, May 29, 2015 at 11:33 AM, Vinod Koul vinod.k...@intel.com
On 06/12/2015 03:58 PM, Vinod Koul wrote:
Sorry this slipped thru
I was away for a week anyways ;)
Thinking about it again, I think we should coverge to two APIs and mark the
legacy depracuated and look to convert folks and phase that out
Currently, w/o this series we have these APIs:
/* to
On 05/26/2015 06:08 PM, Tony Lindgren wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [150526 06:28]:
Switch to use ma_request_slave_channel_compat_reason() to request the DMA
channels. In case of error, return the error code we received including
-EPROBE_DEFER
Signed-off-by: Peter Ujfalusi
Mark,
On 05/26/2015 06:27 PM, Mark Brown wrote:
On Tue, May 26, 2015 at 04:26:06PM +0300, Peter Ujfalusi wrote:
Switch to use ma_request_slave_channel_compat_reason() to request the DMA
channels. Only fall back to pio mode if the error code returned is not
-EPROBE_DEFER, otherwise return
On 05/26/2015 05:44 PM, Greg Kroah-Hartman wrote:
On Tue, May 26, 2015 at 04:25:58PM +0300, Peter Ujfalusi wrote:
Switch to use ma_request_slave_channel_compat_reason() to request the DMA
channels. In case of error, return the error code we received including
-EPROBE_DEFER
I think you typed
On 05/27/2015 01:41 PM, Peter Ujfalusi wrote:
On 05/26/2015 05:44 PM, Greg Kroah-Hartman wrote:
On Tue, May 26, 2015 at 04:25:58PM +0300, Peter Ujfalusi wrote:
Switch to use ma_request_slave_channel_compat_reason() to request the DMA
channels. In case of error, return the error code we
On 05/29/2015 01:18 PM, Vinod Koul wrote:
On Fri, May 29, 2015 at 11:42:27AM +0200, Geert Uytterhoeven wrote:
On Fri, May 29, 2015 at 11:33 AM, Vinod Koul vinod.k...@intel.com wrote:
On Tue, May 26, 2015 at 04:25:57PM +0300, Peter Ujfalusi wrote:
dma_request_slave_channel_compat() 'eats' up
The sDMA requests are routed through the DMA crossbar and without the
crossbar only peripherals using DMA request 0-127 can be used.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Hi Tony,
as you have suggested:
http://permalink.gmane.org/gmane.linux.ports.arm.omap/125999
the DTS
Hi,
On 06/08/2015 04:22 PM, Peter Ujfalusi wrote:
Hi,
Changes since v01:
- Drop change in compatible for the crossbar driver and do the configuration
based on the DT structure.
The ti-dma-crossbar driver in it's current form can work when it is used with
sDMA (omap-dma). On DRA7x
On 07/02/2015 06:56 PM, Vinod Koul wrote:
On Wed, Jul 01, 2015 at 03:41:26PM +0300, Peter Ujfalusi wrote:
Hi,
On 06/08/2015 04:22 PM, Peter Ujfalusi wrote:
Hi,
Changes since v01:
- Drop change in compatible for the crossbar driver and do the configuration
based on the DT structure
GPIO2_1 is used as a mux switch between LCD and HDMI displays. This mux
affects audio routing as well since in LCD mode HDMI audio is not possible
and when HDMI is selected analog audio is not working.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts
Add node for McASP1 along with the needed pinctrl entries.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts | 35 +++
1 file changed, 35 insertions(+)
diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts
b/arch/arm/boot/dts
On 07/02/2015 03:10 PM, Felipe Balbi wrote:
Hi,
On Thu, Jul 02, 2015 at 02:58:04PM +0300, Peter Ujfalusi wrote:
Hi,
There is no reason to use the davinci-evm machine driver's compatible for
audio
support since the setup is simple and the common simple-audio-card can
handle it
just
The board uses McASP1 - tlv320aic3106 for analog audio and has
Headphone out and Line in connectors.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts | 28
1 file changed, 28 insertions(+)
diff --git a/arch/arm/boot/dts
When McASP is not in use the pins can be put to sleep mode to conserve
power.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Tested-by: Felipe Balbi ba...@ti.com
---
arch/arm/boot/dts/am437x-sk-evm.dts | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/arm
The sound support consist only Headset output on the board and can be
handled by simple-audio-card.
Also enable the Line-In route as the board has support for it.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Tested-by: Felipe Balbi ba...@ti.com
---
arch/arm/boot/dts/am437x-sk-evm.dts | 33
The section had two tabs instead of one.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am335x-evm.dts | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
index
The VBAT and DCDC4 regulator is needed for audio support (tlv320aic3111)
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/am43x-epos-evm.dts
b/arch/arm/boot/dts
The section had two tabs instead of one.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am335x-evmsk.dts | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts
b/arch/arm/boot/dts/am335x
boards to use simple card.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/configs/omap2plus_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/configs/omap2plus_defconfig
b/arch/arm/configs/omap2plus_defconfig
index ac521e764d10..b001f7ae67f3 100644
When McASP is not in use the pins can be put to sleep mode to conserve
power.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am335x-evmsk.dts | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am335x-evmsk.dts
b/arch/arm
The sound support consist only Headset output on the board and can be
handled by simple-audio-card
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am335x-evmsk.dts | 30 ++
1 file changed, 22 insertions(+), 8 deletions(-)
diff --git a/arch
Analog audio is using this codec on the board.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/am437x-gp-evm.dts
b/arch/arm/boot/dts/am437x-gp-evm.dts
index
The same regulator is used by other chips on the board. The power path is:
VBAT - TPS63031 - Enable signal is V1_8D regulator - V3_3D.
V3_3D is used by SD slot and tlv320aic3106 codec as well.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts | 6
The sound support consist only Headset output on the board and can be
handled by simple-audio-card
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am437x-sk-evm.dts | 30 ++
1 file changed, 22 insertions(+), 8 deletions(-)
diff --git a/arch
When McASP is not in use the pins can be put to sleep mode to conserve
power.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am335x-evm.dts | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot
Use simple card for audio support on ePOS-EVM.
The audio on the board is: McASP1 - tlv320aic3111 codec.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts | 34 ++
1 file changed, 34 insertions(+)
diff --git a/arch/arm
GPIO5_8 is used as a mux switch between LCD and HDMI displays. This mux
affects audio routing as well since in LCD mode HDMI audio is not possible
and when HDMI is selected analog audio is not working.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am437x-gp-evm.dts
Use mcasp1_pins as name for the pinctrl section needed for McASP1 instead
of the am335x_evm_audio_pins name.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am335x-evm.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/am335x
Analog audio is using this codec on the board.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts | 17 +
1 file changed, 17 insertions(+)
diff --git a/arch/arm/boot/dts/am43x-epos-evm.dts
b/arch/arm/boot/dts/am43x-epos-evm.dts
index
The sound support consist only Headset output on the board and can be
handled by simple-audio-card
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am335x-evm.dts | 35 +--
1 file changed, 25 insertions(+), 10 deletions(-)
diff --git
Add node for McASP1 along with the needed pinctrl entries.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am43x-epos-evm.dts | 35 +++
1 file changed, 35 insertions(+)
diff --git a/arch/arm/boot/dts/am43x-epos-evm.dts
b/arch/arm/boot
On 07/02/2015 03:23 PM, Felipe Balbi wrote:
On Thu, Jul 02, 2015 at 02:58:06PM +0300, Peter Ujfalusi wrote:
The sound support consist only Headset output on the board and can be
handled by simple-audio-card
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Still works fine:
Tested
-evmsk and am335x-evm:
There is no reason to use the davinci-evm machine driver's compatible for audio
support since the setup is simple and the common simple-audio-card can handle it
just fine.
am43xx-epos-evm, am437x-gp-evm:
Add audio support via simple-card
Regards,
Peter
---
Peter Ujfalusi (20
Hi,
There is no reason to use the davinci-evm machine driver's compatible for audio
support since the setup is simple and the common simple-audio-card can handle it
just fine.
Also add McASP1 sleep pin configuration.
Regards,
Peter
---
Peter Ujfalusi (2):
ARM: DTS: am437x-sk-evm: Add sleep pin
When McASP is not in use the pins can be put to sleep mode to conserve
power.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/am437x-sk-evm.dts | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/am437x-sk-evm.dts
b/arch
The driver will not probe without valid DMA channels so no need to check
if they are valid when the module is removed.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Ulf Hansson ulf.hans...@linaro.org
---
drivers/mmc/host/omap_hsmmc.c | 6 ++
1 file changed, 2 insertions(+), 4
of_dma_request_slave_channel should return either pointer for valid
dma_chan or ERR_PTR() error code, NULL is not expected to be returned.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Grant Likely grant.lik...@linaro.org
CC: Rob Herring robh...@kernel.org
---
include/linux/of_dma.h
in
case dma_request_slave_channel_reason() returned with it.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
include/linux/dmaengine.h | 22 ++
1 file changed, 22 insertions(+)
diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
index abf63ceabef9
Switch to use ma_request_slave_channel_compat_reason() to request the DMA
channels. In case of error, return the error code we received including
-EPROBE_DEFER
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Ulf Hansson ulf.hans...@linaro.org
---
drivers/mmc/host/omap_hsmmc.c | 22
Switch to use ma_request_slave_channel_compat_reason() to request the DMA
channels. Only fall back to pio mode if the error code returned is not
-EPROBE_DEFER, otherwise return from the probe with the -EPROBE_DEFER.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Ulf Hansson ulf.hans
deferred by missing regulator so
480b4000.mmc got registered first. In case 2 both deferring because of DMA and
at the end 4809c000.mmc get registered first. So far I have not found a way to
bind mmcblk0/1 to a specific node...
Regards,
Peter
---
Peter Ujfalusi (13):
dmaengine: of_dma: Correct
Switch to use ma_request_slave_channel_compat_reason() to request the DMA
channel. Only fall back to pio mode if the error code returned is not
-EPROBE_DEFER, otherwise return from the probe with the -EPROBE_DEFER.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Laurent Pinchart
801 - 900 of 4568 matches
Mail list logo
