Re: DSP Bridge driver DVFS: two Kconfig oddities

Hi Paul, On Tue, May 14, 2013 at 3:28 PM, Paul Bolle pebo...@tiscali.nl wrote: 0) I ran into two Kconfig oddities with the Dynamic Voltage and Frequency Scaling (DVFS) option for the DSP Bridge driver (ie, Kconfig symbol TIDSPBRIDGE_DVFS). 1) That Kconfig symbol depends on OMAP_PM_SRF. But

Re: [PATCH] tidspbridge: Fix compilation

Hi, On Thu, Feb 28, 2013 at 11:51 AM, Pali Rohár pali.ro...@gmail.com wrote: Fix includes and use clk_prepare_enable/clk_disable_unprepare Signed-off-by: Pali Rohár pali.ro...@gmail.com Signed-off-by: Joni Lapilainen joni.lapilai...@gmail.com ---

Re: [PATCH 0/5] staging: tidspbridge: for 3.9

Hi Greg, On Thu, Jan 17, 2013 at 6:47 PM, Greg Kroah-Hartman gre...@linuxfoundation.org wrote: On Thu, Jan 10, 2013 at 03:36:57AM -0600, Omar Ramirez Luna wrote: Patches for staging-next, fixing comments and suggestions provided by Chen Gang. There is an additional scm patch, that removes

Re: [PATCH 0/5] staging: tidspbridge: for 3.9

Hi Tony, On Thu, Jan 17, 2013 at 8:01 PM, Tony Lindgren t...@atomide.com wrote: * Greg Kroah-Hartman gre...@linuxfoundation.org [130117 16:51]: On Thu, Jan 10, 2013 at 03:36:57AM -0600, Omar Ramirez Luna wrote: Patches for staging-next, fixing comments and suggestions provided by Chen Gang

[PATCH 0/5] staging: tidspbridge: for 3.9

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

[PATCH 1/5] staging: tidspbridge: fix potential array out of bounds write

, because the driver expects the NULL ending to be among the 255 char limit. Reported-by: Chen Gang gang.c...@asianux.com Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- drivers/staging/tidspbridge/rmgr/proc.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git

[PATCH 2/5] staging: tidspbridge: fix memory corruption on long string names

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 omar.rami...@copitl.com

[PATCH 3/5] staging: tidspbridge: fix uninitialized variable sym_name

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 gang.c...@asianux.com Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- drivers/staging/tidspbridge/rmgr/nldr.c |6

[PATCH 4/5] staging: tidspbridge: use scm functions to set boot address and mode

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 omar.rami...@copitl.com --- drivers/staging/tidspbridge/core

Re: [PATCH 1/2] staging: tidspbridge: fix breakages due to CM reorganization

On Mon, Jan 7, 2013 at 5:03 PM, Greg Kroah-Hartman gre...@linuxfoundation.org wrote: On Mon, Dec 24, 2012 at 08:10:24AM -0600, Omar Ramirez Luna wrote: 3.8-rc1 introduced changes in the clock management header files, this resulted in compilation breakages for this driver. Define this locally

[PATCH 1/2] staging: tidspbridge: fix breakages due to CM reorganization

: error: 'OMAP3430_CM_AUTOIDLE_PLL' undeclared (first use in this function) drivers/staging/tidspbridge/core/tiomap_io.c:416:13: error: 'OMAP3430_CM_CLKEN_PLL' undeclared (first use in this function) Reported-by: Chen Gang gang.c...@asianux.com Signed-off-by: Omar Ramirez Luna omar.rami

[PATCH 2/2] staging: tidspbridge: use prepare/unprepare on dsp clocks

in the correct order while handling clocks. Code path to enable/disable dsp clocks can still be reached from an atomic context, hence we can't use clk_prepare_enable and clk_disable_unprepare yet. Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- drivers/staging/tidspbridge/core/dsp-clock.c

Re: [PATCH 1/2] ARM: OMAP2+: move mailbox.h out of plat-omap headers

