On Fri, Jan 11, 2013 at 11:18:41, Porter, Matt wrote:
> The binding definition is based on the generic DMA controller
> binding.
>
> Signed-off-by: Matt Porter
> ---
> Documentation/devicetree/bindings/dma/ti-edma.txt | 51
> +
> 1 file changed, 51 insertions(+)
> create
On Friday 11 January 2013 10:33 AM, Chen Gang wrote:
> 于 2013年01月10日 18:48, Santosh Shilimkar 写道:
>> 'omap_dma_reserve_channels' when used is suppose to be from command
>> line. Hence the proposed fix in the review is the right one.
>
>ok, thank you for your suggestion.
>
>I will send pat
On Fri, Jan 11, 2013 at 11:18:37, Porter, Matt wrote:
> Move mach-davinci/dma.c to common/edma.c so it can be used
> by OMAP (specifically AM33xx) as well. This just moves the
> private EDMA API and enables it to build on OMAP.
>
> Signed-off-by: Matt Porter
> ---
> arch/arm/Kconfig
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports the DT case of
platforms requiring channel selection from either the OMAP DMA or
the EDMA engine. AM33xx only boots from DT and is the only user
implementing EDMA so in the !DT case we can default to the OMA
Adds AM33XX MMC support for am335x-bone, am335x-evm, and
am335x-evmsk..
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am335x-bone.dts |7 +++
arch/arm/boot/dts/am335x-evm.dts |7 +++
arch/arm/boot/dts/am335x-evmsk.dts |7 +++
arch/arm/boot/dts/am33xx.dtsi | 2
Adds support for parsing the TI EDMA DT data into the required
EDMA private API platform data. Enables runtime PM support to
initialize the EDMA hwmod. Adds AM33XX EMDA crossbar event mux
support.
Signed-off-by: Matt Porter
---
arch/arm/common/edma.c | 314 ++
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 51 +
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/ti-edma.txt
diff --git
Fix build on OMAP, the irqs are undefined on AM33xx.
These error interrupt handlers were hardcoded as disabled
so since they are unused code, simply remove them.
Signed-off-by: Matt Porter
---
arch/arm/common/edma.c | 37 -
1 file changed, 37 deletions(-)
d
Changes since v3:
- Rebased on 3.8-rc3
- No longer an RFC
- Fixed bugs in DT/pdata parsing reported by Vaibhav Bedia
- Restored all the Davinci pdata to const
- Removed max_segs hack in favor of using dma_get_channel_caps()
- Fixed extra parens, __raw
Adds AM33XX EDMA support to the am33xx.dtsi as documented in
Documentation/devicetree/bindings/dma/ti-edma.txt
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dt
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 25 +++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/spi/omap-spi.txt
b/D
Adds a dma_request_slave_channel_compat() wrapper which accepts
both the arguments from dma_request_channel() and
dma_request_slave_channel(). Based on whether the driver is
instantiated via DT, the appropriate channel request call will be
made.
This allows for a much cleaner migration of drivers
The EDMA DMAC has a hardware limitation that prevents supporting
scatter gather lists with any number of segments. The DMA Engine
API reports the maximum number of segments a channel can support
via the optional dma_get_channel_caps() API. If the nr_segs
capability is present, the value is used to
Enable TI EDMA option on OMAP.
Signed-off-by: Matt Porter
---
drivers/dma/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index d4c1218..20ef955 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@ -221,7 +221,7 @@
Adds DMA resources to the AM33XX SPI nodes.
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 278b75d..8fd3648 100644
--- a/arch/arm/boot/dts/am33xx.dt
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports the DT case of
platforms requiring channel selection from either the OMAP DMA or
the EDMA engine. AM33xx only boots from DT and is the only user
implementing EDMA so in the !DT case we can default to the OMA
Move mach-davinci/dma.c to common/edma.c so it can be used
by OMAP (specifically AM33xx) as well. This just moves the
private EDMA API and enables it to build on OMAP.
Signed-off-by: Matt Porter
---
arch/arm/Kconfig |1 +
arch/arm/common/Kconfig
'omap_dma_reserve_channels' when used is suppose to be from command.
so, it alreay has value before 1st call of omap_system_dma_probe.
and it will never be changed again during running (not from ioctl).
but 'dma_lch_count' is zero before 1st call of omap_system_dma_probe.
so it wi
于 2013年01月10日 18:51, Santosh Shilimkar 写道:
> Another thing. please fix the subject line. It should be something like
> below.
>
> ARM: OMAP: Fix the use of uninitialized dma_lch_count
ok, thank you for your suggestion
I will use it as subject for patch v2.
:-)
--
Chen Gang
Asianux Corp
于 2013年01月10日 18:48, Santosh Shilimkar 写道:
> 'omap_dma_reserve_channels' when used is suppose to be from command
> line. Hence the proposed fix in the review is the right one.
ok, thank you for your suggestion.
I will send patch v2, also mark you as Signed-of-by.
:-)
--
Chen Gang
Asianu
On Tue, Jan 08, 2013 at 20:45:10, Shilimkar, Santosh wrote:
> On Monday 31 December 2012 06:37 PM, Vaibhav Bedia wrote:
> > The current OMAP timer code registers two timers -
> > one as clocksource and one as clockevent.
> > AM33XX has only one usable timer in the WKUP domain
> > so one of the time
On Thu, Jan 10, 2013 at 6:05 PM, Laurent Pinchart
wrote:
> On Thursday 10 January 2013 10:16:10 Dave Airlie wrote:
>> On Wed, Jan 9, 2013 at 2:11 PM, Rob Clark wrote:
>> > Updated version of DRM driver for TI LCD Controller. Since the initial
>> > version of the patch, which only supported TFP41
The function is reworked to be more readable and fix wrong computations at two
corner cases:
*It takes advantage of the properties of the N and CTS values to recursively
compute the parameters for the highest audio sample rates.
*Fix an overflow in the computation of CTS that was happening with t
On Thursday 10 January 2013 10:16:10 Dave Airlie wrote:
> On Wed, Jan 9, 2013 at 2:11 PM, Rob Clark wrote:
> > Updated version of DRM driver for TI LCD Controller. Since the initial
> > version of the patch, which only supported TFP410 DVI output, I've added
> > an output driver for LCD panels (f
On Sun, Oct 28, 2012 at 01:47:09PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Move mach-davinci/dma.c to common/edma.c so it can be used
> > by OMAP (specifically AM33xx) as well. This just moves the
> > private EDMA API but does not support OMAP.
> >
> > Signed-off-
On Sun, Oct 28, 2012 at 04:41:24PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds support for the per-EDMA channel event mux. This is required
> > for any peripherals using DMA crossbar mapped events.
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/common/
During the migration to the common clock framework, calls to the
functions omap2xxx_clkt_vps_late_init() and
omap2xxx_clkt_vps_check_bootloader_rates() were not preserved for
OMAP2420 and OMAP2430. This causes the variables "sys_ck_rate" and
"curr_prcm_set" to be uninitialised on boot. On reboot, t
On 15:49-20130110, Matt Porter wrote:
> On Thu, Jan 10, 2013 at 01:46:53PM -0600, Nishanth Menon wrote:
> > On 14:35-20130110, Matt Porter wrote:
> > > On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> > > > On 10/18/2
On Thu, Jan 10, 2013 at 01:46:53PM -0600, Nishanth Menon wrote:
> On 14:35-20130110, Matt Porter wrote:
> > On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> > > On 10/18/2012 6:56 PM, Matt Porter wrote:
> > > > Adds AM33XX SPI support
Compilation fix - leftover from:
commit 998c336d4c7183301ed6a6ca93952f63e3cf694f
Author: Tomi Valkeinen
Date: Wed May 30 13:26:00 2012 +0300
OMAPDSS: remove omap_dss_device's suspend/resume
Cc: stable # v3.7
Signed-off-by: Paolo Pisati
---
drivers/staging/omapdrm/omap_connector.c |
On 19:54-20130110, Paul Walmsley wrote:
>
> Here are some basic OMAP test results for Linux v3.8-rc2.
> Logs and other details at:
>
> http://www.pwsan.com/omap/testlogs/test_v3.8-rc2/20130103093341/
>
> Failing tests: needing local investigation (may be
* Andreas Fenkart [121220 14:15]:
> Without functional clock the omap_hsmmc module can't forward
> SDIO IRQs to the system. This patch reconfigures dat1 line
> as a gpio while the fclk is off. And uses SDIO IRQ detection of
> the module, while fclk is present.
Looks pretty good to me, however I c
On Tue, Oct 30, 2012 at 05:33:40AM +, AnilKumar wrote:
> On Thu, Oct 18, 2012 at 18:56:52, Porter, Matt wrote:
> > Adds AM33XX MMC support for am335x-bone and am335x-evm.
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/boot/dts/am335x-bone.dts |6 ++
> > arch/arm/boot/dts/am3
* Peter Ujfalusi [130109 02:03]:
> Use the future proof TWL_MODULE_PWM module id instead to aim the twl-core
> cleanup planed for 3.9 kernel cycle.
>
> Signed-off-by: Peter Ujfalusi
> ---
> Hi Tony,
>
> can you queue this patch for 3.8 cycle?
> With the second part of my twl-core cleanup series
Here are some basic OMAP test results for Linux v3.8-rc2.
Logs and other details at:
http://www.pwsan.com/omap/testlogs/test_v3.8-rc2/20130103093341/
- Paul
Test summary
Boot to userspace:
Pass ( 9/11): 2420n800, 2430sdp, 3517evm, 3530es3beagle,
3730beag
On 14:35-20130110, Matt Porter wrote:
> On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> > On 10/18/2012 6:56 PM, Matt Porter wrote:
> > > Adds AM33XX SPI support for am335x-bone and am335x-evm.
> > >
> > > Signed-off-by: Matt Porter
>
Hi Arnd, Olof,
Below is a pull request to enable multiplatform support for omap2+.
Note that there's a trivial merge conflict with linux next for
drivers/crypto/omap-sham.c. The solution is to just use the version
of the file in linux next.
Russell, looks like you need to update your omap noconf
On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds AM33XX SPI support for am335x-bone and am335x-evm.
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/boot/dts/am335x-bone.dts | 17 +++
> > arch/arm/boot/dts/am33
On Mon, Oct 29, 2012 at 01:48:46PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > The EDMA DMAC has a hardware limitation that prevents supporting
> > scatter gather lists with any number of segments. Since the EDMA
> > DMA Engine driver sets the maximum segments to 16, w
On Sun, Oct 28, 2012 at 04:46:36PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds AM33XX EDMA support to the am33xx.dtsi as documented in
> > Documentation/devicetree/bindings/dma/ti-edma.txt
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/boot/dts/am33xx.
On Sun, Oct 28, 2012 at 04:33:39PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds support for parsing the TI EDMA DT data into the required
> > EDMA private API platform data.
> >
> > Calls runtime PM API only in the DT case in order to unidle the
> > associated hwm
The edma_slave_config() implementation depends on the
direction field such that it will not properly configure
a slave channel when called without direction set.
This fixes the implementation so that the slave config
is copied as is and prep_slave_sg() handles the
direction dependent handling. spi
Hi Linus,
On 01/10/2013 11:41 AM, Linus Walleij wrote:
> On Thu, Dec 20, 2012 at 10:44 AM, Peter Ujfalusi
> wrote:
>
>> Use more coherent locking in the driver. Use bitfield to store the GPIO
>> direction and if the pin is configured as output store the status also in a
>> bitfiled.
>> In this
From: "Philip, Avinash"
The clock framework has changed and it's now better to invoke
clock_prepare_enable() and clk_disable_unprepare() rather than the
legacy clk_enable() and clk_disable() calls. This patch converts the
pwm-tiehrpwm driver to the new framework.
Signed-off-by: Philip Avinash
-
TI PWM sub modules like ECAP & EHRPWM can enter in low power sleep
state during low power transitions of the platforms (like in AM33XX).
This patch series support low power sleep transition support. This
patch series depend on [1] and [2] and tested for low sleep support
on AM335x-evm for ECAP base
In low power modes of AM33XX platforms, peripherals power is cut off.
This patch supports low power sleep transition support for ECAP driver.
Signed-off-by: Philip Avinash
---
drivers/pwm/pwm-tiecap.c | 44
1 file changed, 44 insertions(+)
diff --g
In low power modes of AM33XX platforms, peripherals power is cut off.
This patch supports low power sleep transition support for EHRPWM
driver.
Signed-off-by: Philip Avinash
---
drivers/pwm/pwm-tiehrpwm.c | 65
1 file changed, 65 insertions(+)
diff
Hi,
On Mon, Dec 24, 2012 at 07:28:33PM +0530, Vivek Gautam wrote:
> DWC3 controller curretly depends on CONFIG_USB and CONFIG_USB_GADGET.
> Some hardware may like to use only host feature on dwc3.
> So, removing the dependency of USB_DWC3 on USB_GADGET
> and further modulating the dwc3 core to ena
Hi,
On Thursday 10 January 2013 03:28 PM, Benoit Cousson wrote:
Hi Kishon,
On 01/10/2013 07:19 AM, kishon wrote:
On Friday 28 December 2012 12:05 AM, Aaro Koskinen wrote:
Hi,
On Thu, Sep 20, 2012 at 05:21:15AM +0200, Benoit Cousson wrote:
On 09/19/2012 11:32 AM, Kishon Vijay Abraham I wrote
On Thursday 10 January 2013 04:18 PM, Santosh Shilimkar wrote:
On Thursday 10 January 2013 03:59 PM, Chen Gang wrote:
dma_lch_count is zero before 1st call of omap_system_dma_probe.
omap_dma_reserve_channels has value before 1st call of
omap_system_dma_probe
when 1st call of omap_syst
On Thursday 10 January 2013 03:59 PM, Chen Gang wrote:
dma_lch_count is zero before 1st call of omap_system_dma_probe.
omap_dma_reserve_channels has value before 1st call of omap_system_dma_probe
when 1st call of omap_system_dma_probe
we need set dma_lch_count before use it for ju
On Thu, Dec 20, 2012 at 10:44 AM, Peter Ujfalusi wrote:
> Use more coherent locking in the driver. Use bitfield to store the GPIO
> direction and if the pin is configured as output store the status also in a
> bitfiled.
> In this way we can just look at these bitfields when we need information
>
dma_lch_count is zero before 1st call of omap_system_dma_probe.
omap_dma_reserve_channels has value before 1st call of omap_system_dma_probe
when 1st call of omap_system_dma_probe
we need set dma_lch_count before use it for judging
or which will be failed for omap_dma_reserve_channe
Hi Kishon,
On 01/10/2013 07:19 AM, kishon wrote:
> On Friday 28 December 2012 12:05 AM, Aaro Koskinen wrote:
>> Hi,
>>
>> On Thu, Sep 20, 2012 at 05:21:15AM +0200, Benoit Cousson wrote:
>>> On 09/19/2012 11:32 AM, Kishon Vijay Abraham I wrote:
This patch series adds dt data to get MUSB workin
There is no way to specify the value of iva_img and since this code
is not being used, remove it.
This analysis resulted from a report by
Chen Gang , mentioning that the existing code
was wrongly specifying the size to be copied.
Signed-off-by: Omar Ramirez Luna
---
.../staging/tidspbridge/incl
On both counts, sym_name could be printed uninitialized, this
is solved by moving the pr_* statement to be triggered if the
value is assigned.
Reported-by: Chen Gang
Signed-off-by: Omar Ramirez Luna
---
drivers/staging/tidspbridge/rmgr/nldr.c |6 --
drivers/staging/tidspbridge/rmgr/node
Instead of ioremapping SCM registers, use the correspondent layer
to write into them.
This allows us to get rid of a layer violation, since the registers
are no longer touched by driver code.
Signed-off-by: Omar Ramirez Luna
---
drivers/staging/tidspbridge/core/tiomap3430.c | 34 +
The value allocated doesn't match the one that is meant to be
stored, resulting in corruption of memory for longer strings
that can't be held in such space.
Fix by allocating the correct byte value for the string meant to
be stored.
Signed-off-by: Omar Ramirez Luna
---
drivers/staging/tidspbrid
The name of the firmware (drv_datap->base_img) could potentially
become equal to 255 valid characters (size of exec_file), this
will result in an out of bounds write, given that the 255 chars
along with a '\0' terminator will be copied into an array of
255 chars.
Produce an error on this cases, be
Patches for staging-next, fixing comments and suggestions provided
by Chen Gang.
There is an additional scm patch, that removes hardcoded defines
related to direct register handling for SCM, it was dependent on
changes that already made it to mainline.
Omar Ramirez Luna (5):
staging: tidspbridg
On Wed, Dec 19, 2012 at 4:26 PM, Tomi Valkeinen wrote:
> On 2012-12-19 14:33, Javier Martinez Canillas wrote:
>> Many OMAP3 based boards such as Beagle, Overo and IGEP use
>> the TFP410 DPI-to-DVI chip. So, it's good to have it built
>> as a module by default on OMAP2+ config.
>
> Also on OMAP4 bo
62 matches
Mail list logo
