Hi,
These patches(against -next tree) introduce a device driver under
drivers/misc for enabling one face detection IP[1] which is
integrated inside OMAP4 SoC currently, and have some OMAP4
platform dependent changes to make the module workable on OMAP4 SoC.
For verification purpose, I write one
From: Ming Lei ming@canonical.com
Signed-off-by: Ming Lei ming@canonical.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 81
1 files changed, 81 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
From: Ming Lei ming@canonical.com
Signed-off-by: Ming Lei ming@canonical.com
---
arch/arm/mach-omap2/devices.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
index
From: Ming Lei ming@canonical.com
One face detection IP[1] is integared inside OMAP4 SoC, so
introduce this driver to make face detection function work
on OMAP4 SoC.
This driver is platform independent, so in theory can
be used to drive same IP module on other platforms.
[1], ch9 of OMAP4
From: Ming Lei tom.leim...@gmail.com
CC arch/arm/mach-omap2/cpuidle34xx.o
arch/arm/mach-omap2/cpuidle34xx.c: In function 'omap3_enter_idle':
arch/arm/mach-omap2/cpuidle34xx.c:117:2: error: implicit declaration of
function 'omap_irq_pending'
make[1]: *** [arch/arm/mach-omap2/cpuidle34xx.o]
From: Ming Lei tom.leim...@gmail.com
Fix the failure below:
CC drivers/iommu/omap-iommu-debug.o
drivers/iommu/omap-iommu-debug.c:416:20: error: expected declaration
specifiers or '...' before string constant
drivers/iommu/omap-iommu-debug.c:416:1: warning: data definition has no
type or
From: Ming Lei tom.leim...@gmail.com
The patch fixes the compile failure:
CC arch/arm/mach-omap2/cpuidle34xx.o
arch/arm/mach-omap2/cpuidle34xx.c:317:12: error: 'THIS_MODULE'
undeclared here (not in a function)
make[1]: *** [arch/arm/mach-omap2/cpuidle34xx.o] Error 1
make: ***
From: Ming Lei tom.leim...@gmail.com
This patch selects ARM_AMBA if OMAP3_EMU is defined because
OC_ETM depends on ARM_AMBA, so fix the link failure[1].
[1],
arch/arm/kernel/built-in.o: In function `etm_remove':
/home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:609: undefined
reference to
From: Ming Lei tom.leim...@gmail.com
The patch fixes the build failure:
drivers/mfd/omap-usb-host.c:1034:1: warning: data definition has no type
or storage class
drivers/mfd/omap-usb-host.c:1034:1: warning: type defaults to 'int' in
declaration of 'EXPORT_SYMBOL_GPL'
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the clock_*
trace point, based on the ideas below:
- the cpu_id which is passed to trace point is always the current
cpu
- the current cpu info has been included into the trace result already
- smp_processor_id()
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the power_domain_target
trace point, based on the ideas below:
- the cpu_id which is passed to trace point is always the current
cpu
- the current cpu info has been included into the trace result
already
-
From: Ming Lei tom.leim...@gmail.com
This patch removes the 'cpu_id' parameter of the cpu_idle
trace point, based on the ideas below:
- the cpu_id which is passed to trace point is always the current
cpu
- the current cpu info has been included into the trace result
already
-
From: Ming Lei tom.leim...@gmail.com
Obviously it is mistake for CPU_HAS_PMU to depend on
(!ARCH_OMAP3 || OMAP3_EMU).
No mattery it is omap3 or not, we can build pmu.o into
kernel safely. In fact, arm-v7 of omap3 has pmu inside
also.
So fix it that we can build pmu into kernel to support perf
From: Ming Lei tom.leim...@gmail.com
This patch supports pmu irq routed from CTI, so
make pmu/perf working on OMAP4.
The idea is from Woodruff Richard in the disscussion
about Oprofile on Pandaboard / Omap4 on pandabo...@googlegroups.com.
Acked-by: Jean Pihet j-pi...@ti.com
Acked-by: Tony
From: Ming Lei tom.leim...@gmail.com
This patch supports pmu irq routed from CTI, so
make pmu/perf working on OMAP4.
The idea is from Woodruff Richard in the disscussion
about Oprofile on Pandaboard / Omap4 on pandabo...@googlegroups.com.
Cc: Santosh Shilimkar santosh.shilim...@ti.com
Cc:
From: Ming Lei tom.leim...@gmail.com
This patch supports pmu irq routed from CTI, so
make pmu/perf working on OMAP4.
The idea is from Woodruff Richard in the disscussion
about Oprofile on Pandaboard / Omap4 on pandabo...@googlegroups.com.
Cc: Woodruff Richard r-woodru...@ti.com
Cc: Tony
From: Ming Lei tom.leim...@gmail.com
This patch supports pmu irq routed from CTI, so
make pmu/perf working on OMAP4.
The idea is from Woodruff Richard in the disscussion
Oprofile on Pandaboard / Omap4 of pandabo...@googlegroups.com.
Cc: Woodruff Richard r-woodru...@ti.com
Cc: Tony Lindgren
From: Ming Lei tom.leim...@gmail.com
This patch supports pmu irq routed from CTI, so
make pmu/perf working on OMAP4.
The idea is from Woodruff Richard in the disscussion
Oprofile on Pandaboard / Omap4 of pandabo...@googlegroups.com.
Cc: Woodruff Richard r-woodru...@ti.com
Cc: Tony Lindgren
From: Ming Lei tom.leim...@gmail.com
Panda uses both twl6030 otg phy(vbus, id) and internal
phy(data lines, DP/DM), so removes usb_nop_xceiv_register to make
twl6030 otg driver working since current otg code only supports
one global transceiver. Otherwise, musb doesn't work without
the remove.
From: Ming Lei tom.leim...@gmail.com
Panda uses twl6030 otg phy instead of internal phy,
so removes usb_nop_xceiv_register to make musb working.
Cc: Felipe Balbi ba...@ti.com
Signed-off-by: Ming Lei tom.leim...@gmail.com
---
arch/arm/mach-omap2/board-omap4panda.c |2 --
1 files changed, 0
From: Ming Lei tom.leim...@gmail.com
Obviously we should only initialize musb once.
Signed-off-by: Ming Lei tom.leim...@gmail.com
---
arch/arm/mach-omap2/board-omap4panda.c |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
From: Ming Lei tom.leim...@gmail.com
The instance of omap_mmc_platform_data is alwasy passed to
mmc omap host driver from board, so remove ifdef in omap_mmc_platform_data
defination to simplify handling it in mmc omap host driver.
The patch fixes the compile error below:
This patch set fixes two kinds of musb-gadget bug:
-fix kernel panic if using out ep with FIFO_TXRX style
-make double buffer mode usable, fix infinate hangs and buffer
corrupt bug when using double buffer mode to do data transfer;
now we can use musb double
From: Ming Lei tom.leim...@gmail.com
For shared fifo hw endpoint(with FIFO_TXRX style), only ep_in
field of musb_hw_ep is intialized in musb_g_init_endpoints, and
ep_out is not initialized, but musb_g_rx and rxstate may access
ep_out field of musb_hw_ep by the method below:
musb_ep =
From: Ming Lei tom.leim...@gmail.com
This patch fixes one infinite hang of bulk IN transfer in double buffer
case, the hang can be observed easily by test #6 of usbtest if musb is
configured as g_zero and fifo mode 3 is taken to enable double fifo.
In fact, the patch only removes the check for
From: Ming Lei tom.leim...@gmail.com
This patch fixes one bugs of OUT transfer in double buffer case:
-the current code only enable autoclear for dma mode 1, and not
for dma mode 0
Without this patch, test #5 of usbtest can't be passed if we
configure musb as g_zero and use fifo
From: Ming Lei tom.leim...@gmail.com
DMA length should not go beyond the availabe space of request buffer,
so fix it.
Signed-off-by: Ming Lei tom.leim...@gmail.com
Acked-by: Anand Gadiyar gadi...@ti.com
Cc: David Brownell dbrown...@users.sourceforge.net
Cc: Felipe Balbi m...@felipebalbi.com
From: Ming Lei tom.leim...@gmail.com
Complete the current request only if the data transfer is over.
Signed-off-by: Ming Lei tom.leim...@gmail.com
Cc: David Brownell dbrown...@users.sourceforge.net
Cc: Felipe Balbi m...@felipebalbi.com
Cc: Anand Gadiyar gadi...@ti.com
Cc: Mike Frysinger
From: Ming Lei tom.leim...@gmail.com
DMA length should not go beyond the availabe space of request buffer,
so fix it.
Signed-off-by: Ming Lei tom.leim...@gmail.com
Cc: David Brownell dbrown...@users.sourceforge.net
Cc: Felipe Balbi m...@felipebalbi.com
Cc: Anand Gadiyar gadi...@ti.com
Cc: Mike
From: Ming Lei tom.leim...@gmail.com
Commit 461c317705eca5cac09a360f488715927fd0a927(into 2.6.36-v3)
is put forward to power down phy if no usb cable is connected,
but does introduce the two issues below:
1), phy is not into work state if usb cable is connected
with PC during poweron, so musb
From: Ming Lei tom.leim...@gmail.com
Commit 461c317705eca5cac09a360f488715927fd0a927(into 2.6.36-v3)
is put forward to power down phy if no usb cable is connected,
but does introduce the two issues below:
1), phy is not into work state if usb cable is connected
with PC during poweron, so musb
From: Ming Lei tom.leim...@gmail.com
This patch fixes one infinite hang of bulk IN transfer in double buffer
case, the hang can be observed easily by test #6 of usbtest if musb is
configured as g_zero and fifo mode 3 is taken to enable double fifo.
In fact, the patch only removes the check for
From: Ming Lei tom.leim...@gmail.com
This patch fixes two bugs of OUT transfer in double buffer case:
-USE_MODE1 should be enabled except for ANOMALY_05000456 case, or
else may cause infinite hang and data error bug in double buffer
-DMA length should not go beyond the
From: Ming Lei tom.leim...@gmail.com
This patch fixes one bugs of OUT transfer in double buffer case:
-the current code only enable autoclear for dma mode 1, and not
for dma mode 0
Without this patch, test #5 of usbtest can't be passed if we
configure musb as g_zero and use fifo mode 3 to
From: Ming Lei tom.leim...@gmail.com
DMA length should not go beyond the availabe space of request buffer,
so fix it.
Signed-off-by: Ming Lei tom.leim...@gmail.com
Cc: Anand Gadiyar gadi...@ti.com
Cc: Mike Frysinger vap...@gentoo.org
Cc: Sergei Shtylyov sshtyl...@ru.mvista.com
---
From: Ming Lei tom.leim...@gmail.com
All hcd's debugfs entries are under usb debugfs root dir already,
so musb should not be a exception.
Signed-off-by: Ming Lei tom.leim...@gmail.com
---
drivers/usb/musb/musb_debugfs.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
From: Ming Lei tom.leim...@gmail.com
This patch uses kmalloc(size,GFP_ATOMIC) instead of kmalloc(size,GFP_KERNEL)
to allocate memory for instance of struct power_state in pwrdms_setup(),
since it may be called by pwrdm_for_each() with irq disabled.
It is a easy fix for the following lockdep
37 matches
Mail list logo