Hi Greg, On 30 October 2012 16:02, Greg Kroah-Hartman gre...@linuxfoundation.org wrote: OK. Greg, do these patches look OK to you to move to live under drivers/mailbox? Um, I don't know, I wasn't paying attention here, sorry. As part of plat-omap code cleanup, I was planning to move

Re: [PATCH 1/2] ARM: OMAP2+: move mailbox.h out of plat-omap headers

Tony, On 29 October 2012 12:52, Tony Lindgren t...@atomide.com wrote: --- /dev/null +++ b/include/linux/platform_data/omap_mailbox.h @@ -0,0 +1,105 @@ This file should only contain pure platform data needed by the core omap code to pass to the mailbox driver. Ok, looking at it closely,

[PATCH 1/6] staging: tidspbridge: request the right irq for mmu

Ramirez Luna omar.rami...@copitl.com --- Intended for 3.7 due to code changes during rc1. .../tidspbridge/include/dspbridge/host_os.h|4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/tidspbridge/include/dspbridge/host_os.h b/drivers/staging

[PATCH 2/6] staging: tidspbridge: drop const from custom mmu implementation

is of type 'const void *' Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- Intended for 3.7 due to code changes during rc1. drivers/staging/tidspbridge/hw/hw_mmu.c | 40 +++ drivers/staging/tidspbridge/hw/hw_mmu.h | 28 +++--- 2 files changed

[PATCH 0/6] staging: tidspbridge fixes for 3.7

writeback addressing modes for __raw_ accessors, so the build system was filled with warnings from the old parameter usage. Omar Ramirez Luna (6): staging: tidspbridge: request the right irq for mmu staging: tidspbridge: drop const from custom mmu implementation staging: tidspbridge: change type

[PATCH 3/6] staging: tidspbridge: change type to __iomem for per and core addresses

from integer without a cast ../io.h:88: note: expected 'volatile void *' but argument is of type 'u32' Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- Intended for 3.7 due to code changes during rc1. .../tidspbridge/include/dspbridge/cfgdefs.h|4 ++-- drivers/staging

[PATCH 4/6] staging: tidspbridge: ioremap dsp sync addr

without a cast ../io.h:88: note: expected 'volatile void *' but argument is of type 'u32' Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- Intended for 3.7 due to code changes during rc1. drivers/staging/tidspbridge/core/tiomap3430.c | 37 + 1 file changed, 26

[PATCH 5/6] staging: tidspbridge: ioremap physical address of the stack segment in shm

Due to data type change, readl can no longer receive a u32. Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- Intended for 3.7 due to code changes during rc1. drivers/staging/tidspbridge/rmgr/node.c | 21 +++-- 1 file changed, 15 insertions(+), 6 deletions(-) diff

[PATCH 6/6] staging: tidspbridge: delete unused mmu functions

From: Omar Ramirez Luna omar.l...@linaro.org This should get rid of warnings of the type: warning: passing argument 1 of '' discards qualifiers from pointer target type note: expected 'void *' but argument is of type 'const void *' Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com

Re: [PATCH 0/6] staging: tidspbridge fixes for 3.7

Hi, On Wed, Oct 24, 2012 at 5:28 PM, Greg Kroah-Hartman gre...@linuxfoundation.org wrote: On Wed, Oct 24, 2012 at 05:09:14PM -0500, Omar Ramirez Luna wrote: With 3.7-rc1 changes: - New irq numbering in OMAP3 broke the driver request for a mmu irq, until this is migrated to the common iommu

Re: [PATCH 1/2] The tidspbridge driver does not compile anymore (Some OMAP34XX CPU definitions are missing). I Added a header file for these definitions.

Hi, On Mon, Sep 24, 2012 at 1:54 PM, selso selso.liber...@gmail.com wrote: From: sli sli@SLI-V420.(none) Signed-off-by: sli sli@SLI-V420.(none) --- drivers/staging/tidspbridge/core/dsp-clock.c |3 ++ drivers/staging/tidspbridge/core/tiomap3430.c |4 ++

