.gitignore | 1 arch/x86/include/asm/perf_event_p4.h | 1 arch/x86/kernel/cpu/perf_event_p4.c | 11 + drivers/char/pcmcia/cm4000_cs.c | 3 drivers/char/pcmcia/ipwireless/main.c | 52 +++++--- drivers/i2c/busses/i2c-omap.c | 35 +++++- drivers/i2c/busses/i2c-stu300.c | 2 drivers/pcmcia/pcmcia_resource.c | 2 drivers/pcmcia/pxa2xx_base.c | 2 drivers/pcmcia/pxa2xx_base.h | 1 drivers/pcmcia/pxa2xx_lubbock.c | 1 drivers/usb/core/quirks.c | 8 + drivers/usb/musb/musb_core.h | 17 +- drivers/usb/musb/omap2430.c | 1 drivers/usb/serial/sierra.c | 3 drivers/usb/serial/usb_wwan.c | 15 +- drivers/usb/serial/visor.c | 12 ++ include/pcmcia/ds.h | 1 include/sound/wm8903.h | 10 - kernel/irq/internals.h | 6 + kernel/irq/irqdesc.c | 11 + kernel/irq/manage.c | 2 kernel/irq/resend.c | 2 kernel/perf_event.c | 19 ++- sound/soc/codecs/cx20442.c | 2 sound/soc/codecs/wm8903.c | 2 sound/soc/codecs/wm8994.c | 197 +++++++++++++++++++++++++++++++--- sound/soc/soc-dapm.c | 23 +++ 28 files changed, 369 insertions(+), 73 deletions(-)
New commits: commit a5a595cc36bbbe16f6a3f0e6968f94a0604bfd28 Author: Ben Dooks <[email protected]> Date: Wed Feb 23 00:43:55 2011 +0000 i2c-omap: fixup commit cb527ede1bf6ff2008a025606f25344b8ed7b4ac whitespace Fixup the whitespace error noticed in cb527ede1bf6ff2008a025606f25344b8ed7b4ac Signed-off-by: Ben Dooks <[email protected]> commit cb527ede1bf6ff2008a025606f25344b8ed7b4ac Author: Richard woodruff <[email protected]> Date: Wed Feb 16 10:24:16 2011 +0530 i2c-omap: Double clear of ARDY status in IRQ handler This errata occurs when the ARDY interrupt generation is enabled. At the begining of every new transaction the ARDY interrupt is cleared. On continuous i2c transactions where after clearing the ARDY bit from I2C_STAT register (clearing the interrupt), the IRQ line is reasserted and the I2C_STAT[ARDY] bit set again on 1. In fact, the ARDY status bit is not cleared at the write access to I2C_STAT[ARDY] and only the IRQ line is deasserted and then reasserted. This is not captured in the usual errata documents. The workaround is to have a double clear of ARDY status in irq handler. Signed-off-by: Richard woodruff <[email protected]> Signed-off-by: Keerthy <[email protected]> Signed-off-by: Ben Dooks <[email protected]> commit f72487e7a1827f5e95425b80ec4fcc4f928329e8 Author: Balaji T K <[email protected]> Date: Tue Feb 22 12:25:39 2011 +0530 i2c-omap: fix build for !CONFIG_SUSPEND fix the build break when !CONFIG_SUSPEND drivers/i2c/busses/i2c-omap.c:1173: error: lvalue required as unary '&' operand make[3]: *** [drivers/i2c/busses/i2c-omap.o] Error 1 make[2]: *** [drivers/i2c/busses] Error 2 make[1]: *** [drivers/i2c] Error 2 make: *** [drivers] Error 2 Signed-off-by: Balaji T K <[email protected]> Signed-off-by: Ben Dooks <[email protected]> commit adf6e07922255937c8bfeea777d19502b4c9a2be Author: Kevin Hilman <[email protected]> Date: Thu Jan 27 16:18:41 2011 -0800 i2c-omap: fix static suspend vs. runtime suspend When runtime PM is enabled, each OMAP i2c device is suspended after each i2c xfer. However, there are two cases when the static suspend methods must be used to ensure the devices are suspended: 1) runtime PM is disabled, either at compile time or dynamically via /sys/devices/.../power/control. 2) an i2c client driver uses i2c during it's suspend callback, thus leaving the i2c driver active (NOTE: runtime suspend transitions are disabled during system suspend, so i2c activity during system suspend will runtime resume the device, but not runtime (re)suspend it.) Since the actual work to suspend the device is handled by the subsytem, call the bus methods to take care of it. NOTE: This takes care of a known suspend problem on OMAP3 where the TWL RTC driver does i2c xfers during its suspend path leaving the i2c driver in an active state (since runtime suspend transistions are disabled.) Signed-off-by: Kevin Hilman <[email protected]> Signed-off-by: Ben Dooks <[email protected]> commit f10820e49585f281706ac07570a9e1652bdb5dd9 Author: Wolfram Sang <[email protected]> Date: Mon Jan 31 15:09:23 2011 +0100 i2c-stu300: make sure adapter-name is terminated Use strlcpy instead of strncpy. Signed-off-by: Wolfram Sang <[email protected]> Cc: Linus Walleij <[email protected]> Cc: Ben Dooks <[email protected]> Signed-off-by: Ben Dooks <[email protected]> commit 790e10ba6c93c123665a3cfa53d6dcf73923e458 Author: Romain Francoise <[email protected]> Date: Tue Feb 22 10:48:06 2011 +0100 .gitignore: ignore *.xz files Building with CONFIG_KERNEL_XZ results in the following: # Untracked files: # (use "git add <file>..." to include in what will be committed) # # arch/x86/boot/compressed/vmlinux.bin.xz So ignore xz-compressed files at the top level like we already do for other compression types. Signed-off-by: Romain Francoise <[email protected]> Signed-off-by: Linus Torvalds <[email protected]> commit 33619f0d3ff715a2a5499520967d526ad931d70d Author: Dominik Brodowski <[email protected]> Date: Sat Feb 19 12:35:15 2011 +0100 pcmcia: re-enable Zoomed Video support Allow drivers to enable Zoomed Video support. Currently, this is only used by out-of-tree drivers (L64020 DVB driver in particular). CC: <[email protected]> [for 2.6.37] Signed-off-by: Dominik Brodowski <[email protected]> commit 644e6e4a7fa6b11d59f24032997d90ea0d858d03 Author: Alan Cox <[email protected]> Date: Tue Feb 1 15:46:05 2011 +0000 cm4000_cs: Fix undefined ops warning Signed-off-by: Alan Cox <[email protected]> Signed-off-by: Dominik Brodowski <[email protected]> commit 5b703683b6cc3cb97bbe6b1b14898b273eb59279 Author: Pavel Machek <[email protected]> Date: Fri Feb 4 09:03:43 2011 +0100 pcmcia vs. MECR on pxa25x/sa1111 After 2.6.34 changes, __pxa2xx_drv_pcmcia_probe() was replaced by sa1111_pcmcia_add(). That unfortunately means that configure_sockets() is not called, leading to MECR not being set properly, leading to strange crashes. Tested on pxa255+sa1111, I do not have lubbock board nearby. Perhaps cleaner solution exists? Signed-off-by: Pavel Machek <[email protected]> Signed-off-by: Dominik Brodowski <[email protected]> commit d5bb2923cfa0a29c5854f9618703ff60849b949e Author: Julia Lawall <[email protected]> Date: Sun Feb 13 13:12:10 2011 +0100 drivers/char/pcmcia/ipwireless/main.c: Convert release_resource to release_region/release_mem_region Request_region should be used with release_region, not release_resource. This patch contains a number of changes, related to calls to request_region, request_mem_region, and the associated error handling code. 1. For the call to request_region, the variable io_resource storing the result is dropped. The call to release_resource at the end of the function is changed to a call to release_region with the first two arguments of request_region as its arguments. The same call to release_region is also added to release_ipwireless. 2. The first call to request_mem_region is now tested and ret is set to -EBUSY if the the call has failed. This call was associated with the initialization of ipw->attr_memory. But the error handling code was testing ipw->common_memory. The definition of release_ipwireless also suggests that this call should be associated with ipw->common_memory, not ipw->attr_memory. 3. The second call to request_mem_region is now tested and ret is set to -EBUSY if the the call has failed. 4. The various gotos to the error handling code is adjusted so that there is no need for ifs. 5. Return the value stored in the ret variable rather than -1. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // <smpl> @@ expression x,E; @@ ( *x = request_region(...) | *x = request_mem_region(...) ) ... when != release_region(x) when != x = E * release_resource(x); // </smpl> Signed-off-by: Julia Lawall <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Dominik Brodowski <[email protected]> commit 6d83f94db95cfe65d2a6359cccdf61cf087c2598 Author: Thomas Gleixner <[email protected]> Date: Fri Feb 18 23:27:23 2011 +0100 genirq: Disable the SHIRQ_DEBUG call in request_threaded_irq for now With CONFIG_SHIRQ_DEBUG=y we call a newly installed interrupt handler in request_threaded_irq(). The original implementation (commit a304e1b8) called the handler _BEFORE_ it was installed, but that caused problems with handlers calling disable_irq_nosync(). See commit 377bf1e4. It's braindead in the first place to call disable_irq_nosync in shared handlers, but .... Moving this call after we installed the handler looks innocent, but it is very subtle broken on SMP. Interrupt handlers rely on the fact, that the irq core prevents reentrancy. Now this debug call violates that promise because we run the handler w/o the IRQ_INPROGRESS protection - which we cannot apply here because that would result in a possibly forever masked interrupt line. A concurrent real hardware interrupt on a different CPU results in handler reentrancy and can lead to complete wreckage, which was unfortunately observed in reality and took a fricking long time to debug. Leave the code here for now. We want this debug feature, but that's not easy to fix. We really should get rid of those disable_irq_nosync() abusers and remove that function completely. Signed-off-by: Thomas Gleixner <[email protected]> Cc: Anton Vorontsov <[email protected]> Cc: David Woodhouse <[email protected]> Cc: Arjan van de Ven <[email protected]> Cc: [email protected] # .28 -> .37 commit c1ee6264280e740a9d3ff3feef38642cf0a57013 Author: Thomas Gleixner <[email protected]> Date: Thu Feb 17 17:45:15 2011 +0100 genirq: Prevent access beyond allocated_irqs bitmap Lars-Peter Clausen pointed out: I stumbled upon this while looking through the existing archs using SPARSE_IRQ. Even with SPARSE_IRQ the NR_IRQS is still the upper limit for the number of IRQs. Both PXA and MMP set NR_IRQS to IRQ_BOARD_START, with IRQ_BOARD_START being the number of IRQs used by the core. In various machine files the nr_irqs field of the ARM machine defintion struct is then set to "IRQ_BOARD_START + NR_BOARD_IRQS". As a result "nr_irqs" will greater then NR_IRQS which then again causes the "allocated_irqs" bitmap in the core irq code to be accessed beyond its size overwriting unrelated data. The core code really misses a sanity check there. This went unnoticed so far as by chance the compiler/linker places data behind that bitmap which gets initialized later on those affected platforms. So the obvious fix would be to add a sanity check in early_irq_init() and break all affected platforms. Though that check wants to be backported to stable as well, which will require to fix all known problematic platforms and probably some more yet not known ones as well. Lots of churn. A way simpler solution is to allocate a slightly larger bitmap and avoid the whole churn w/o breaking anything. Add a few warnings when an arch returns utter crap. Reported-by: Lars-Peter Clausen <[email protected]> Signed-off-by: Thomas Gleixner <[email protected]> Cc: [email protected] # .37 Cc: Haojian Zhuang <[email protected]> Cc: Eric Miao <[email protected]> Cc: Peter Zijlstra <[email protected]> commit 9ce4f80fb67b47b96c647ac6280a06dbd4bb50d2 Author: Greg Kroah-Hartman <[email protected]> Date: Thu Feb 17 14:39:36 2011 -0800 Revert "USB: Reset USB 3.0 devices on (re)discovery" This reverts commit 637d11bfb814637ec7b81e878db3ffea6408a89a. Sarah wants to tweak it some more before it's applied to the tree. Cc: Luben Tuikov <[email protected]> Cc: Sarah Sharp <[email protected]> Cc: Alan Stern <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 19b9a83e214d3d3ac52a56daca5ea0d033ca47bc Author: Johan Hovold <[email protected]> Date: Fri Feb 11 16:57:08 2011 +0100 USB: musb: omap2430: fix kernel panic on reboot Cancel idle timer in musb_platform_exit. The idle timer could trigger after clock had been disabled leading to kernel panic when MUSB_DEVCTL is accessed in musb_do_idle on 2.6.37. The fault below is no longer triggered on 2.6.38-rc4 (clock is disabled later, and only if compiled as a module, and the offending memory access has moved) but the timer should be cancelled nonetheless. Rebooting... musb_hdrc musb_hdrc: remove, state 4 usb usb1: USB disconnect, address 1 musb_hdrc musb_hdrc: USB bus 1 deregistered Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab060 Internal error: : 1028 [#1] PREEMPT last sysfs file: /sys/kernel/uevent_seqnum Modules linked in: CPU: 0 Not tainted (2.6.37+ #6) PC is at musb_do_idle+0x24/0x138 LR is at musb_do_idle+0x18/0x138 pc : [<c02377d8>] lr : [<c02377cc>] psr: 80000193 sp : cf2bdd80 ip : cf2bdd80 fp : c048a20c r10: c048a60c r9 : c048a40c r8 : cf85e110 r7 : cf2bc000 r6 : 40000113 r5 : c0489800 r4 : cf85e110 r3 : 00000004 r2 : 00000006 r1 : fa0ab000 r0 : cf8a7000 Flags: Nzcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user Control: 10c5387d Table: 8faac019 DAC: 00000015 Process reboot (pid: 769, stack limit = 0xcf2bc2f0) Stack: (0xcf2bdd80 to 0xcf2be000) dd80: 00000103 c0489800 c02377b4 c005fa34 00000555 c0071a8c c04a3858 cf2bdda8 dda0: 00000555 c048a00c cf2bdda8 cf2bdda8 1838beb0 00000103 00000004 cf2bc000 ddc0: 00000001 00000001 c04896c8 0000000a 00000000 c005ac14 00000001 c003f32c dde0: 00000000 00000025 00000000 cf2bc000 00000002 00000001 cf2bc000 00000000 de00: 00000001 c005ad08 cf2bc000 c002e07c c03ec039 ffffffff fa200000 c0033608 de20: 00000001 00000000 cf852c14 cf81f200 c045b714 c045b708 cf2bc000 c04a37e8 de40: c0033c04 cf2bc000 00000000 00000001 cf2bde68 cf2bde68 c01c3abc c004f7d8 de60: 60000013 ffffffff c0033c04 00000000 01234567 fee1dead 00000000 c006627c de80: 00000001 c00662c8 28121969 c00663ec cfa38c40 cf9f6a00 cf2bded0 cf9f6a0c dea0: 00000000 cf92f000 00008914 c02cd284 c04a55c8 c028b398 c00715c0 becf24a8 dec0: 30687465 00000000 00000000 00000000 00000002 1301a8c0 00000000 00000000 dee0: 00000002 1301a8c0 00000000 00000000 c0450494 cf527920 00011f10 cf2bdf08 df00: 00011f10 cf2bdf10 00011f10 cf2bdf18 c00f0b44 c004f7e8 cf2bdf18 cf2bdf18 df20: 00011f10 cf2bdf30 00011f10 cf2bdf38 cf401300 cf486100 00000008 c00d2b28 df40: 00011f10 cf401300 00200200 c00d3388 00011f10 cfb63a88 cfb63a80 c00c2f08 df60: 00000000 00000000 cfb63a80 00000000 cf0a3480 00000006 c0033c04 cfb63a80 df80: 00000000 c00c0104 00000003 cf0a3480 cfb63a80 00000000 00000001 00000004 dfa0: 00000058 c0033a80 00000000 00000001 fee1dead 28121969 01234567 00000000 dfc0: 00000000 00000001 00000004 00000058 00000001 00000001 00000000 00000001 dfe0: 4024d200 becf2cb0 00009210 4024d218 60000010 fee1dead 00000000 00000000 [<c02377d8>] (musb_do_idle+0x24/0x138) from [<c005fa34>] (run_timer_softirq+0x1a8/0x26) [<c005fa34>] (run_timer_softirq+0x1a8/0x26c) from [<c005ac14>] (__do_softirq+0x88/0x13) [<c005ac14>] (__do_softirq+0x88/0x138) from [<c005ad08>] (irq_exit+0x44/0x98) [<c005ad08>] (irq_exit+0x44/0x98) from [<c002e07c>] (asm_do_IRQ+0x7c/0xa0) [<c002e07c>] (asm_do_IRQ+0x7c/0xa0) from [<c0033608>] (__irq_svc+0x48/0xa8) Exception stack(0xcf2bde20 to 0xcf2bde68) de20: 00000001 00000000 cf852c14 cf81f200 c045b714 c045b708 cf2bc000 c04a37e8 de40: c0033c04 cf2bc000 00000000 00000001 cf2bde68 cf2bde68 c01c3abc c004f7d8 de60: 60000013 ffffffff [<c0033608>] (__irq_svc+0x48/0xa8) from [<c004f7d8>] (sub_preempt_count+0x0/0xb8) Code: ebf86030 e5940098 e594108c e5902010 (e5d13060) ---[ end trace 3689c0d808f9bf7c ]--- Kernel panic - not syncing: Fatal exception in interrupt Cc: stable <[email protected]> Signed-off-by: Johan Hovold <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit e1dc5157c574e7249dc1cd072fde2e48b3011533 Author: Jon Thomas <[email protected]> Date: Wed Feb 16 11:02:34 2011 -0500 sierra: add new ID for Airprime/Sierra USB IP modem I picked up a new Sierra usb 308 (At&t Shockwave) on 2/2011 and the vendor code is 0x0f3d Looking up vendor and product id's I see: 0f3d Airprime, Incorporated 0112 CDMA 1xEVDO PC Card, PC 5220 Sierra and Airprime are somehow related and I'm guessing the At&t usb 308 might be have some common hardware with the AirPrime SL809x. Signed-off-by: Jon Thomas <[email protected]> Cc: stable <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 38237fd2be9421c104f84cc35665097bdce89013 Author: Jiri Slaby <[email protected]> Date: Tue Feb 15 15:55:07 2011 +0100 USB: serial/usb_wwan, fix tty NULL dereference tty_port_tty_get may return without any problems NULL. Handle this case and do not oops in usb_wwan_indat_callback by dereferencing it. The oops: Unable to handle kernel paging request for data at address 0x000000d8 Faulting instruction address: 0xc0175b3c Oops: Kernel access of bad area, sig: 11 [#1] PowerPC 40x Platform last sysfs file: /sys/devices/pci0000:00/0000:00:00.0/0000:01:00.0/0000:02:09.2/usb1/idVendor Modules linked in: NIP: c0175b3c LR: c0175e7c CTR: c0215c90 REGS: c77f7d50 TRAP: 0300 Not tainted (2.6.37-rc5) MSR: 00021030 <ME,CE,IR,DR> CR: 88482028 XER: 2000005f DEAR: 000000d8, ESR: 00000000 TASK = c7141b90[1149] 'wvdial' THREAD: c2750000 GPR00: 00021030 c77f7e00 c7141b90 00000000 0000000e 00000000 0000000e c0410680 GPR08: c683db00 00000000 00000001 c03c81f8 88482028 10073ef4 ffffffb9 ffffff94 GPR16: 00000000 fde036c0 00200200 00100100 00000001 ffffff8d c34fabcc 00000000 GPR24: c71120d4 00000000 00000000 0000000e 00021030 00000000 00000000 0000000e NIP [c0175b3c] tty_buffer_request_room+0x2c/0x194 LR [c0175e7c] tty_insert_flip_string_fixed_flag+0x3c/0xb0 Call Trace: [c77f7e00] [00000003] 0x3 (unreliable) [c77f7e30] [c0175e7c] tty_insert_flip_string_fixed_flag+0x3c/0xb0 [c77f7e60] [c0215df4] usb_wwan_indat_callback+0x164/0x170 ... References: https://bugzilla.kernel.org/show_bug.cgi?id=24582 Cc: Amit Shah <[email protected]> Cc: baoyb <[email protected]> Signed-off-by: Jiri Slaby <[email protected]> Cc: stable <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 637d11bfb814637ec7b81e878db3ffea6408a89a Author: Luben Tuikov <[email protected]> Date: Fri Feb 11 11:33:10 2011 -0800 USB: Reset USB 3.0 devices on (re)discovery If the device isn't reset, the XHCI HCD sends SET ADDRESS to address 0 while the device is already in Addressed state, and the request is dropped on the floor as it is addressed to the default address. This sequence of events, which this patch fixes looks like this: usb_reset_and_verify_device() hub_port_init() hub_set_address() SET_ADDRESS to 0 with 1 usb_get_device_descriptor(udev, 8) usb_get_device_descriptor(udev, 18) descriptors_changed() --> goto re_enumerate: hub_port_logical_disconnect() kick_khubd() And then: hub_events() hub_port_connect_change() usb_disconnect() usb_disable_device() new device struct sets device state to Powered choose_address() hub_port_init() <-- no reset, but SET ADDRESS to 0 with 1, timeout! The solution is to always reset the device in hub_port_init() to put it in a known state. Signed-off-by: Luben Tuikov <[email protected]> Cc: Sarah Sharp <[email protected]> Cc: Alan Stern <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 72a012ce0a02c6c616676a24b40ff81d1aaeafda Author: Maciej Szmigiero <[email protected]> Date: Sat Feb 5 21:52:00 2011 +0100 USB: Add quirk for Samsung Android phone modem My Galaxy Spica needs this quirk when in modem mode, otherwise it causes endless USB bus resets and is unusable in this mode. Unfortunately Samsung decided to reuse ID of its old CDMA phone SGH-I500 for the modem part. That's why in addition to this patch the visor driver must be prevented from binding to SPH-I500 ID, so ACM driver can do that. Signed-off-by: Maciej Szmigiero <[email protected]> Cc: stable <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit acb52cb1613e1d3c8a8c650717cc51965c60d7d4 Author: Maciej Szmigiero <[email protected]> Date: Mon Feb 7 12:42:36 2011 +0100 USB: Add Samsung SGH-I500/Android modem ID switch to visor driver [USB]Add Samsung SGH-I500/Android modem ID switch to visor driver Samsung decided to reuse USB ID of its old CDMA phone SGH-I500 for the modem part of some of their Android phones. At least Galaxy Spica is affected. This modem needs ACM driver and does not work with visor driver which binds the conflicting ID for SGH-I500. Because SGH-I500 is pretty an old hardware its best to add switch to visor driver in cause somebody still wants to use that phone with Linux. Note that this is needed only when using the Android phone as modem, not in USB storage or ADB mode. Signed-off-by: Maciej Szmigiero <[email protected]> Cc: stable <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 3c18e30f87ac5466bddbb05cf955605efd7db025 Author: Alan Stern <[email protected]> Date: Thu Feb 17 10:26:38 2011 -0500 USB: add quirks entry for Keytouch QWERTY Panel This patch (as1448) adds a quirks entry for the Keytouch QWERTY Panel firmware, used in the IEC 60945 keyboard. This device crashes during enumeration when the computer asks for its configuration string descriptor. Signed-off-by: Alan Stern <[email protected]> Tested-by: kholis <[email protected]> CC: <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit b193b412e62b134adf69af286c7e7f8e99259350 Author: Johan Hovold <[email protected]> Date: Fri Feb 11 16:57:08 2011 +0100 usb: musb: omap2430: fix kernel panic on reboot Cancel idle timer in musb_platform_exit. The idle timer could trigger after clock had been disabled leading to kernel panic when MUSB_DEVCTL is accessed in musb_do_idle on 2.6.37. The fault below is no longer triggered on 2.6.38-rc4 (clock is disabled later, and only if compiled as a module, and the offending memory access has moved) but the timer should be cancelled nonetheless. Rebooting... musb_hdrc musb_hdrc: remove, state 4 usb usb1: USB disconnect, address 1 musb_hdrc musb_hdrc: USB bus 1 deregistered Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab060 Internal error: : 1028 [#1] PREEMPT last sysfs file: /sys/kernel/uevent_seqnum Modules linked in: CPU: 0 Not tainted (2.6.37+ #6) PC is at musb_do_idle+0x24/0x138 LR is at musb_do_idle+0x18/0x138 pc : [<c02377d8>] lr : [<c02377cc>] psr: 80000193 sp : cf2bdd80 ip : cf2bdd80 fp : c048a20c r10: c048a60c r9 : c048a40c r8 : cf85e110 r7 : cf2bc000 r6 : 40000113 r5 : c0489800 r4 : cf85e110 r3 : 00000004 r2 : 00000006 r1 : fa0ab000 r0 : cf8a7000 Flags: Nzcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user Control: 10c5387d Table: 8faac019 DAC: 00000015 Process reboot (pid: 769, stack limit = 0xcf2bc2f0) Stack: (0xcf2bdd80 to 0xcf2be000) dd80: 00000103 c0489800 c02377b4 c005fa34 00000555 c0071a8c c04a3858 cf2bdda8 dda0: 00000555 c048a00c cf2bdda8 cf2bdda8 1838beb0 00000103 00000004 cf2bc000 ddc0: 00000001 00000001 c04896c8 0000000a 00000000 c005ac14 00000001 c003f32c dde0: 00000000 00000025 00000000 cf2bc000 00000002 00000001 cf2bc000 00000000 de00: 00000001 c005ad08 cf2bc000 c002e07c c03ec039 ffffffff fa200000 c0033608 de20: 00000001 00000000 cf852c14 cf81f200 c045b714 c045b708 cf2bc000 c04a37e8 de40: c0033c04 cf2bc000 00000000 00000001 cf2bde68 cf2bde68 c01c3abc c004f7d8 de60: 60000013 ffffffff c0033c04 00000000 01234567 fee1dead 00000000 c006627c de80: 00000001 c00662c8 28121969 c00663ec cfa38c40 cf9f6a00 cf2bded0 cf9f6a0c dea0: 00000000 cf92f000 00008914 c02cd284 c04a55c8 c028b398 c00715c0 becf24a8 dec0: 30687465 00000000 00000000 00000000 00000002 1301a8c0 00000000 00000000 dee0: 00000002 1301a8c0 00000000 00000000 c0450494 cf527920 00011f10 cf2bdf08 df00: 00011f10 cf2bdf10 00011f10 cf2bdf18 c00f0b44 c004f7e8 cf2bdf18 cf2bdf18 df20: 00011f10 cf2bdf30 00011f10 cf2bdf38 cf401300 cf486100 00000008 c00d2b28 df40: 00011f10 cf401300 00200200 c00d3388 00011f10 cfb63a88 cfb63a80 c00c2f08 df60: 00000000 00000000 cfb63a80 00000000 cf0a3480 00000006 c0033c04 cfb63a80 df80: 00000000 c00c0104 00000003 cf0a3480 cfb63a80 00000000 00000001 00000004 dfa0: 00000058 c0033a80 00000000 00000001 fee1dead 28121969 01234567 00000000 dfc0: 00000000 00000001 00000004 00000058 00000001 00000001 00000000 00000001 dfe0: 4024d200 becf2cb0 00009210 4024d218 60000010 fee1dead 00000000 00000000 [<c02377d8>] (musb_do_idle+0x24/0x138) from [<c005fa34>] (run_timer_softirq+0x1a8/0x26) [<c005fa34>] (run_timer_softirq+0x1a8/0x26c) from [<c005ac14>] (__do_softirq+0x88/0x13) [<c005ac14>] (__do_softirq+0x88/0x138) from [<c005ad08>] (irq_exit+0x44/0x98) [<c005ad08>] (irq_exit+0x44/0x98) from [<c002e07c>] (asm_do_IRQ+0x7c/0xa0) [<c002e07c>] (asm_do_IRQ+0x7c/0xa0) from [<c0033608>] (__irq_svc+0x48/0xa8) Exception stack(0xcf2bde20 to 0xcf2bde68) de20: 00000001 00000000 cf852c14 cf81f200 c045b714 c045b708 cf2bc000 c04a37e8 de40: c0033c04 cf2bc000 00000000 00000001 cf2bde68 cf2bde68 c01c3abc c004f7d8 de60: 60000013 ffffffff [<c0033608>] (__irq_svc+0x48/0xa8) from [<c004f7d8>] (sub_preempt_count+0x0/0xb8) Code: ebf86030 e5940098 e594108c e5902010 (e5d13060) ---[ end trace 3689c0d808f9bf7c ]--- Kernel panic - not syncing: Fatal exception in interrupt Cc: [email protected] Signed-off-by: Johan Hovold <[email protected]> Signed-off-by: Felipe Balbi <[email protected]> commit 5990378b393429244559f4750f2ee3a50929b932 Author: Felipe Balbi <[email protected]> Date: Fri Feb 11 10:00:02 2011 +0200 usb: musb: fix build breakage commit 0662481855c389b75a0a54c32870cc90563d80a9 (usb: musb: disable double buffering when it's broken), introduced a compile error when gadget API is disabled. Fix it. Signed-off-by: Felipe Balbi <[email protected]> commit 4fe757dd48a9e95e1a071291f15dda5421dacb66 Author: Peter Zijlstra <[email protected]> Date: Tue Feb 15 22:26:07 2011 +0100 perf: Fix throttle logic It was possible to call pmu::start() on an already running event. In particular this lead so some wreckage as the hrtimer events would re-initialize active timers. This was due to throttled events being activated again by scheduling. Scheduling in a context would add and force start events, resulting in running events with a possible throttle status. The next tick to hit that task will then try to unthrottle the event and call ->start() on an already running event. Reported-by: Jeff Moyer <[email protected]> Cc: <[email protected]> Signed-off-by: Peter Zijlstra <[email protected]> LKML-Reference: <new-submission> Signed-off-by: Ingo Molnar <[email protected]> commit 7d44ec193d95416d1342cdd86392a1eeb7461186 Author: Cyrill Gorcunov <[email protected]> Date: Wed Feb 16 14:08:02 2011 +0300 perf, x86: P4 PMU: Fix spurious NMI messages Several people have reported spurious unknown NMI messages on some P4 CPUs. This patch fixes it by checking for an overflow (negative counter values) directly, instead of relying on the P4_CCCR_OVF bit. Reported-by: George Spelvin <[email protected]> Reported-by: Meelis Roos <[email protected]> Reported-by: Don Zickus <[email protected]> Reported-by: Dave Airlie <[email protected]> Signed-off-by: Cyrill Gorcunov <[email protected]> Cc: Lin Ming <[email protected]> Cc: Don Zickus <[email protected]> Cc: Peter Zijlstra <[email protected]> LKML-Reference: <[email protected]> Signed-off-by: Ingo Molnar <[email protected]> commit 3017358a75917b5ed5ad361c02ba2a7e257d3b2a Author: Mark Brown <[email protected]> Date: Fri Feb 11 11:42:19 2011 +0000 ASoC: Ensure supplies are maintained for force enabled widgets If a widget has been force enabled then not only do we need to keep the widget itself enabled, we also need to keep any supplies the widget requires enabled. The user could force all the individual widgets on but this requires too much knowledge of device internals. Signed-off-by: Mark Brown <[email protected]> Tested-by: Stephen Warren <[email protected]> Acked-by: Liam Girdwood <[email protected]> commit c52fd021bc027a90a10782c0dcf667ac0135e478 Author: Dimitris Papastamos <[email protected]> Date: Fri Feb 11 16:32:12 2011 +0000 ASoC: WM8994: Improve playback robustness On WM8994 revision D and earlier ensure proper playback robustness as some rare use cases can trigger issues. Signed-off-by: Dimitris Papastamos <[email protected]> Acked-by: Liam Girdwood <[email protected]> Signed-off-by: Mark Brown <[email protected]> Cc: [email protected] commit 173efa09e4c807a2a764509ddd593ad13a44d1df Author: Dimitris Papastamos <[email protected]> Date: Fri Feb 11 16:32:11 2011 +0000 ASoC: WM8994: Improve robustness in some use cases Ensure that on disabling certain registers such as AIF1DAC1L, AIF1DAC1R etc. the AIF1CLK and AIF2CLK remain enabled. Similarly when enabling those registers, AIF1CLK and AIF2CLK will remain disabled. Signed-off-by: Dimitris Papastamos <[email protected]> Acked-by: Liam Girdwood <[email protected]> Signed-off-by: Mark Brown <[email protected]> Cc: [email protected] commit 3088e3b4963d26d6f6f54987f595b974ed6d48d8 Author: Stephen Warren <[email protected]> Date: Thu Feb 10 15:37:14 2011 -0700 ASoC: WM8903: Fix mic detection enable logic The mic detection HW should be enabled when either mic or short detection is required, not when only both are required. Signed-off-by: Stephen Warren <[email protected]> Acked-by: Liam Girdwood <[email protected]> Signed-off-by: Mark Brown <[email protected]> Cc: [email protected] commit 28d639f7bd2559e3d6dc10c0316d19154b28a2a4 Author: Stephen Warren <[email protected]> Date: Thu Feb 10 15:37:13 2011 -0700 ASoC: WM8903: Fix mic detection register definitions * There is no hysteresis enable field in the current datasheet. * Mic detection threshold field is only 2 bits wide. Signed-off-by: Stephen Warren <[email protected]> Acked-by: Liam Girdwood <[email protected]> Signed-off-by: Mark Brown <[email protected]> commit 8e6bfb9b1f79e07c18b0ae406c7c678fc54e4d8e Author: Janusz Krzysztofik <[email protected]> Date: Thu Feb 10 13:24:32 2011 +0100 ASoC: CX20442: fix wrong reg_cache_default content Content of the CX20442's snd_soc_codec_driver.reg_cache_default pointed area, introduced with my recent NULL pointer dereferece fix (commit f019ee5feb344ff0b22b58df4568676295aae14f), occured wrong after further testing, more thorough than just booting successfully. There are two problems with it: 1) It should read (1 << CX20442_TELOUT) | (1 << CX20442_MIC), not CX20442_TELOUT | CX20442_MIC. 2) While correctly matching actual codec hardware state on boot when fixed per 1), a few more code modifications would still be required to reflect that state not only into register cache, but also force them into DAPM pins state, otherwise an inconsitency occures which may prevent further codec state changes from being applied correctly. As a result, the phone stops ringing after reboot, until someone picks up the handset for the first time. Revert that reg_cache_default content to a working, previous de facto default value of 0, in hope this change can still be accepted as an rc cycle fix. Created and tested against linux-2.6.38-rc4 Signed-off-by: Janusz Krzysztofik <[email protected]> Acked-by: Liam Girdwood <[email protected]> Signed-off-by: Mark Brown <[email protected]> commit b66a70d5e9929f3b0df5a7177bba75652d2f4c3e Author: Mark Brown <[email protected]> Date: Wed Feb 9 18:04:11 2011 +0000 ASoC: Sync initial widget state with hardware ASoC generally uses the register defaults for everything, but in some cases the hardware will default to enabling some of the DAPM widgets (clocks for example). Ensure that DAPM knows about the actual widget state at initialisation by reading the enable bits after instantiating the widgets so they don't get left enabled needlessly. Signed-off-by: Mark Brown <[email protected]> Acked-by: Liam Girdwood <[email protected]> http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=a5a595cc36bbbe16f6a3f0e6968f94a0604bfd28 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=cb527ede1bf6ff2008a025606f25344b8ed7b4ac http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=f72487e7a1827f5e95425b80ec4fcc4f928329e8 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=adf6e07922255937c8bfeea777d19502b4c9a2be http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=f10820e49585f281706ac07570a9e1652bdb5dd9 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=790e10ba6c93c123665a3cfa53d6dcf73923e458 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=33619f0d3ff715a2a5499520967d526ad931d70d http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=644e6e4a7fa6b11d59f24032997d90ea0d858d03 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=5b703683b6cc3cb97bbe6b1b14898b273eb59279 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=d5bb2923cfa0a29c5854f9618703ff60849b949e http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=6d83f94db95cfe65d2a6359cccdf61cf087c2598 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=c1ee6264280e740a9d3ff3feef38642cf0a57013 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=9ce4f80fb67b47b96c647ac6280a06dbd4bb50d2 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=19b9a83e214d3d3ac52a56daca5ea0d033ca47bc http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=e1dc5157c574e7249dc1cd072fde2e48b3011533 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=38237fd2be9421c104f84cc35665097bdce89013 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=637d11bfb814637ec7b81e878db3ffea6408a89a http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=72a012ce0a02c6c616676a24b40ff81d1aaeafda http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=acb52cb1613e1d3c8a8c650717cc51965c60d7d4 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=3c18e30f87ac5466bddbb05cf955605efd7db025 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=b193b412e62b134adf69af286c7e7f8e99259350 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=5990378b393429244559f4750f2ee3a50929b932 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=4fe757dd48a9e95e1a071291f15dda5421dacb66 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=7d44ec193d95416d1342cdd86392a1eeb7461186 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=3017358a75917b5ed5ad361c02ba2a7e257d3b2a http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=c52fd021bc027a90a10782c0dcf667ac0135e478 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=173efa09e4c807a2a764509ddd593ad13a44d1df http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=3088e3b4963d26d6f6f54987f595b974ed6d48d8 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=28d639f7bd2559e3d6dc10c0316d19154b28a2a4 http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=8e6bfb9b1f79e07c18b0ae406c7c678fc54e4d8e http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=b66a70d5e9929f3b0df5a7177bba75652d2f4c3e _______________________________________________ svn mailing list [email protected] http://mailman.vyatta.com/mailman/listinfo/svn
