Hi
On Mon, 25 Jan 2010 15:06:44 -0600
Candelaria Villareal, Jorge jorge.candela...@ti.com wrote:
+static int omap_mcpdm_dai_startup(struct snd_pcm_substream
*substream,
+ struct snd_soc_dai *dai)
+{
+ struct snd_soc_pcm_runtime *rtd =
Tony, Kevin,
As discussed on off the list email, below two patches converts all the
omap_globals to
physical address and ioremap the space dynamically. Patches generated against
the latest
2.6.33-rc5+ mainline kernel.
Boot tested on OMAP4430SDP and OMAP3430SDP. I don't have OMAP2 board here
This is a clean-up patch towards dynamic allocation of IO space
instead of using harcoded macros to calculate virtual addresses.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
CC: Kevin Hilman khil...@deeprootsystems.com
CC: Tony Lindgren t...@atomide.com
---
This patch update the sdrc, prcm, tap and control module to
allocate iospace dynamically
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
CC: Kevin Hilman khil...@deeprootsystems.com
CC: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/control.c |6 +-
On Mon, Jan 25, 2010 at 03:06:27PM -0600, Candelaria Villareal, Jorge wrote:
Liam Girdwood wrote:
What does this do and why is it not static ?
It enables and configures offset cancelation for the analog headset path. It
is supposed to be called by the codec driver, so it should'nt be
On Mon, Jan 25, 2010 at 11:06:55PM -0800, David Brownell wrote:
On Monday 14 December 2009, Felipe Balbi wrote:
move twl4030 children to threaded irq.
But nothing in drivers/mfd ... the entry to the whole stack?
Did the threaded IRQ stuff ever get set up so that the top
level IRQ thread
On Mon, 2010-01-25 at 15:06 -0600, Candelaria Villareal, Jorge wrote:
Liam Girdwood wrote:
On Fri, 2010-01-22 at 17:15 -0600, Candelaria Villareal, Jorge wrote:
McPDM is the interface between Phoenix audio codec
and the OMAP4430 processor. It enables data to be transfered
to/from
On Tue, 2010-01-26 at 10:27 +0200, Jarkko Nikula wrote:
Hi
On Mon, 25 Jan 2010 15:06:44 -0600
Candelaria Villareal, Jorge jorge.candela...@ti.com wrote:
+static int omap_mcpdm_dai_startup(struct snd_pcm_substream
*substream,
+ struct snd_soc_dai
On Tue, Jan 26, 2010 at 08:06:55AM +0100, ext David Brownell wrote:
On Monday 14 December 2009, Felipe Balbi wrote:
move twl4030 children to threaded irq.
Felipe Balbi (4):
input: keyboard: twl4030: move to request_threaded_irq
input: misc: twl4030: move to request_threaded_irq
rtc:
On Tue, Jan 26, 2010 at 3:56 AM, Omar Ramirez Luna omar.rami...@ti.com wrote:
From: Hiroshi DOYU hiroshi.d...@nokia.com
Based on the discussion:
http://www.spinics.net/lists/arm-kernel/msg72810.html
HACK: export follow_page() for dspbridge cache operation
This is clearly a hack, so what's
On Tuesday 26 January 2010, Felipe Balbi wrote:
But nothing in drivers/mfd ... the entry to the whole stack?
...
correct, that's still missing. I tried to play with it for a while, but
had to give up due to other musb tasks. So if someone wants to step up
and code that part, I'd be glad
On Friday 11 December 2009, Felipe Balbi wrote:
The notifier will be used to communicate usb events
to other drivers like the charger chip.
Good idea ... but not OTG-specific. It doesn't seem to me
that charging hookups belong in that header at all.
In fact, usb_gadget_vbus_draw() might
On Tue, Jan 26, 2010 at 03:16:20AM -0800, David Brownell wrote:
I'd vote to convert all the USB-to-charger interfaces so
they use notifiers. After fixing the events ... see
comments below. :)
Yes please - it's not just chargers either, this can also be used by
PMICs which do power path
On Tuesday 26 January 2010, Mark Brown wrote:
On Tue, Jan 26, 2010 at 03:16:20AM -0800, David Brownell wrote:
I'd vote to convert all the USB-to-charger interfaces so
they use notifiers. After fixing the events ... see
comments below. :)
Yes please - it's not just chargers either,
Hi,
On Tue, Jan 26, 2010 at 12:16:20PM +0100, ext David Brownell wrote:
On Friday 11 December 2009, Felipe Balbi wrote:
The notifier will be used to communicate usb events
to other drivers like the charger chip.
Good idea ... but not OTG-specific. It doesn't seem to me
thanks
that
On Tue, Jan 26, 2010 at 02:35:21PM +0100, ext David Brownell wrote:
On Tuesday 26 January 2010, Mark Brown wrote:
On Tue, Jan 26, 2010 at 03:16:20AM -0800, David Brownell wrote:
I'd vote to convert all the USB-to-charger interfaces so
they use notifiers. After fixing the events ... see
On Tue, Jan 26, 2010 at 05:35:21AM -0800, David Brownell wrote:
On Tuesday 26 January 2010, Mark Brown wrote:
Yes please - it's not just chargers either, this can also be used by
PMICs which do power path management that includes USB.
Color me confused ... what do you mean by power path?
Hi again,
On Tue, Jan 26, 2010 at 03:10:16PM +0100, Balbi Felipe (Nokia-D/Helsinki) wrote:
On Tue, Jan 26, 2010 at 12:16:20PM +0100, ext David Brownell wrote:
On Friday 11 December 2009, Felipe Balbi wrote:
The notifier will be used to communicate usb events
to other drivers like the charger
Am Dienstag, 26. Januar 2010 15:14:43 schrieb Felipe Balbi:
There are load bursting issues too. All part of the USB spec;
a load that's OK for 1 millisecond might not be OK for 1 second.
if you get a SetConfiguration(config), then you can use that load for as
long as needed, the limitation
On Tue, Jan 26, 2010 at 03:24:49PM +0100, ext Oliver Neukum wrote:
Am Dienstag, 26. Januar 2010 15:14:43 schrieb Felipe Balbi:
There are load bursting issues too. All part of the USB spec;
a load that's OK for 1 millisecond might not be OK for 1 second.
if you get a SetConfiguration(config),
On Tuesday 26 January 2010, Felipe Balbi wrote:
+enum usb_xceiv_events {
Let's keep charger events separate from anything else,
like enter host mode or enter peripheral mode (or
even disconnect). The audiences for any other types
of event would be entirely different.
the idea was to
On Tuesday 26 January 2010, Felipe Balbi wrote:
but when suspended, we have to cut power ASAP. If not enumerated we can
still draw power for a few miliseconds due to dead battery provision.
When suspended, it's OK to draw a small amount of power.
On the order of one milliamp, based on the
On Tuesday 26 January 2010, Felipe Balbi wrote:
Thing is, supplying current is a bit more involved. If the
board can't supply 300 mA, the USB configuration selection
mechanism has to know that, so it never selects peripheral
configurations which require that much current.
but that's done
On Tuesday 26 January 2010, Felipe Balbi wrote:
just remember of another problem which I couldn't solve yet:
if you boot the board with the usb cable already attached, then we miss
the first notification because when the notifier is called, usb
controller driver isn't probed yet.
That's
On Tuesday 26 January 2010, Mark Brown wrote:
Yes please - it's not just chargers either, this can also be used by
PMICs which do power path management that includes USB.
Color me confused ... what do you mean by power path?
In the sort of design I'm talking about there is generally a
Hello,
I've been studying the power management support on the OMAP 35x EVM (Rev
G) and have noticed something which seems inconsistent with the
documentation.
According to the elinux OMAP Power Management wiki page
(http://elinux.org/OMAP_Power_Management) - setting sleep_while_idle
to '1' and
* Santosh Shilimkar santosh.shilim...@ti.com [100126 00:37]:
This patch update the sdrc, prcm, tap and control module to
allocate iospace dynamically
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
CC: Kevin Hilman khil...@deeprootsystems.com
CC: Tony Lindgren t...@atomide.com
On Tue, Jan 26, 2010 at 07:44:46AM -0800, David Brownell wrote:
On Tuesday 26 January 2010, Mark Brown wrote:
In the sort of design I'm talking about there is generally a system
power rail which is generated from the various power sources available
to the system, which might include a
Andrew Murray amur...@mpc-data.co.uk writes:
Hello,
I've been studying the power management support on the OMAP 35x EVM (Rev
G) and have noticed something which seems inconsistent with the
documentation.
According to the elinux OMAP Power Management wiki page
Hi Kevin,
Thanks for the detailed response. I will try to find an un-solved bug to
report next time ;)
Thanks,
Andrew Murray
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: 26 January 2010 16:32
To: Andrew Murray
Cc: linux-omap@vger.kernel.org
Subject:
Attached is a hacked omap_hsmmc.c which works with libertas on my
board (very similar to beagle). This is not intended to be a solution
but points in the direction of the problem. I ripped out the
CONFIG_PM code and turned off all the enable/disable stuff. I also
explicitly turn on the fclk at
Hi,
* Pandita, Vikram vikram.pand...@ti.com [100118 17:24]:
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Tony
Lindgren
Sent: Friday, January 15, 2010 7:35 PM
To: linux-arm-ker...@lists.infradead.org
Cc:
Mark Brown wrote:
On Mon, Jan 25, 2010 at 03:06:27PM -0600, Candelaria
Villareal, Jorge wrote:
Liam Girdwood wrote:
What does this do and why is it not static ?
It enables and configures offset cancelation for the analog
headset path. It is supposed to be called by the codec
On Tue, Jan 26, 2010 at 04:21:28PM +0100, ext David Brownell wrote:
On Tuesday 26 January 2010, Felipe Balbi wrote:
Thing is, supplying current is a bit more involved. If the
board can't supply 300 mA, the USB configuration selection
mechanism has to know that, so it never selects peripheral
Liam Girdwood wrote:
On Mon, 2010-01-25 at 15:06 -0600, Candelaria Villareal, Jorge wrote:
Liam Girdwood wrote:
On Fri, 2010-01-22 at 17:15 -0600, Candelaria Villareal,
Jorge wrote:
McPDM is the interface between Phoenix audio codec
and the OMAP4430 processor. It enables data
The omap_device_[enable|idle|shutdown] functions print a warning
when called from an invalid state. Print the invalid state in
the warning messages. This also uses __func__ to get the function
name.
Also, move the entire print string onto a single line to facilitate
grepping or error messages.
The omap_device struct contains a 'struct platform_device'. Normally,
converting a platform_device pointer to an omap_device pointer
consists of simply doing a container_of(), as is done currently by the
to_omap_device() macro.
However, if this is attempted when using platform_device that has
On Tue, Jan 26, 2010 at 04:07:22PM +0100, ext David Brownell wrote:
On Tuesday 26 January 2010, Felipe Balbi wrote:
+enum usb_xceiv_events {
Let's keep charger events separate from anything else,
like enter host mode or enter peripheral mode (or
even disconnect). The audiences for any other
Hi,
On Tue, Jan 26, 2010 at 08:09:34PM +0100, Balbi Felipe (Nokia-D/Helsinki) wrote:
well, if you have access to twl5031 docs you'd understand what I'm
talking about, the charger detection involves at least 3 blocks on
twl5031 plus musb to enable/disable pullups. The sequence is pretty much
as
Hi,
Here are three patches for review to allow more complicated
DEBUG_LL port handling by adding a tmp register for addruart.
The third patch makes it possible to boot mach-omap2 kernels with
omap2420 (v6) and omap34xx (v7) compiled in.
These are needed for the following omap specific patch
Otherwise more complicated uart configuration won't be possible.
We can use r1 for tmp register for both head.S and debug.S.
NOTE: This patch depends on another patch to add the the \tmp register
into all debug-macro.S files. That can be done with:
$ sed -i -e s/addruart,rx\|addruart,
Done with:
$ sed -i -e s/addruart,rx\|addruart, rx/addruart, rx, tmp/ \
arch/arm/*/include/*/debug-macro.S
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-aaec2000/include/mach/debug-macro.S |2 +-
arch/arm/mach-at91/include/mach/debug-macro.S |2 +-
Otherwise the kernel built with both CPU_V6 and CPU_V7 will not
boot on omap2.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mm/Kconfig |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
index baf6384..4c2e90d 100644
Hi all,
These patches clean up the DEBUG_LL code for mach-omap1 and mach-omap2
and then makes multiboot work for mach-omap2.
Note that these patches currently allow only multiboot for 2420 + 36xx.
Adding 2430 and omap4 needs further work.
Also note that in order to boot multiomap configuration
This way we don't have conflicts with the defines
with compiling in multiple omaps. Set the addresses
for uarts in struct omap_globals for the early serial
init code.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap1/include/mach/debug-macro.S | 16 +++--
Define arch_decomp_setup() the same way as some other
architectures do. Use arch_id to configure the debug uart
based on the machine_is by storing it into the uart
scratchpad register for DEBUG_LL code to use.
Note that to avoid merge conflicts, this patch is using
hardcoded register r1 until tmp
These are no longer needed. Note that zoom boards
should now set their own function in uncompress.h
and debug-macro.S for the external UART.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/plat-omap/Kconfig | 19 ---
1 files changed, 0 insertions(+), 19 deletions(-)
Make get_irqnr_and_base common for mach-omap2 multiboot
Thanks to a tip from Russell King rmk+ker...@arm.linux.org.uk,
this also optimizes the code for non-multiboot configurations by
using get_irqnr_preamble.
Note that this will only work currently for 24xx and 34xx.
Support for 44xx can be
Allows compiling in omap2 and omap3.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Makefile |8
arch/arm/mach-omap2/clock.c | 26 +
arch/arm/mach-omap2/clock.h | 35 +-
Fix dmtimer.c for multi-omap boot. Also remove legacy
clk_enable/disable wrappers that are no longer needed.
Note that the clock handling should be further improved
to make use of the clock aliases.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/plat-omap/dmtimer.c | 90
Fix omap2_map_common_io for multi-omap
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/board-2430sdp.c|2 +
arch/arm/mach-omap2/board-3430sdp.c|2 +
arch/arm/mach-omap2/board-3630sdp.c|2 +
arch/arm/mach-omap2/board-4430sdp.c|
Fix mbox init for multi-omap
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/devices.c | 30 --
1 files changed, 24 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
index 18ad931..935e36c
Convert ARCH_OMAP24XX to ARCH_OMAP2
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Kconfig| 16 +++-
arch/arm/mach-omap2/Makefile |2 +
arch/arm/mach-omap2/clockdomains.h |6 ++-
arch/arm/mach-omap2/io.c
Replace ARCH_OMAP34XX with ARCH_OMAP3
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Kconfig| 37 --
arch/arm/mach-omap2/clockdomains.h |6 +--
arch/arm/mach-omap2/io.c |4 +-
arch/arm/mach-omap2/mcbsp.c
omap: Replace orred CONFIG_ARCH_OMAP2/3/4 with CONFIG_ARCH_OMAP2PLUS
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Kconfig |2 +-
arch/arm/plat-omap/Kconfig|4 ++-
arch/arm/plat-omap/dma.c |3 +-
Otherwise the wrong initcalls can run.
Signed-off-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/clock2xxx.c |2 +-
arch/arm/mach-omap2/clock34xx.c |2 +-
arch/arm/mach-omap2/emu.c |3 +++
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git
Otherwise we'll an error when booting a kernel with both
CONFIG_ARCH_OMAP2 and CONFIG_ARCH_OMAP3 compiled in:
Unhandled fault: imprecise external abort (0xc06) at 0x
...
Note that the same problem may still exist when trying to boot
a kernel with 2420 and 2430 both compiled in. We
Note that booting 2420 depends on another patch posted earlier to not
select CONFIG_CPU_32v6K if CONFIG_ARCH_OMAP2 is selected.
Also note that we cannot add omap2430 in yet because of the different
clock addresses compared to 2420. Also note that we cannot have
CONFIG_CPU_32v6K=y in order to boot
Hello,
With regards to the OMAP2 (or at least the 3530 EVM) -the TRM and
various whitepapers suggest that they are 3 OPP levels available for
VDD2 (L3). However, from looking at the sources (linux-omap-pm / pm
branch) it seems that only 2 OPP levels are supported (@166Mhz and
@83Mhz) and used. I
Andrew Murray had written, on 01/26/2010 02:34 PM, the following:
Hello,
With regards to the OMAP2 (or at least the 3530 EVM) -the TRM and
various whitepapers suggest that they are 3 OPP levels available for
VDD2 (L3). However, from looking at the sources (linux-omap-pm / pm
branch) it seems
Thanks for the pointer to the pm-wip-opp branch - I'm not familiar with
the new opp layer so I'll take a look.
I currently have no need to directly control the VDD2 frequency - though
after browsing the code I was interested to find out if my understanding
was correct or if I was missing
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Andrew Murray
Thanks for the pointer to the pm-wip-opp branch - I'm not familiar with
the new opp layer so I'll take a look.
I currently have no need to directly control the VDD2 frequency - though
Hi,
On 1/23/2010 4:19 AM, Felipe Contreras wrote:
From: Jouni Hoganderjouni.hogan...@nokia.com
Signed-off-by: Jouni Hoganderjouni.hogan...@nokia.com
Signed-off-by: Hiroshi DOYUhiroshi.d...@nokia.com
This patch is missing to export enable_off_mode otherwise it will fail
while linking.
FTR,
Hi,
I have a problem with the USB OTG port on my Beagle Board revision B6 - the OTG
port is the only USB port on that device so it's critical that it works.
Everybody on this list probably knows this hardware, I'll just say that it has
an ARM Cortex-A8 CPU (OMAP3530) with a built-in USB
Andrew Murray amur...@mpc-data.co.uk writes:
[...]
I've noticed that other than using the debugfs there is no way for a
user to configure sleep_when_idle, enable_off_mode,
voltage_off_when_idle. Do you think it would be worthwhile to add
these options to the KConfigs? I'd be happy to make
The OPP sets in the TRM are the one that were characterized and
validated by TI. They provide you the max frequency you can achieve
at a certain voltage.
As soon as the frequency is below the one defined in the OPP, you can
do whatever you want.
Thanks for the clarification - this makes sense
On Tue, Jan 26, 2010 at 4:30 PM, Andreas Hartmetz ahartm...@gmail.com wrote:
Hi,
I have a problem with the USB OTG port on my Beagle Board revision B6 - the
OTG
port is the only USB port on that device so it's critical that it works.
Everybody on this list probably knows this hardware, I'll
Hi Kevin,
For some reason I thought that enable_off_mode, voltage_off_when_idle
and sleep_when_idle are disabled by default - thus the only way to make
use of these features in a production system would be to mount debugfs
and use the controls.
The documentation on the elinux wiki suggests this
Andrew Murray amur...@mpc-data.co.uk writes:
For some reason I thought that enable_off_mode, voltage_off_when_idle
and sleep_when_idle are disabled by default - thus the only way to make
use of these features in a production system would be to mount debugfs
and use the controls.
The
On 1/21/2010 7:40 AM, Ameya Palande wrote:
This patch contains indentation fixes and cleans up various warnings
uncovered with extra warning flags:
- empty if() bodies
- incorrect use of unsigned variables
- bad comparison of pointer value
- pointless check of unsigned value being
x0080...@ti.com wrote:
From: Lesly A M x0080...@ti.com
omap3: pm: Generic TRITON power scripts for OMAP3 based boards
Copying the sleep/wakeup/warm_rest sequence voltsetup_time to a new
twl430 script file, since these changes are specific to the power companion
chip.
This can be used by
Hi,
just FYI, one minor tweak to this patch (updated version below). The file
mach-omap2/clkt3xxx_dpll3m2.c has been renamed to
mach-omap2/clkt34xx_dpll3m2.c to reflect the fact that it is not
available on AM35xx chips.
- Paul
From: Paul Walmsley p...@pwsan.com
Split the DPLL3 M2
It is more logic to initialize services related modules inside
services layer, even if we are planning to remove it.
v2:
- Fixed crefs build issue (patch 2) if enabling debug
Omar Ramirez Luna (5):
DSPBRIDGE: Avoid multiple calls to SERVICES_[Init|Exit]
DSPBRIDGE: remove crefs for
NTFY module should be only initialized by services layer.
Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/dsp/bridge/pmgr/wcd.c |7 +--
1 files changed, 1 insertions(+), 6 deletions(-)
diff --git a/drivers/dsp/bridge/pmgr/wcd.c b/drivers/dsp/bridge/pmgr/wcd.c
index
No point in having a module counter if these are called
only once.
Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/dsp/bridge/services/services.c | 100
1 files changed, 37 insertions(+), 63 deletions(-)
diff --git
MEM module should be only initialized by services layer,
removed reference counter for it.
Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/dsp/bridge/gen/gs.c |8 ++--
drivers/dsp/bridge/pmgr/dbll.c| 15 ++-
drivers/dsp/bridge/rmgr/dbdcd.c |
REG module should be only initialized by services layer.
Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/dsp/bridge/rmgr/dbdcd.c |9 +
1 files changed, 1 insertions(+), 8 deletions(-)
diff --git a/drivers/dsp/bridge/rmgr/dbdcd.c b/drivers/dsp/bridge/rmgr/dbdcd.c
Avoid calling multiple times to SERVICES_[Init|Exit] functions,
these should be called once at probe and exit respectively.
Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com
---
drivers/dsp/bridge/pmgr/wcd.c | 10 ++
1 files changed, 2 insertions(+), 8 deletions(-)
diff --git
On 1/22/2010 9:23 PM, Ramirez Luna, Omar wrote:
From: Andy Shevchenkoext-andriy.shevche...@nokia.com
* Change struct LST_ELEM to struct list_head in whole dsp bridge driver
* Remove useless commentaries
* Minor change in the services/mem.c:
...
struct list_head *last =mMan.lst.head;
On 1/22/2010 9:23 PM, Ramirez Luna, Omar wrote:
From: Andy Shevchenkoext-andriy.shevche...@nokia.com
* Remove LST_Init() and LST_Exit() calls because they are doing nothing except
tracing, Thus, remove tracing as well.
* Remove DBC_* calls. It's internal kernel business whether to have
On 1/22/2010 9:23 PM, Ramirez Luna, Omar wrote:
From: Andy Shevchenkoext-andriy.shevche...@nokia.com
Change LST_Create() to the MEM_Calloc() and INIT_LIST_HEAD() pair in optimal
way.
Use MEM_Free() instead of LST_Delete(). We can use it without checking because
MEM_Free() validates input
On 1/22/2010 9:23 PM, Ramirez Luna, Omar wrote:
From: Andy Shevchenkoext-andriy.shevche...@nokia.com
Including the list.h in some files looks redundant. So, remove those lines.
Signed-off-by: Andy Shevchenkoext-andriy.shevche...@nokia.com
Acked-by: Fernando Guzman Lugo x0095...@ti.com
---
On 1/22/2010 10:44 PM, Ramirez Luna, Omar wrote:
From: Shivananda Hebbarx0heb...@ti.com
This patch removes un-used enum definitions from bridge.
Signed-off-by: Shivananda Hebbarx0heb...@ti.com
---
arch/arm/plat-omap/include/dspbridge/cmmdefs.h |8
On 1/22/2010 10:44 PM, Omar Ramirez Luna wrote:
From: Shivananda Hebbarx0heb...@ti.com
This patch removes unrelated enum constants and replaces it with
the macros
Signed-off-by: Shivananda Hebbarx0heb...@ti.com
---
arch/arm/plat-omap/include/dspbridge/_chnl_sm.h | 11 +--
From: Shivananda Hebbar x0heb...@ti.com
This patch removes the conditional check which can result in
message skip.
Discovered-by: Bhavin Shah bs...@ti.com
Signed-off-by: Shivananda Hebbar x0heb...@ti.com
---
drivers/dsp/bridge/wmd/io_sm.c |5 +
1 files changed, 1 insertions(+), 4
Hi,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Ramirez Luna, Omar
Sent: Tuesday, January 26, 2010 6:57 PM
To: linux-omap
Cc: Ameya Palande; Hiroshi Doyu; Felipe Contreras; Menon, Nishanth; Ramirez
Luna, Omar
Subject:
On 1/26/2010 7:46 PM, Guzman Lugo, Fernando wrote:
Hi,
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Ramirez Luna, Omar
Sent: Tuesday, January 26, 2010 6:57 PM
To: linux-omap
Cc: Ameya Palande; Hiroshi Doyu; Felipe
Hi Tony,
On Tue, 26 Jan 2010, Tony Lindgren wrote:
Otherwise we'll an error when booting a kernel with both
CONFIG_ARCH_OMAP2 and CONFIG_ARCH_OMAP3 compiled in:
Unhandled fault: imprecise external abort (0xc06) at 0x
...
Note that the same problem may still exist when trying to
* Paul Walmsley p...@pwsan.com [100126 18:24]:
Hi Tony,
On Tue, 26 Jan 2010, Tony Lindgren wrote:
Otherwise we'll an error when booting a kernel with both
CONFIG_ARCH_OMAP2 and CONFIG_ARCH_OMAP3 compiled in:
Unhandled fault: imprecise external abort (0xc06) at 0x
...
Convert CONFIG_ARCH_OMAP34XX to CONFIG_ARCH_OMAP3, and
CONFIG_ARCH_OMAP24XX to CONFIG_ARCH_OMAP2, in preparation for Tony's
multi-OMAP patches.
While here, update some copyrights, convert instances of 34xx to
3xxx where applicable, and convert preprocessor directives of the
form
#if
Hi Tony,
The following changes since commit 4f4e65d2484811210a2826fa9d59712c7fcf1b49:
Linus Torvalds (1):
Merge branch 'omap-fixes-for-linus' of
git://git.kernel.org/.../tmlind/linux-omap-2.6
are available in the git repository at:
git://git.pwsan.com/linux-2.6 for_2.6.34_4f4e65_a
-Original Message-
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Tuesday, January 26, 2010 9:16 PM
To: Shilimkar, Santosh
Cc: linux-omap@vger.kernel.org; Kevin Hilman
Subject: Re: [PATCH] OMAP2/3/4: ioremap address space
* Santosh Shilimkar santosh.shilim...@ti.com [100126
snip
void __iomem *omap_ctrl_base_get(void)
diff --git a/arch/arm/mach-omap2/id.c b/arch/arm/mach-omap2/id.c
index a091b53..fb5921b 100644
--- a/arch/arm/mach-omap2/id.c
+++ b/arch/arm/mach-omap2/id.c
@@ -407,7 +407,12 @@ void __init omap2_check_revision(void)
void __init
On Saturday 23 January 2010 01:14:59 ext Candelaria Villareal, Jorge wrote:
From: Misael Lopez Cruz x0052...@ti.com
Allow client drivers to set the data_type (16, 32) and the
sync_mode (element, packet, etc) of the audio dma transferences.
McBSP dai driver configures it for a data type of
94 matches
Mail list logo