[PATCH] staging: tidspbridge: fix uuid strings

by the firmware. E.g.: tidspbridge sees: 24BC8D90-BB45-11D4-B756-006008BDB66F firmware expects: .24BC8D90_BB45_11D4_B756_006008BDB66F Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com CC: Andy Shevchenko andriy.shevche...@linux.intel.com --- drivers/staging/tidspbridge/rmgr/dbdcd.c | 27

[PATCH 0/5] staging: tidspbridge: fix various compilation warnings

This fixes the compilation warnings that have been showing up lately. Omar Ramirez Luna (5): staging: tidspbridge: add pud code staging: tidspbridge: split bridge_io_on_loaded staging: tidspbridge: dynamically allocate ibuf in dload_data staging: tidspbridge: dynamically allocate

[PATCH 1/5] staging: tidspbridge: add pud code

*' but argument is of type 'pmdval_t (*)[2]' While at it, eliminate 'if' nesting to increase readability. Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- drivers/staging/tidspbridge/core/tiomap3430.c | 27 +++- 1 files changed, 17 insertions(+), 10 deletions

[PATCH 2/5] staging: tidspbridge: split bridge_io_on_loaded

Ramirez Luna omar.rami...@copitl.com --- drivers/staging/tidspbridge/core/io_sm.c | 704 +++--- 1 files changed, 343 insertions(+), 361 deletions(-) diff --git a/drivers/staging/tidspbridge/core/io_sm.c b/drivers/staging/tidspbridge/core/io_sm.c index c51f651..480a384

[PATCH 3/5] staging: tidspbridge: dynamically allocate ibuf in dload_data

Dynamically allocate ibuf to silence the following warning: drivers/staging/tidspbridge/dynload/cload.c: In function 'dload_data': drivers/staging/tidspbridge/dynload/cload.c:1337: warning: the frame size of 1216 bytes is larger than 1024 bytes Signed-off-by: Omar Ramirez Luna omar.rami

[PATCH 4/5] staging: tidspbridge: dynamically allocate my_sym_buf in dload_symbols

Dynamically allocate my_sym_buf to silence the following warning: drivers/staging/tidspbridge/dynload/cload.c: In function 'dload_symbols': drivers/staging/tidspbridge/dynload/cload.c:890: warning: the frame size of 1040 bytes is larger than 1024 bytes Signed-off-by: Omar Ramirez Luna

[PATCH 5/5] staging: tidspbridge: check the return value of kstrtol

it was replaced for kstrtol as the former is obsolete now. Signed-off-by: Omar Ramirez Luna omar.rami...@copitl.com --- drivers/staging/tidspbridge/pmgr/dbll.c |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/staging/tidspbridge/pmgr/dbll.c b/drivers/staging

[PATCH] staging: tidspbridge: remove usage of OMAP2_L4_IO_ADDRESS

2012 01:07 Reported-by: Tony Lindgren t...@atomide.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/tiomap3430.c | 20 drivers/staging/tidspbridge/core/wdt.c|8 +++- 2 files changed, 19 insertions(+), 9 deletions

[PATCH 0/2] staging: tidspbridge: detecting wdt from baseimage

seen by IVA_SS at address 0 Omar Ramirez Luna (2): staging: tidspbridge: always compile dsp wdt code staging: tidspbridge: detect wdt3 feature at runtime drivers/staging/tidspbridge/Kconfig| 16 - drivers/staging/tidspbridge/core/tiomap3430.c | 10

[PATCH 1/2] staging: tidspbridge: always compile dsp wdt code

In order to detect it at runtime, we need the code handling wdt clock available at runtime to decide whether to enable or disable based on the baseimage symbols. Default timeout has been set to 5 seconds. Downside is that we will lose the option to set a custom timeout for overflow, but than can

[PATCH 2/2] staging: tidspbridge: detect wdt3 feature at runtime

... That occurs because the dsp tries to access wdt3 registers when the clock for those registers is not enabled. Reported-by: Felipe Contreras felipe.contre...@gmail.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/tiomap3430.c | 10 +++--- 1 files

