- 09 Mar, 2010 40 commits
-
-
Mike Frysinger authored
The file is no longer generated, so we don't want to clean it. Reported-by:
Vivi Li <vivi.li@analog.com> Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Graf Yang authored
Need to make sure we update the loops_per_jiffy values when we start changing the core clock. Signed-off-by:
Graf Yang <graf.yang@analog.com> Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Robin Getz authored
The exact hardware error handling code was added before the workaround for anomaly 283 which caused the anomaly to be triggered in some cases (an infinite core stall). So re-order the code to avoid this. Reported-by:
Andrew Rook <andrew.rook@speakerbus.co.uk> Signed-off-by:
Robin Getz <robin.getz@analog.com> Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Graf Yang authored
Signed-off-by:
-
Michael Hennerich authored
The on-chip keypad peripheral requires different registers to be setup depending on the standby type (standby vs hibernation). However, since the power management framework doesn't differentiate between these types, the driver doesn't know which registers to program and subsequently it avoids doing so. Always enabling the keyboard wakeup source causes misbehavior when the pins are not assigned to the keypad. If they happen to drive a certain level, they'll trigger a wake up event which is not wanted. So until the aforementioned issue can be sorted out, drop support for the wakeup source completely. Signed-off-by:
-
Sonic Zhang authored
Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com> Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Sonic Zhang authored
Signed-off-by:
-
Barry Song authored
The ASoC codec driver was generalized and renamed, so update the board resources accordingly. Signed-off-by:
Barry Song <barry.song@analog.com> Signed-off-by:
-
Graf Yang authored
Signed-off-by:
-
Michael Hennerich authored
This patch provides infrastructure for MAC Wake-On-Lan and PHYINT use in phylib. New Interrupts added: IRQ_MAC_PHYINT /* PHY_INT Interrupt */ IRQ_MAC_MMCINT /* MMC Counter Interrupt */ IRQ_MAC_RXFSINT /* RX Frame-Status Interrupt */ IRQ_MAC_TXFSINT /* TX Frame-Status Interrupt */ IRQ_MAC_WAKEDET /* Wake-Up Interrupt */ IRQ_MAC_RXDMAERR /* RX DMA Direction Error Interrupt */ IRQ_MAC_TXDMAERR /* TX DMA Direction Error Interrupt */ IRQ_MAC_STMDONE /* Station Mgt. Transfer Done Interrupt */ On BF537/6 the implementation is not straight forward since there are now two chained chained_handlers. A cleaner approach would have been to add latter IRQs to the demux of IRQ_GENERIC_ERROR. Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Joachim Eastwood authored
Signed-off-by:
Joachim Eastwood <joachim.eastwood@jotron.com> Signed-off-by:
-
Cliff Cai authored
Signed-off-by:
Cliff Cai <cliff.cai@analog.com> Signed-off-by:
-
Joachim Eastwood authored
This makes it possible to support IRQs coming from off-chip GPIO controllers. Signed-off-by:
-
Sonic Zhang authored
Signed-off-by:
-
Graf Yang authored
Signed-off-by:
-
Sonic Zhang authored
Signed-off-by:
-
Frans Pop authored
Signed-off-by:
Frans Pop <elendil@planet.nl> Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
We want to report all system calls (even invalid ones) to the tracing layers, so check the NR only after we've notified. Signed-off-by: -
Mike Frysinger authored
On Blackfin systems, the hardware single step exception triggers before the system call exception, so we need to save this info to process it later on. Otherwise, single stepping in userspace misses a few insns right after the system call. This is based a bit on the SuperH code added in commit 4b505db9. Reported-by:
Roland McGrath <roland@redhat.com> Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
We don't support core dumps (yet?), but this should make things easier. Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
We don't want to let user space modify the SYSCFG register arbitrarily as the settings are system wide (SNEN/CNEN) and can cause misbehavior. The only other bit here (SSSTEP) has proper controls via PTRACE_SINGLESTEP. Signed-off-by: -
Christoph Hellwig authored
Use the generic ptrace_resume code for PTRACE_SYSCALL, PTRACE_CONT, PTRACE_KILL and PTRACE_SINGLESTEP. This implies defining arch_has_single_step in <asm/ptrace.h> and implementing the user_enable_single_step and user_disable_single_step functions, which also causes the breakpoint information to be cleared on fork, which could be considered a bug fix. Also the TIF_SYSCALL_TRACE thread flag is now cleared on PTRACE_KILL which it previously wasn't which is consistent with all architectures using the modern ptrace code. Signed-off-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
-
Barry Song authored
Signed-off-by:
-
Graf Yang authored
This functions are implicitly called by core functions like cpu_relax(), and since those functions may be called early on before common code has initialized the per-cpu data area, we need to tweak the stats gathering. Now the statistics are maintained in common bss which makes these funcs safe to use as soon as the C runtime env is setup. Signed-off-by:
-
Graf Yang authored
Signed-off-by:
-
Barry Song authored
The ASoC codec driver was generalized and renamed, so update the board resources accordingly. Signed-off-by:
-
Yi Li authored
Since GCC doesn't support __builtin_frame_address(n) where n!=0, add our own function to walk the stack frame pointers. Signed-off-by:
Yi Li <yi.li@analog.com> Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Graf Yang authored
This allows things to be shared between the different watchdog sources. Signed-off-by:
-
Barry Song authored
Some IRQ handlers need to disable a DMA channel without waiting. Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
Signed-off-by:
-
