ret should be signed here for the error handling to work.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
diff --git a/drivers/usb/phy/omap-usb2.c b/drivers/usb/phy/omap-usb2.c
index 15ab3d6..d36c282 100644
--- a/drivers/usb/phy/omap-usb2.c
+++ b/drivers/usb/phy/omap-usb2.c
@@ -120,7
On 09/14/2012 06:24 AM, Vinod Koul wrote:
On Thu, 2012-09-13 at 16:37 +0300, Peter Ujfalusi wrote:
Change the parameter list of device_prep_dma_cyclic() so the DMA drivers
can receive the no_wakeup request coming from client drivers.
This feature can be used during audio operation to disable
Hi,
On 09/13/2012 06:27 PM, Lars-Peter Clausen wrote:
On 09/13/2012 03:37 PM, Peter Ujfalusi wrote:
The dmaengine_prep_dma_cyclic() function primarily used by audio for cyclic
transfer required by ALSA.
With this new parameter it is going to be possible to enable the
On 09/13/2012 06:38 PM, Russell King - ARM Linux wrote:
On Thu, Sep 13, 2012 at 05:27:09PM +0200, Lars-Peter Clausen wrote:
Hm... Do you think it would work as well if we implement this by setting the
callback for the descriptor to NULL? If the callback is NULL there is
nothing to at the end
On 09/14/2012 06:26 AM, Vinod Koul wrote:
On Thu, 2012-09-13 at 17:27 +0200, Lars-Peter Clausen wrote:
Hi,
Hm... Do you think it would work as well if we implement this by
setting the
callback for the descriptor to NULL? If the callback is NULL there is
nothing to at the end of a
On 09/03/12 15:36, Sean Young wrote:
On Sun, Sep 02, 2012 at 11:08:20PM +0300, Timo Kokkonen wrote:
On 09/02/12 22:41, Sakari Ailus wrote:
On Sun, Sep 02, 2012 at 06:20:27PM +0300, Timo Kokkonen wrote:
On 09.02 2012 18:06:34, Sakari Ailus wrote:
Heippa,
Timo Kokkonen wrote:
Terve,
On
Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
lis331dlh accelerometer is connected to I2C2 bus. So this patch
change the status of I2C2 node to okay to use I2C2 bus. Also
added all the required platform data to am335x-evm.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
Remove lis3lv02d driver device tree initialization from core driver
and move it to individual drivers. With the current implementation
some pdata parameters are missing if we use lis3lv02d_init_device()
in lis3lv02d_i2c driver.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
Add lis3lv02d device tree initialization code/API to take pdata
from device node. Also remove CONFIG_OF ifdef from the driver,
if CONFIG_OF is not defined then OF APIs returns 0.
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
drivers/misc/lis3lv02d/lis3lv02d_spi.c |8 +---
1 file
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is missing in lis3lv02d_i2c driver.
Also adds platform data for lis331dlh driver to am335x-EVM. These
patches were tested on
Hi Tomi
On Fri, 14 Sep 2012, Tomi Valkeinen wrote:
I've noticed the following stack dump on omap3 and omap4 when the device
idles. It takes some time to happen, but it does happen reliably. I just
boot up the device to my minimal filesystem, and wait. Attached is my
kernel config, and I'm
On 09/14/2012 05:26 AM, Vinod Koul wrote:
On Thu, 2012-09-13 at 17:27 +0200, Lars-Peter Clausen wrote:
Hi,
Hm... Do you think it would work as well if we implement this by
setting the
callback for the descriptor to NULL? If the callback is NULL there is
nothing to at the end of a
On Thursday 13 September 2012, AnilKumar Ch wrote:
Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
lis331dlh accelerometer is connected to I2C2 bus. So this patch
change the status to okay to use I2C2 bus. Also added all the
required platform data to am335x-evm.
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
DSS HW on OMAP4 onwards supports a new pipeline called writeback. Unlike other
pipelines(called overlays in OMAPDSS), writeback takes pixel data from an
overlay output or a overlay manager output and writes it back into a specified
On Fri, 2012-09-14 at 11:27 +0300, Tomi Valkeinen wrote:
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
This series prepares the low level DISPC driver(dispc.c) to configure
writeback
registers. The aim is to reuse most of the code as most of its registers are
like overlay or
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
Scaling calculations for an overlay are done by comparing pixel clock of the
connected overlay manager and the core clock of DISPC. The pixel clock is the
output rate of the scalar. The scalar block needs to provide pixels at this
rate
On Fri, 2012-09-14 at 10:13 +0200, Lars-Peter Clausen wrote:
On 09/14/2012 05:26 AM, Vinod Koul wrote:
On Thu, 2012-09-13 at 17:27 +0200, Lars-Peter Clausen wrote:
Hi,
Hm... Do you think it would work as well if we implement this by
setting the
callback for the descriptor to NULL? If
On Thu, 2012-09-13 at 17:45 +0530, Archit Taneja wrote:
Writeback pipeline receives RGB data from one of the overlays or one of the
overlay managers. If the target color mode is YUV422 or NV12, we need to
convert
the RGB pixels to YUV. The scalar in WB then converts it to the target color
On Friday 14 September 2012 02:23 PM, Tomi Valkeinen wrote:
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
Scaling calculations for an overlay are done by comparing pixel clock of the
connected overlay manager and the core clock of DISPC. The pixel clock is the
output rate of the
Hi Arnd,
Thanks for the review,
On Fri, Sep 14, 2012 at 13:56:06, Arnd Bergmann wrote:
On Thursday 13 September 2012, AnilKumar Ch wrote:
Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
lis331dlh accelerometer is connected to I2C2 bus. So this patch
change the status to
OMAP interconnect drivers are used for the interconnect error handling.
Since they are bus driver, lets move it to newly created drivers/bus.
Cc: Arnd Bergmann a...@arndb.de
Cc: Tony Lindgren t...@atomide.com
Tested-by: Lokesh Vutla lokeshvu...@ti.com
Signed-off-by: Santosh Shilimkar
Hi,
On 09/14/2012 11:50 AM, Vinod Koul wrote:
Well, the idea was that the driver would disable interrupts if there is no
callback to call, since there would be nothing to do in the interrupt
handler anyway. But I guess the flags approach should work fine as well.
Yes we _could_ do that, but
From: Jean Pihet j-pi...@ti.com
Remove the device dependent settings (cpu_is_xxx(), IP clock name)
from the driver code and pass them instead via the platform
data.
This allows a clean separation of the driver code and the platform
code.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
On Fri, 2012-09-14 at 12:28 +0300, Peter Ujfalusi wrote:
Hi,
On 09/14/2012 11:50 AM, Vinod Koul wrote:
Well, the idea was that the driver would disable interrupts if there is no
callback to call, since there would be nothing to do in the interrupt
handler anyway. But I guess the flags
On Thursday 13 September 2012, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
I think we're getting very close now, I only have a few small
On Fri, 2012-09-14 at 14:43 +0530, Archit Taneja wrote:
On Friday 14 September 2012 02:23 PM, Tomi Valkeinen wrote:
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
Scaling calculations for an overlay are done by comparing pixel clock of
the
connected overlay manager and the core
On Fri, Sep 14, 2012 at 12:28:28PM +0300, Peter Ujfalusi wrote:
I'm not sure about which flags should ASoC set for the two case we are going
to have. I think it should be something like this:
unsigned long flags = DMA_CTRL_ACK;
if (!substream-runtime-no_period_wakeup)
flags |=
On Friday 14 September 2012 03:19 PM, Tomi Valkeinen wrote:
On Fri, 2012-09-14 at 14:43 +0530, Archit Taneja wrote:
On Friday 14 September 2012 02:23 PM, Tomi Valkeinen wrote:
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
Scaling calculations for an overlay are done by comparing
On Mon, Sep 03, 2012 at 11:23:22PM +0300, Aaro Koskinen wrote:
Add i2c driver to enable access to devices behind CBUS on Nokia Internet
Tablets.
The patch also adds CBUS I2C configuration for N8x0 which is one of the
users of this driver.
Cc: linux-...@vger.kernel.org
Acked-by: Felipe
On Friday 14 September 2012 01:57 PM, Tomi Valkeinen wrote:
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
DSS HW on OMAP4 onwards supports a new pipeline called writeback. Unlike other
pipelines(called overlays in OMAPDSS), writeback takes pixel data from an
overlay output or a
From: Jean Pihet j-pi...@ti.com
Fix the error handling path in omap_sr_probe to correctly
de-allocate resources in case of problems.
Signed-off-by: Jean Pihet j-pi...@ti.com
---
drivers/power/avs/smartreflex.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git
On Fri, 2012-09-14 at 15:33 +0530, Archit Taneja wrote:
On Friday 14 September 2012 03:19 PM, Tomi Valkeinen wrote:
I see your reasoning. I'm a bit reluctant to add a new clock term to
omapdss. You can't (probably) find it in the TRM. Does the TRM talk
about clocks with regard to WB?
Hi!
On Fri, Sep 14, 2012 at 12:14 PM, jean.pi...@newoldbits.com wrote:
From: Jean Pihet j-pi...@ti.com
Fix the error handling path in omap_sr_probe to correctly
de-allocate resources in case of problems.
Please note that this patch applies on top of 'ARM: OMAP: SmartReflex:
pass device
* Mohammed, Afzal: Wednesday, September 12, 2012 3:20 PM
But some of the tusb async values is less by one. I need
to get it right.
Reason has been identified. It was due to rounding error,
no changes are required in the expressions. Moving
completely to picoseconds resolves the issue.
Can you
On Fri, 14 Sep 2012 12:08:06 +0200, Wolfram Sang wrote:
OK, I found the short paragrahp about CBUS in the I2C spec, so I2C might
be an appropriate place. Still, before deciding if it should rather be
in the core directory, I still have a few questions.
Also, does anybody know of a generic
On Friday 14 September 2012 02:16 PM, Tomi Valkeinen wrote:
On Fri, 2012-09-14 at 11:27 +0300, Tomi Valkeinen wrote:
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
This series prepares the low level DISPC driver(dispc.c) to configure writeback
registers. The aim is to reuse most of
On Friday 14 September 2012, AnilKumar, Chimata wrote:
On Fri, Sep 14, 2012 at 13:56:06, Arnd Bergmann wrote:
On Thursday 13 September 2012, AnilKumar Ch wrote:
Why do you put the reg property here
Here I specified reg property because lis331dlh I2C slave address is 0x18.
On Friday 14 September 2012 02:58 AM, Kevin Hilman wrote:
Felipe Balbi ba...@ti.com writes:
Hi,
On Thu, Sep 13, 2012 at 11:04:42AM -0700, Kevin Hilman wrote:
Kevin Hilman khil...@deeprootsystems.com writes:
Kevin Hilman khil...@deeprootsystems.com writes:
[...]
Sorry to be late to the
On Fri, 2012-09-14 at 15:43 +0530, Archit Taneja wrote:
On Friday 14 September 2012 01:57 PM, Tomi Valkeinen wrote:
I initially kept all of this the same, but I changed my mind at some
point, not totally sure why. Even if we stick to the dispc_ovl_* names,
we would still need to create q
On Fri, 2012-09-14 at 15:54 +0530, Archit Taneja wrote:
On Friday 14 September 2012 02:16 PM, Tomi Valkeinen wrote:
On Fri, 2012-09-14 at 11:27 +0300, Tomi Valkeinen wrote:
On Thu, 2012-09-13 at 17:44 +0530, Archit Taneja wrote:
This series prepares the low level DISPC driver(dispc.c) to
+Daniel
On Fri, Sep 14, 2012 at 15:58:37, Arnd Bergmann wrote:
On Friday 14 September 2012, AnilKumar, Chimata wrote:
On Fri, Sep 14, 2012 at 13:56:06, Arnd Bergmann wrote:
On Thursday 13 September 2012, AnilKumar Ch wrote:
Why do you put the reg property here
Here I specified
Hi Kevin,
On Fri, Sep 14, 2012 at 2:15 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
From: Kevin Hilman khil...@ti.com
On some platforms, bootloaders are known to do some interesting RTC
programming. Without going into the obscurities as to why this may be
the case, suffice it to say
The PHY framework provides a set of API's for the PHY drivers to
create/remove a PHY and the PHY users to obtain a reference to the PHY
using or without using phandle. If the PHY users has to obtain a reference to
the PHY without using phandle, the platform specfic intialization code (say
from
When McBSP is configured in threshold mode we can use sDMA packet mode in
all cases.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/omap-mcbsp.c | 47 -
1 file changed, 17 insertions(+), 30 deletions(-)
diff --git
Original author: Russell King rmk+ker...@arm.linux.org.uk
Switch the omap-pcm to use dmaengine.
Certain features are not supported by after dmaengine conversion:
1. No period wakeup mode
DMA engine has no way to communicate this information through
standard channels.
Signed-off-by: Peter
omap-pcm can figure out the correct dma_type based on the stream's format.
In this way we can get rid of the plat/dma.h include from these drivers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/omap-dmic.c | 2 --
sound/soc/omap/omap-mcbsp.c | 3 ---
Set the dma_data for the stream (snd_soc_dai_set_dma_data) at dai_startup
time so omap-pcm will have access to the needed information regarding to
the DMA channel earlier.
This is needed for the clean dmaengine support.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
When requested (DMA_PREP_INTERRUPT is cleared in flags) disable all DMA
interrupts for the channel. In this mode user space does not expect
periodic reports from kernel about the progress of the audio stream.
PulseAudio for example support this type of mode.
Signed-off-by: Peter Ujfalusi
To help the driver to get the correct memory range to access McPDM
registers.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
Instead of the OMAP DMA data type definition the data_type will be used to
specify the number of bits the DMA word should be configured or 0 in case
when based on the stream's format the omap-pcm can decide the needed DMA
word size.
This feature is needed for the omap-hdmi where the sDMA need to
Get the needed resources in a correct way and avoid using defines for them.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/omap-mcpdm.c | 27 +++
1 file changed, 23 insertions(+), 4 deletions(-)
diff --git a/sound/soc/omap/omap-mcpdm.c
Based on the format of the stream the omap-pcm can decide alone what data
type should be used with by the sDMA.
Keep the possibility for OMAP dai drivers to tell omap-pcm if they want to
use different data type. This is needed for the omap-hdmi for example which
needs 32bit data type even if the
Hello,
Changes since v2:
- As it has been discussed the no_wakeup parameter has been replaced with flags
for the dmaengine APIs
Changes since v1:
- Support for pause/resume for OMAP audio via dmaengine
- dmaengine: support for NO_PERIOD_WAKEUP in cyclic mode
- OMAP to keep supporting
The audio stack used omap_stop_dma/omap_start_dma to pause/resume the DMA.
This method has been used for years on OMAP based products.
We only allow pause/resume when the DMA has been configured in cyclic mode
which is used by the audio stack.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Change the parameter list of device_prep_dma_cyclic() so the DMA drivers
can receive the flags coming from clients.
This feature can be used during audio operation to disable all audio
related interrupts when the DMA_PREP_INTERRUPT is cleared from the flags.
Signed-off-by: Peter Ujfalusi
With this parameter added to dmaengine_prep_dma_cyclic() the API will be in
sync with other dmaengine_prep_*() functions.
The dmaengine_prep_dma_cyclic() function primarily used by audio for cyclic
transfer required by ALSA, we use the from audio to ask dma drivers to
suppress interrupts (if
The omap-pcm platform driver no longer needs this parameter to select
between ELEMENT and PACKET mode. The selection is based on the configured
packet_size.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/omap/omap-dmic.c | 1 -
sound/soc/omap/omap-hdmi.c | 1 -
Since we only have element or packet synchronization we can use the
dma_data-packet_size to select the desired mode:
if packet_size is 0 we use ELEMENT mode
if packet_size is not 0 we use PACKET mode for sDMA synchronization.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
When src_maxburst/dst_maxburst is set to 0 by the users of cyclic DMA
(mostly audio) indicates that we should configure the omap DMA to element
sync mode instead of packet mode.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
CC: Russell King rmk+ker...@arm.linux.org.uk
---
On Fri, Sep 14, 2012 at 12:08:06PM +0200, Wolfram Sang wrote:
On Mon, Sep 03, 2012 at 11:23:22PM +0300, Aaro Koskinen wrote:
Add i2c driver to enable access to devices behind CBUS on Nokia Internet
Tablets.
The patch also adds CBUS I2C configuration for N8x0 which is one of the
users
On 09/14/2012 01:58 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/remove a PHY and the PHY users to obtain a reference to the PHY
using or without using phandle. If the PHY users has to obtain a reference to
the PHY without using
Hi all,
we've designed two beagle board clones (two different layouts) for a customer.
After quite some time without any problems they are now seeing USB problems on
some of the boards. I have so far not been able to reproduce the problem...
The USB port of the OMAP the problems appear on is
Sorry :-( With log now.
-Ursprüngliche Nachricht-
Von: linux-usb-ow...@vger.kernel.org
[mailto:linux-usb-ow...@vger.kernel.org] Im Auftrag von
Maximilian Schwerin
Gesendet: Freitag, 14. September 2012 14:26
An: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
Betreff: USB
Hi,
On Fri, Sep 14, 2012 at 5:58 PM, Marc Kleine-Budde m...@pengutronix.de wrote:
On 09/14/2012 01:58 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/remove a PHY and the PHY users to obtain a reference to the PHY
using or without
Hi,
On Fri, Sep 14, 2012 at 02:57:49PM +0200, Maximilian Schwerin wrote:
Sorry :-( With log now.
-Ursprüngliche Nachricht-
Von: linux-usb-ow...@vger.kernel.org
[mailto:linux-usb-ow...@vger.kernel.org] Im Auftrag von
Maximilian Schwerin
Gesendet: Freitag, 14. September 2012
Hi again,
On Fri, Sep 14, 2012 at 04:07:56PM +0300, Felipe Balbi wrote:
On Fri, Sep 14, 2012 at 02:57:49PM +0200, Maximilian Schwerin wrote:
Sorry :-( With log now.
-Ursprüngliche Nachricht-
Von: linux-usb-ow...@vger.kernel.org
[mailto:linux-usb-ow...@vger.kernel.org] Im
On Fri, Sep 14, 2012 at 02:28:19PM +0200, Marc Kleine-Budde wrote:
On 09/14/2012 01:58 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of API's for the PHY drivers to
create/remove a PHY and the PHY users to obtain a reference to the PHY
using or without using phandle. If
Hi,
-Ursprüngliche Nachricht-
Von: Felipe Balbi [mailto:ba...@ti.com]
Gesendet: Freitag, 14. September 2012 15:08
An: Maximilian Schwerin
Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
Betreff: Re: USB problem on beagleboard clone (PGP: Plain,
Unable to verify
On Fri, Sep 14, 2012 at 03:21:47PM +0200, Maximilian Schwerin wrote:
Hi,
-Ursprüngliche Nachricht-
Von: Felipe Balbi [mailto:ba...@ti.com]
Gesendet: Freitag, 14. September 2012 15:08
An: Maximilian Schwerin
Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
Betreff:
Hi Arnd,
On 09/14/2012 04:43 AM, Arnd Bergmann wrote:
On Thursday 13 September 2012, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
I think
On Friday 14 September 2012, Jon Hunter wrote:
On 09/14/2012 04:43 AM, Arnd Bergmann wrote:
+
+Client drivers should specify the DMA property using a phandle to the
controller
+followed by DMA controller specific data.
+
+Required property:
+- dmas: List of one or
On 09/14/2012 08:32 AM, Arnd Bergmann wrote:
On Friday 14 September 2012, Jon Hunter wrote:
On 09/14/2012 04:43 AM, Arnd Bergmann wrote:
+
+Client drivers should specify the DMA property using a phandle to the
controller
+followed by DMA controller specific data.
+
+Required property:
Shubhrajyoti Datta omaplinuxker...@gmail.com writes:
Hi Kevin,
On Fri, Sep 14, 2012 at 2:15 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
From: Kevin Hilman khil...@ti.com
On some platforms, bootloaders are known to do some interesting RTC
programming. Without going into the
Hello,
On Friday, September 07, 2012 12:55 PM Tomi Valkeinen wrote:
On Fri, 2012-09-07 at 07:55 +0200, Marek Szyprowski wrote:
Hello,
On Wednesday, September 05, 2012 12:09 PM Tomi Valkeinen wrote:
OMAP has a custom video ram allocator, which I'd like to remove and use
the
On OMAP4+ platforms the functional clock for the McPDM IP is suplied by
the twl6040 codec (bit clock on the PDM bus).
This common clock driver for twl6040 will register the mcpdm_fclk clock to
be used by the McPDM driver to make sure that the needed clocks are
available when needed.
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2] to add
some basic device-tree helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
v5: - minor update to binding documentation
- added loop to exhaustively search for a slave channel
Currently slave DMA channels are requested by calling dma_request_channel()
and requires DMA clients to pass various filter parameters to obtain the
appropriate channel.
With device-tree being used by architectures such as arm and the addition of
device-tree helper functions to extract the
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
Aim of DMA helpers
- The purpose of device-tree is to describe the capabilites of the hardware.
Thinking about DMA
On Friday 14 September 2012, Jon Hunter wrote:
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Stephen Warren swar...@nvidia.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Russell King li...@arm.linux.org.uk
Cc: Rob Herring rob.herr...@calxeda.com
Cc:
On Friday 14 September 2012, Jon Hunter wrote:
Currently slave DMA channels are requested by calling dma_request_channel()
and requires DMA clients to pass various filter parameters to obtain the
appropriate channel.
With device-tree being used by architectures such as arm and the addition
On Friday 14 September 2012, AnilKumar, Chimata wrote:
Small question here, in my v2 version I have specified both
the compatible names lis3lv02d and lis331dlh is it fine or
only one is sufficient?
+static struct of_device_id lis3lv02d_i2c_dt_ids[] = {
+ { .compatible = st,lis3lv02d
On Friday 14 September 2012, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is missing in lis3lv02d_i2c driver.
Also adds platform data for lis331dlh
On Thu, Sep 13, 2012 at 1:45 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
From: Kevin Hilman khil...@ti.com
On some platforms, bootloaders are known to do some interesting RTC
programming. Without going into the obscurities as to why this may be
the case, suffice it to say the the
On 09/14/2012 05:18 PM, Jon Hunter :
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
Aim of DMA helpers
- The purpose of device-tree is to describe the
Hi,
On Fri, Sep 14, 2012 at 03:38:56PM +0200, Maximilian Schwerin wrote:
I have never seen that error before on any of the boards
I have. One
question though, if the port is always Host, why are you
using the OTG
subsystem instead of the actual Host Subsystem which has an EHCI
On 09/13/2012 04:00 PM, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
diff --git a/Documentation/devicetree/bindings/dma/dma.txt
On 09/14/2012 11:28 AM, Stephen Warren wrote:
On 09/13/2012 04:00 PM, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
diff --git
On 09/14/2012 10:26 AM, Arnd Bergmann wrote:
On Friday 14 September 2012, Jon Hunter wrote:
Cc: Nicolas Ferre nicolas.fe...@atmel.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Stephen Warren swar...@nvidia.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: Russell King li...@arm.linux.org.uk
On Fri, Sep 14, 2012 at 7:37 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
Shubhrajyoti Datta omaplinuxker...@gmail.com writes:
Hi Kevin,
On Fri, Sep 14, 2012 at 2:15 AM, Kevin Hilman
khil...@deeprootsystems.com wrote:
From: Kevin Hilman khil...@ti.com
On some platforms, bootloaders
* Tony Lindgren t...@atomide.com [120914 08:28]:
The following changes since commit a1e01703bacbadd22eb4aaca0bbba59bcba7d3b3:
Merge tags 'omap-devel-gpmc-fixed-for-v3.7' and
'cleanup-omap-tags-for-v3.7' into cleanup-sparseirq (2012-09-12 18:05:19
-0700)
are available in the git
On Wednesday, September 12, 2012, Paul Walmsley wrote:
Remove some unnecessary plat/ includes that are interfering with multi-subarch
ARM kernels.
Signed-off-by: Paul Walmsley p...@pwsan.com
Cc: Kevin Hilman khil...@ti.com
Cc: Rafael J. Wysocki r...@sisk.pl
Acked-by: Kevin Hilman
On Fri, 14 Sep 2012 08:33:42 -0700
Steve Sakoman st...@sakoman.com wrote:
Tested-by: Steve Sakoman st...@sakoman.com
Thanks.
Given the tested-by's that are rolling in, I will assume that people
are hitting this problem in 3.5 and perhaps earlier kernels, so I
scheduled the fix for 3.6, with a
On Fri, Sep 14, 2012 at 12:20 PM, Andrew Morton
a...@linux-foundation.org wrote:
Given the tested-by's that are rolling in, I will assume that people
are hitting this problem in 3.5 and perhaps earlier kernels, so I
scheduled the fix for 3.6, with a -stable backport.
Yes, I just checked an
On Fri, 14 Sep 2012 15:31:36 +
Arnd Bergmann a...@arndb.de wrote:
On Friday 14 September 2012, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual drivers, with the
current implementation some pdata is
On Friday 14 September 2012, Andrew Morton wrote:
On Fri, 14 Sep 2012 15:31:36 +
Arnd Bergmann a...@arndb.de wrote:
On Friday 14 September 2012, AnilKumar Ch wrote:
Adds device tree support to lis3lv02d_i2c driver. Along with this
DT init is moved from core driver to individual
Hi all,
I apologise for sending out so many updates in quick succession before everyone
has had chance to review, however, I will be out of office next week and I know
that several people have been waiting for this. Normally, I would not send out
a series and disappear for a week, but Arnd agreed
Currently slave DMA channels are requested by calling dma_request_channel()
and requires DMA clients to pass various filter parameters to obtain the
appropriate channel.
With device-tree being used by architectures such as arm and the addition of
device-tree helper functions to extract the
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
Aim of DMA helpers
- The purpose of device-tree is to describe the capabilites of the hardware.
Thinking about DMA
On 09/14/2012 04:41 PM, Jon Hunter wrote:
This is based upon the work by Benoit Cousson [1] and Nicolas Ferre [2]
to add some basic helpers to retrieve a DMA controller device_node and the
DMA request/channel information.
The binding looks good to me now, so,
Reviewed-by: Stephen Warren
On Fri, Sep 14, 2012 at 05:41:56PM -0500, Jon Hunter wrote:
3. Supporting legacy devices not using DMA Engine
These devices present a problem, as there may not be a uniform way to
easily
support them with regard to device tree. Ideally, these should be migrated
to DMA engine.
1 - 100 of 102 matches
Mail list logo