[RFC PATCH 0/2] staging: tidspbridge: detecting wdt from baseimage

to take (between this and default y for CONFIG_TIDSPBRIDGE_WDT3[1]). [1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg62119.html Omar Ramirez Luna (2): staging: tidspbridge: always compile dsp wdt code staging: tidspbridge: detect wdt3 feature at runtime drivers/staging

[RFC PATCH 1/2] staging: tidspbridge: always compile dsp wdt code

In order to detect it at runtime, we need the code handling wdt clock available at runtime to decide whether to enable or disable based on the baseimage symbols. Default timeout has been set to 5 seconds. Downside is that we will lose the option to set a custom timeout for overflow, but than can

[RFC PATCH 2/2] staging: tidspbridge: detect wdt3 feature at runtime

... That occurs because the dsp tries to access wdt3 registers when the clock for those registers is not enabled. Reported-by: Felipe Contreras felipe.contre...@gmail.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/tiomap3430.c | 10 +++--- 1 files

Re: [PATCH 1/2] staging: tidspbridge: fix bridge_open memory leaks

On Tue, Jan 31, 2012 at 2:17 AM, Dan Carpenter dan.carpen...@oracle.com wrote: On Mon, Jan 30, 2012 at 07:20:17PM -0600, Omar Ramirez Luna wrote: There are two members of pr_ctxt allocated during bridge_open that are never freed resulting in memory leaks, these are stream_id and node_id

[PATCH 0/2] staging: tidspbridge: memory leak fixes

triggered error paths during module removal leaking some memory. When accepted they must be propagated to stable kernel releases. Omar Ramirez Luna (2): staging: tidspbridge: fix bridge_open memory leaks staging: tidspbridge: fix incorrect free to drv_datap drivers/staging/tidspbridge/core

[PATCH 1/2] staging: tidspbridge: fix bridge_open memory leaks

variables could result in memory leaking due to missing handling of failure scenarios. While at it, the indentation changes were introduced to avoid interleaved goto statements inside big if blocks. Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/rmgr/drv_interface.c

[PATCH 2/2] staging: tidspbridge: fix incorrect free to drv_datap

drv_get_first_dev_extension: Failed to retrieve the object handle drv_destroy: Failed to store DRV object mgr_destroy: Failed to store MGR object Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/tiomap3430.c|2 -- drivers/staging/tidspbridge/rmgr

[PATCH] staging: tidspbridge: request dmtimer clocks on init

Given that dm timer framework doesn't support request of clocks by soft | hard irqs because some recent changes, tidspbridge needs to request its clocks on init and enable/disable them on demand. This was first seen on 3.2-rc1. Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers

[PATCH v2] staging: tidspbridge: request dmtimer clocks on init

Given that dm timer framework doesn't support request of clocks by soft | hard irqs because some recent changes, tidspbridge needs to request its clocks on init and enable/disable them on demand. This was first seen on 3.2-rc1. Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers

[PATCH] staging: tidspbridge: include module.h by default

/drv_interface.c:359: error: for each function it appears in.) Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/rmgr/drv_interface.c |4 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/drivers/staging/tidspbridge/rmgr/drv_interface.c b/drivers

[PATCH] staging: tidspbridge: fix compilation on dsp clock functions

Seen on v3.1-rc3, patch: omap: mcbsp: Drop in-driver transfer support bafe2721a0fbd1cc1af04384133684f660f3658e Removed code that now cause tidspbridge to break while compiling. Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/dsp-clock.c |1 - 1

[PATCH v4 1/6] staging: tidspbridge: introduce mapping search based on device address

Create function find_containing_mapping_da to search mapping objects given the dsp va instead of the mpu va, in preparation to delete dmm functions altogether. Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/rmgr/proc.c | 41

[PATCH v4 2/6] staging: tidspbridge: replace custom mmu for omap iommu framework

