On 07/04/2012 12:16 PM, Guillaume Gardet wrote:
This patch add missing modules aliases to get sound working on omap devices.
Tested on Beagleboard xM rev. B.
This patch is against 3.5-rc5 vanilla.
Signed-off-by: Guillaume GARDET guillaume.gar...@free.fr
* DebBarma, Tarun Kanti tarun.ka...@ti.com [120705 04:46]:
Patch 3: Comment was about adding summary in patch 0/x why we have
not removed iclk in OMAP2/3 platform. In other words there was no
specific changes needed on patch 3 as such. BTW, patch 3 is already merged.
...
I will rebase on top
* Mohammed, Afzal af...@ti.com [120703 05:10]:
Hi Tony,
On Mon, Jul 02, 2012 at 13:05:47, Tony Lindgren wrote:
* Artem Bityutskiy artem.bityuts...@linux.intel.com [120627 02:36]:
On Wed, 2012-06-13 at 17:02 +0530, Afzal Mohammed wrote:
This series cleans up gpmc mtd interactions so
(+ linux-omap, linux-watchdog)
Vaibhav,
On Thu, Jul 5, 2012 at 8:06 PM, Bedia, Vaibhav vaibhav.be...@ti.com wrote:
Hi,
On Mon, Jun 18, 2012 at 10:53:16, Vutla, Lokesh wrote:
OMAP watchdong driver is adapted to runtime PM like a general device
driver but it is not appropriate. It is causing
* Shilimkar, Santosh santosh.shilim...@ti.com [120705 04:26]:
Looks like the merge has not happened correctly.
I see from the commit log that, you had a merge conflict in omap_hwmod.c
and probably while resolving that the below change got missed.
Tarun Kanti DebBarma (1):
ARM:
* Tarun Kanti DebBarma tarun.ka...@ti.com [120705 05:45]:
With omap_hwmod_get_main_clk() now available, this can be passed to
clk_get() to extract the fclk and thus avoid construction of fclk name.
Corrected the timer fck name mis-match between clock44xx_data.c and
omap_hwmod_44xx_data.c. For
* AnilKumar Ch anilku...@ti.com [120705 02:18]:
Adds basic pinctrl support for AM33XX family of devices. This patch
is based on the pinctrl-simple driver submitted by Tony Lindgren's
here: http://lwn.net/Articles/496075/
Signed-off-by: AnilKumar Ch anilku...@ti.com
---
On Fri, Jul 6, 2012 at 1:39 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120705 04:26]:
Looks like the merge has not happened correctly.
I see from the commit log that, you had a merge conflict in omap_hwmod.c
and probably while resolving that the
* Tero Kristo t-kri...@ti.com [120628 03:54]:
OMAP2 does not use the external voltage controller code for TWL, and
thus OMAP2 only compilation generates following warnings:
Hmm well omap2420 does not have twl, but 2430 usually has. So do you
mean that 2430 does not use the external voltage
On Fri, Jul 6, 2012 at 2:19 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
--
To unsubscribe from this
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/board-4430sdp.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-4430sdp.c
From: R Sricharan r.sricha...@ti.com
The l3 interconnect ip is same for OMAP4 and OMAP5.
So reuse the l3 error handler error code for OMAP5
as well. Also a few targets has been newly added for
OMAP5. So updating the driver for that here.
Signed-off-by: R Sricharan r.sricha...@ti.com
From: R Sricharan r.sricha...@ti.com
Adding the minimal support for OMAP5 evm board
with device tree.
Reviewed-by: Benoit Cousson b-cous...@ti.com
Signed-off-by: R Sricharan r.sricha...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
From: Tarun Kanti DebBarma tarun.ka...@ti.com
OMAP5 has 8 GPIO banks so that there are 32x8 = 256 GPIOs.
In order for the gpiolib to detect and initialize these
additional GPIOs and other TWL GPIOs, ARCH_NR_GPIO is set
to 512 instead of present 256.
Cc: Santosh Shilimkar santosh.shilim...@ti.com
On 07/06/2012 11:02 AM, Shilimkar, Santosh wrote:
On Fri, Jul 6, 2012 at 2:19 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Should remove the boot-loader
From: R Sricharan r.sricha...@ti.com
Adding the OMAP5 ES1.0, 2.0 and OMAP5432 cpu revision
detection support.
Signed-off-by: R Sricharan r.sricha...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/control.h |4
arch/arm/mach-omap2/id.c
From: R Sricharan r.sricha...@ti.com
OMAP socs has a legacy and a highlander version of the
32k sync counter IP. The register offsets vary between the
highlander and the legacy scheme. So use the 'SCHEME'
bits(30-31) of the revision register to distinguish between
the two versions and choose the
Add OMAP5 SMP boot support using OMAP4 SMP code. The relevant code paths
are runtime checked using cpu id
Signed-off-by: R Sricharan r.sricha...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/common.h |1 +
arch/arm/mach-omap2/omap-headsmp.S |
From: R Sricharan r.sricha...@ti.com
Move the irq_match arrays and the irq init functions of OMAP 2,3
and 4 based boards out of board-generic.c file and also rename the
irq init function to match the interrupt controller present in
the SOCs.
This is a preparatory patch to add the OMAP5 evm
From: R Sricharan r.sricha...@ti.com
omap_secure_ram_reserve_memblock is stubbed for OMAP1,2 only builds using a
ifdef check. But this results in adding CONFIG_ARCH_OMAPxx checks for
future socs that use the real function. So move this to common.c file and
call it __weak.
Signed-off-by: R
OMAP4 and OMAP5 share same WakeupGen IP with below few udpates on OMAP5.
- Additional 32 interrupt support is added w.r.t OMAP4 design.
- The AUX CORE boot registers are now made accessible from non-secure SW.
- SAR offset are changed and PTMSYNC* registers are removed from SAR.
Patch updates the
From: R Sricharan r.sricha...@ti.com
Adding the Initialisaton for clocksource and clockevent device
on OMAP5 Socs.
Signed-off-by: R Sricharan r.sricha...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/common.h |1 +
arch/arm/mach-omap2/timer.c |
From: R Sricharan r.sricha...@ti.com
GPMC module is the same as in OMAP4.
Just update the base address and irq number.
Signed-off-by: R Sricharan r.sricha...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/gpmc.c |3 ++-
1 file changed, 2
Tony,
Here is the updated series with suggested corrections and generated against
the latest cleanup-part2 at commit ae6df418. The series adds minimal OMAP5
support. OMAP5430 has a dual core Cortex-A15 based MPU subsystem with 2MB
L2 cache. The SOC has many compatible blocks with OMAP4 SOCS and
From: R Sricharan r.sricha...@ti.com
Adding the build support required for OMAP5 soc
in to omap2+ config.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: R Sricharan r.sricha...@ti.com
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
+ Russell
On Fri, Jul 6, 2012 at 2:52 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
On 07/06/2012 11:02 AM, Shilimkar, Santosh wrote:
On Fri, Jul 6, 2012 at 2:19 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
OMAP4 only build breaks with below error
arch/arm/mach-omap2/sdrc.c:135: error: redefinition of 'omap2_sdrc_init'
arch/arm/plat-omap/include/plat/sdrc.h:130: note: previous definition of
'omap2_sdrc_init' was here
make[1]: *** [arch/arm/mach-omap2/sdrc.o] Error 1
Fix the same by using newly
* Shilimkar, Santosh santosh.shilim...@ti.com [120706 01:32]:
On Fri, Jul 6, 2012 at 1:39 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120705 04:26]:
Looks like the merge has not happened correctly.
I see from the commit log that, you had a
* Zumeng Chen zumeng.c...@windriver.com [120620 02:19]:
Since it's no more sense to set parent for dummy clock,
so we can just ignore it to mute failed message.
This is something Paul should look at.
Regards,
Tony
Signed-off-by: Jon Hunter jon-hun...@ti.com
Signed-off-by: Zumeng Chen
Hi Wim,
* jgq...@gmail.com jgq...@gmail.com [120531 20:56]:
From: Xiao Jiang jgq...@gmail.com
Add device table for omap_wdt to support dt.
Care to ack this patch in the series?
Regards,
Tony
Signed-off-by: Xiao Jiang jgq...@gmail.com
---
drivers/watchdog/omap_wdt.c |7 +++
* Sergei Shtylyov sshtyl...@mvista.com [120620 05:10]:
On 20-06-2012 13:14, Zumeng Chen wrote:
This will set TWL4030.GPIO2 as output pin to drive EHCI tranceiver.
...
+/* Enable VBUS switch by setting TWL4030.GPIO2DIR as output
+ * for starting USB tranceiver
+ */
+if
Hi,
* AnilKumar, Chimata anilku...@ti.com [120705 01:21]:
I realized that for mcspi and mmc, the compatible name supposed tobe close to
omap4-mcspi.
These changes seems to went from my local branch, so could you please merge
below patch with this
5fc0b42a98556bd9f01cecc6a64fcbd15ec363f0
On Fri, Jul 6, 2012 at 2:00 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120706 01:32]:
On Fri, Jul 6, 2012 at 1:39 PM, Tony Lindgren t...@atomide.com wrote:
* Shilimkar, Santosh santosh.shilim...@ti.com [120705 04:26]:
Looks like the merge has
On Fri, Jul 6, 2012 at 2:19 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
Should remove the boot-loader pin-muxing dependency.
Was this the reason, Audio had
From: Xiao Jiang jgq...@gmail.com
Since more and more arm chips support device tree, it'd be better add
PROC_DEVICETREE
in arch/arm/Kconfig to avoid duplicate code.
Signed-off-by: Xiao Jiang jgq...@gmail.com
---
arch/arm/Kconfig |1 +
arch/arm/configs/at91_dt_defconfig |
On Thu, Jul 5, 2012 at 4:49 PM, Samuel Ortiz sa...@linux.intel.com wrote:
Hi Kevin, Keshava,
On Wed, Jul 04, 2012 at 06:33:35AM -0700, Kevin Hilman wrote:
Munegowda, Keshava keshava_mgo...@ti.com writes:
On Tue, Jul 3, 2012 at 12:17 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On
On Fri, 2012-07-06 at 01:53 -0700, Tony Lindgren wrote:
* Tero Kristo t-kri...@ti.com [120628 03:54]:
OMAP2 does not use the external voltage controller code for TWL, and
thus OMAP2 only compilation generates following warnings:
Hmm well omap2420 does not have twl, but 2430 usually has. So
Hi Tero,
On 06/28/2012 12:49 PM, Tero Kristo wrote:
OMAP2 does not use the external voltage controller code for TWL, and
thus OMAP2 only compilation generates following warnings:
arch/arm/mach-omap2/twl-common.c:51: warning: 'twl_set_voltage' defined but
not used
* Kevin Hilman khil...@ti.com [120705 17:35]:
Tony,
Hopefully this is the last one.
This one fixes a problem where the CORE power domain does not hit
retention during suspend. This has been known since v3.5 came out, but
there has been some discussion about the proper fix. The solution
On Mon, 25 Jun 2012, Arnd Bergmann wrote:
[snip]
The channel data in the device tree is still in a format
that is specific to that dmaengine driver and interpreted
by it. Using the regular dma_filter_fn prototype is not
necessary, but it would be convenient because the dmaengine
code
The usb host is disabled in the omap2 build; This is because
usb host is causing the retention to break in cpu idle.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
---
arch/arm/configs/omap2plus_defconfig | 11 ---
1 file changed, 11 deletions(-)
diff --git
On Fri, Jul 6, 2012 at 5:19 PM, Keshava Munegowda keshava_mgo...@ti.com wrote:
The usb host is disabled in the omap2 build; This is because
usb host is causing the retention to break in cpu idle.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
---
arch/arm/configs/omap2plus_defconfig
On Fri, Jul 6, 2012 at 3:30 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Thu, Jul 5, 2012 at 4:49 PM, Samuel Ortiz sa...@linux.intel.com wrote:
Hi Kevin, Keshava,
On Wed, Jul 04, 2012 at 06:33:35AM -0700, Kevin Hilman wrote:
Munegowda, Keshava keshava_mgo...@ti.com writes:
On
On Fri, Jul 6, 2012 at 5:25 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Fri, Jul 6, 2012 at 5:19 PM, Keshava Munegowda keshava_mgo...@ti.com
wrote:
The usb host is disabled in the omap2 build; This is because
usb host is causing the retention to break in cpu idle.
Signed-off-by:
On Fri, Jul 6, 2012 at 5:29 PM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Fri, Jul 6, 2012 at 5:25 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Fri, Jul 6, 2012 at 5:19 PM, Keshava Munegowda keshava_mgo...@ti.com
wrote:
The usb host is disabled in the omap2 build; This
* Mohammed, Afzal af...@ti.com [120705 07:56]:
Hi Tony,
On Thu, Jul 05, 2012 at 16:25:35, Tony Lindgren wrote:
* Mohammed, Afzal af...@ti.com [120705 03:29]:
I have a doubt whether we are talking about the same thing, presently
our main issue is in eliminating the necessity of
* Munegowda, Keshava keshava_mgo...@ti.com [120706 05:06]:
On Fri, Jul 6, 2012 at 5:29 PM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Fri, Jul 6, 2012 at 5:25 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
On Fri, Jul 6, 2012 at 5:19 PM, Keshava Munegowda
On Fri, Jul 6, 2012 at 5:37 PM, Tony Lindgren t...@atomide.com wrote:
* Munegowda, Keshava keshava_mgo...@ti.com [120706 05:06]:
On Fri, Jul 6, 2012 at 5:29 PM, Shilimkar, Santosh
santosh.shilim...@ti.com wrote:
On Fri, Jul 6, 2012 at 5:25 PM, Munegowda, Keshava
keshava_mgo...@ti.com wrote:
Hi Santosh,
On Fri, Jul 06, 2012 at 12:51:03, Shilimkar, Santosh wrote:
[...]
A few questions based on the description given in the commit message.
1. On OMAP4 SYSCLK can't be gated, because of issue with WDTIMER2 module,
which constantly stays in in transition state. Value of register
* Santosh Shilimkar santosh.shilim...@ti.com [120706 02:26]:
Tony,
Here is the updated series with suggested corrections and generated against
the latest cleanup-part2 at commit ae6df418. The series adds minimal OMAP5
support. OMAP5430 has a dual core Cortex-A15 based MPU subsystem with 2MB
* Munegowda, Keshava keshava_mgo...@ti.com [120706 05:30]:
On Fri, Jul 6, 2012 at 5:37 PM, Tony Lindgren t...@atomide.com wrote:
I think it's best to fix things properly, even if it means that it will
take longer and go into next kernel version.
This requires ehci remote wakeup
On 07/06/2012 05:38 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
Since more and more arm chips support device tree, it'd be better add
PROC_DEVICETREE
in arch/arm/Kconfig to avoid duplicate code.
I think this should remain user choice. If its going to be selected,
then you
On 18:38 Fri 06 Jul , jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
Since more and more arm chips support device tree, it'd be better add
PROC_DEVICETREE
in arch/arm/Kconfig to avoid duplicate code.
Acked-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com
Best
On Fri, Jul 6, 2012 at 6:06 PM, Tony Lindgren t...@atomide.com wrote:
* Santosh Shilimkar santosh.shilim...@ti.com [120706 02:26]:
Tony,
Here is the updated series with suggested corrections and generated
against
the latest cleanup-part2 at commit ae6df418. The series adds minimal
Hi,
On 07/06/2012 10:49 AM, Peter Ujfalusi wrote:
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Please ignore this two patch, I'll resend them with the correct MUX config.
By mistake I have set MUX_MODE1, while it must be set MUX_MODE0.
It was working with
Hello,
sys_nirq2 pin needs to be set to mode0 (instead of mode1 done in v1 patches).
To my surprise mode1 also worked, but it was not the correct mode.
I have kept the acks from Santosh since the idea behind of the patches are the
same, but now the mux mode is the correct one.
Regards,
Peter
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/board-4430sdp.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git
From: Misael Lopez Cruz misael.lo...@ti.com
Clock and module mode are explictly enable when hwmod is enabled. But if
the hwmod doesn't get ready on time, clocks are disabled but module is left
enabled.
Signed-off-by: Misael Lopez Cruz misael.lo...@ti.com
Signed-off-by: Rajendra Nayak
On Fri, Jul 6, 2012 at 6:09 PM, Tony Lindgren t...@atomide.com wrote:
* Munegowda, Keshava keshava_mgo...@ti.com [120706 05:30]:
On Fri, Jul 6, 2012 at 5:37 PM, Tony Lindgren t...@atomide.com wrote:
I think it's best to fix things properly, even if it means that it will
take longer and go
From: Yegor Yefremov yegorsli...@googlemail.com
add FB_BLANK_NORMAL, FB_BLANK_VSYNC_SUSPEND and FB_BLANK_HSYNC_SUSPEND
modes (copy drivers/video/omap2/omapfb/omapfb-main.c implementation).
Otherwise X-server will complain about invalid parameter.
Signed-off-by: Yegor Yefremov
Keshava Munegowda keshava_mgo...@ti.com writes:
The usb host is disabled in the omap2 build; This is because
usb host is causing the retention to break in cpu idle.
... and causes warnings during boot, and hangs in suspend, can't suspend
using NFSroot, etc. etc.
Thank you for disabling this
Peter Ujfalusi peter.ujfal...@ti.com writes:
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/board-4430sdp.c |3 +++
1 files
Alessandro,
Gentle reminder ping on this one so it can make it in for v3.5-rc. Thanks.
On Thu, Jun 28, 2012 at 9:17 AM, Kevin Hilman khil...@ti.com wrote:
Requesting a threaded interrupt without a primary handler and without
IRQF_ONESHOT is dangerous, and after commit 1c6c6952 (genirq:
On Fri, Jul 6, 2012 at 7:46 PM, Kevin Hilman khil...@ti.com wrote:
Peter Ujfalusi peter.ujfal...@ti.com writes:
The sys_nirq2 is used for twl6040, make sure the pin is configured
correctly.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Santosh Shilimkar
I've requested several times to remove my e-mail from that list. I'll
report it to legal authorities on this issue if no action is taken.
William.
* Mohammed, Afzalaf...@ti.com [120703 05:10]:
Hi Tony,
On Mon, Jul 02, 2012 at 13:05:47, Tony Lindgren wrote:
* Artem
On Fri, 2012-07-06 at 11:35 -0300, William F. wrote:
I've requested several times to remove my e-mail from that list. I'll
report it to legal authorities on this issue if no action is taken.
Have you tried following the link at the bottom of every mail you
receive from the list, and following
On Friday 06 July 2012, Guennadi Liakhovetski wrote:
On Mon, 25 Jun 2012, Arnd Bergmann wrote:
[snip]
The channel data in the device tree is still in a format
that is specific to that dmaengine driver and interpreted
by it. Using the regular dma_filter_fn prototype is not
necessary,
Hi Arnd
On Fri, 6 Jul 2012, Arnd Bergmann wrote:
On Friday 06 July 2012, Guennadi Liakhovetski wrote:
On Mon, 25 Jun 2012, Arnd Bergmann wrote:
[snip]
The channel data in the device tree is still in a format
that is specific to that dmaengine driver and interpreted
by it.
Requesting a threaded interrupt without a primary handler and without
IRQF_ONESHOT is dangerous, and after commit 1c6c6952 (genirq: Reject
bogus threaded irq requests), these requests are rejected. This
causes -probe() to fail, and the RTC driver not to be availble.
To fix, add IRQF_ONESHOT to
The EHCI driver is not stable enough to be enabled by default. In v3.5,
it has at least the following problems:
- warning dump during bootup
- hang during suspend
- prevents CORE powerdomain from entering retention during idle (even
when no USB devices connected.)
This demonstrates that this
On Friday 06 July 2012, Guennadi Liakhovetski wrote:
dmaengine_core
for_each_channel() {
ret = chan-device-device_alloc_chan_resources(chan,
filter_arg);
if (!ret)
return chan;
else if (ret != -ENODEV)
On Fri, Jul 06, 2012 at 01:36:32PM +0200, Guennadi Liakhovetski wrote:
I like this idea, but why don't we extend it to also cover the non-DT
case? I.e., why don't we add the above callback (call it match or
filter or anything else) to dmaengine operations and inside (the
extended)
On Fri, Jul 06, 2012 at 05:43:38PM +0200, Guennadi Liakhovetski wrote:
Hi Arnd
On Fri, 6 Jul 2012, Arnd Bergmann wrote:
How would the individual driver know the size of the filter_arg?
In exactly the same way as most dmaengine drivers do it today: they don't
touch filter_arg until
Hello `./scripts/get_maintainer.pl -f drivers/usb/musb/omap2430.c`
omap2430_musb_set_vbus in omap2430.c contains:
while (musb_readb(musb-mregs, MUSB_DEVCTL) 0x80) {
cpu_relax();
if (time_after(jiffies,
On Thu, 2012-07-05 at 10:44 +0800, Andy Green wrote:
[...]
To make use of this safely you also need to make sure that any drivers that
may compete for the bus ordinal you are using (eg, mUSB and ehci in Panda
case) are loaded in a deterministic order.
[...]
This seems very restrictive... would
On Fri, 6 Jul 2012, Russell King - ARM Linux wrote:
On Fri, Jul 06, 2012 at 01:36:32PM +0200, Guennadi Liakhovetski wrote:
I like this idea, but why don't we extend it to also cover the non-DT
case? I.e., why don't we add the above callback (call it match or
filter or anything else) to
device_init_wakeup uses the dev_name() of the device to set the
name of the wakeup_source which appears in
/sys/kernel/debug/wakeup_sources.
For a platform device, that name is not set until platform_device_add
calls dev_set_name.
So the call to device_init_wakeup() must be after the call to
On Fri, Jul 6, 2012 at 4:15 PM, Xiao Jiang jgq...@gmail.com wrote:
2012/7/6 Rob Herring robherri...@gmail.com
On 07/06/2012 05:38 AM, jgq...@gmail.com wrote:
From: Xiao Jiang jgq...@gmail.com
Since more and more arm chips support device tree, it'd be better add
PROC_DEVICETREE
in
Hi Grant,
Here's a couple (hopefully) final OMAP GPIO fixes for v3.5-rc.
Thanks,
Kevin
The following changes since commit 6b16351acbd415e66ba16bf7d473ece1574cf0bc:
Linux 3.5-rc4 (2012-06-24 12:53:04 -0700)
are available in the git repository at:
81 matches
Mail list logo