Guzman Lugo x0095...@ti.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/Kconfig| 10 + drivers/staging/tidspbridge/core/_deh.h|2 + drivers/staging/tidspbridge/core/_tiomap.h | 16 +- drivers/staging/tidspbridge

[PATCH v4 3/6] staging: tidspbridge: mapping support when SG_CHAIN is not defined

...@ti.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/Kconfig|1 + drivers/staging/tidspbridge/core/tiomap3430.c | 94 +++- .../tidspbridge/include/dspbridge/dspdefs.h|3 +- drivers/staging/tidspbridge/rmgr

[PATCH v4 0/6] staging tidspbridge: iommu migration

: OMAP: iovmm: fix SW flags passed by user[2]. [1] http://bit.ly/lUxbRO [2] http://bit.ly/mgSrr8 Fernando Guzman Lugo (3): staging: tidspbridge: remove custom mmu code staging: tidspbridge: remove dmm module staging: tidspbridge: decouple mmu functions from regular code Omar Ramirez Luna

[PATCH v4 5/6] staging: tidspbridge: remove dmm module

if dynamic debug is enabled. Signed-off-by: Fernando Guzman Lugo x0095...@ti.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/Makefile |2 +- drivers/staging/tidspbridge/core/tiomap3430.c |1 - .../staging/tidspbridge/include/dspbridge

[PATCH v4 6/6] staging: tidspbridge: decouple mmu functions from regular code

-off-by: Fernando Guzman Lugo x0095...@ti.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/Makefile |2 +- drivers/staging/tidspbridge/core/_deh.h|3 - drivers/staging/tidspbridge/core/dsp_mmu.c | 396

[GIT PULL] staging: tidspbridge for 2.6.39

staging: tidspbridge: rmgr/node.c code cleanup Laurent Pinchart (1): staging: tidspbridge: Fix atoi to support hexadecimal numbers correctly Omar Ramirez Luna (1): staging: tidspbridge: use the right type for list_is_last Ramos Falcon, Ernesto (1): staging: tidspbridge: remove

[PATCH v2 2/2] staging: tidspbridge: replace mbox callback with notifier_call

-by: Hari Kanigeri h-kanige...@ti.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/io_sm.c |8 +++--- drivers/staging/tidspbridge/core/tiomap3430.c | 10 +--- .../staging/tidspbridge/include/dspbridge/io_sm.h | 21

[no subject]

, Fernando (1): staging: tidspbridge: configure full L1 MMU range Omar Ramirez Luna (1): staging: tidspbridge: replace mbox callback with notifier_call drivers/staging/tidspbridge/core/tiomap3430.c | 15 +++ 1 files changed, 7 insertions(+), 8 deletions(-) Regards, Omar

[PATCH 0/2] staging: tidspbridge for 2.6.38

Set of important changes for 2.6.38, to fix a critical bug (1) and a compile break (2). Guzman Lugo, Fernando (1): staging: tidspbridge: configure full L1 MMU range Omar Ramirez Luna (1): staging: tidspbridge: replace mbox callback with notifier_call drivers/staging/tidspbridge/core

[PATCH 1/2] staging: tidspbridge: configure full L1 MMU range

-by: Felipe Contreras felipe.contre...@nokia.com Signed-off-by: Fernando Guzman Lugo fernando.l...@ti.com Signed-off-by: Felipe Contreras felipe.contre...@nokia.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/tiomap3430.c |5 + 1 files changed, 1

[PATCH 2/2] staging: tidspbridge: replace mbox callback with notifier_call

Lately, mailbox callbacks have been replaced by notifier block call chains, this needs to be changed in the users of mailbox, otherwise compilation will break due to missing parameters. Reported-by: Hari Kanigeri h-kanige...@ti.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers

[PATCH] staging: tidspbridge: replace mbox callback with notifier_call

Lately, mailbox callbacks have been replaced by notifier block call chains, this needs to be changed in the users of mailbox, otherwise compilation will break due to missing parameters. Reported-by: Hari Kanigeri h-kanige...@ti.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com

[GIT PULL] staging: tidspbridge for 2.6.38

correctly Omar Ramirez Luna (1): staging: tidspbridge: use the right type for list_is_last Ramos Falcon, Ernesto (1): staging: tidspbridge: remove code referred by OPT_ZERO_COPY_LOADER Sapiens, Rene (1): staging: tidspbridge: overwrite DSP error codes drivers/staging

[PATCH] staging: tidspbridge: remove file handling functions for loader

$FIRMWARE /sys/$DEVPATH/data; \ echo 0 /sys/$DEVPATH/loading' Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- .../tidspbridge/include/dspbridge/dbldefs.h| 10 -- .../staging/tidspbridge/include/dspbridge/dbll.h |7 ++ .../tidspbridge/include

[PATCH 00/02] staging: tidspbridge: 2.6.37-rcX fixes

Hi Greg, Please consider the following patch set for tidspbridge driver in staging tree, the following has been tested on an omap3430 based board + gst-dsp environment. Many thanks to Felipe Contreras for piling this up, as I'm just propagating his patches. First two patches: 1. omap: dsp:

[PATCH 02/02] staging: tidspbridge: hardcode SCM macros while fix is upstreamed

, but needed until omap_ctrl_set_dsp_boot*() are provided. Signed-off-by: Felipe Contreras felipe.contre...@gmail.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/core/tiomap3430.c | 14 +- 1 files changed, 13 insertions(+), 1 deletions(-) diff --git

[PATCH 01/02] omap: dsp: remove shm from normal memory

: 'MEMBLOCK_REAL_LIMIT' undeclared (first use in this function) Signed-off-by: Felipe Contreras felipe.contre...@gmail.com Acked-by: Tony Lindgren t...@atomide.com Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- arch/arm/plat-omap/devices.c |4 +++- 1 files changed, 3 insertions(+), 1

[PATCH] tidspbridge: bind driver name to device name

Since the device name has changed use the new name to bind the driver to it. Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com --- drivers/staging/tidspbridge/rmgr/drv_interface.c |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/drivers/staging/tidspbridge/rmgr

[PATCH v2 0/6] staging: tidspbridge: header cleanup series

Rebased version of the patches that couldn't be applied. Original set: [1] http://marc.info/?l=linux-kernelm=127897548706686w=2 [2] http://marc.info/?l=linux-kernelm=127982129204138w=2 Fixed unexpected change while replacing IN modifier [3] http://marc.info/?l=linux-kernelm=127972475532227w=2

[PATCH 1/6] staging: tidspbridge: remove GlobalTypes.h

From: Menon, Nishanth n...@ti.com Remove custom globaltypes.h header Signed-off-by: Nishanth Menon n...@ti.com --- drivers/staging/tidspbridge/hw/GlobalTypes.h | 291 -- drivers/staging/tidspbridge/hw/MMURegAcM.h |1 - drivers/staging/tidspbridge/hw/hw_defs.h

[PATCH 2/6] staging: tidspbridge: replace CONST with c standard const

From: Menon, Nishanth n...@ti.com Signed-off-by: Nishanth Menon n...@ti.com --- drivers/staging/tidspbridge/core/chnl_sm.c |4 ++-- drivers/staging/tidspbridge/core/io_sm.c |2 +- drivers/staging/tidspbridge/core/msg_sm.c |2 +-

[PATCH 4/6] staging: tidspbridge: remove OPTIONAL

From: Menon, Nishanth n...@ti.com OPTIONAL modifier makes no sense in linux kernel Signed-off-by: Nishanth Menon n...@ti.com --- drivers/staging/tidspbridge/core/chnl_sm.c |2 +- .../staging/tidspbridge/include/dspbridge/cod.h|2 +-

[PATCH 6/6] staging: tidspbridge: remove dbdefs.h

From: Menon, Nishanth n...@ti.com Remove yet another custom definition header Signed-off-by: Nishanth Menon n...@ti.com --- .../staging/tidspbridge/include/dspbridge/dbdefs.h |1 - .../staging/tidspbridge/include/dspbridge/dbtype.h | 69