- 17 Sep, 2009 40 commits
-
-
Robin Getz authored
Make sure our interrupt entry code with exact hardware errors handles anomaly 05000283 (infinite stall in system MMR kill) so we don't stall while under load. Signed-off-by:
Robin Getz <robin.getz@analog.com> Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
-
Michael Hennerich authored
Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Yi Li authored
When preempt debugging is enabled, smp_processor_id() may utilize the "current" structure. This may not be safe to access under all exceptions due to it being in dynamically allocated memory. So in exception code, make sure we use raw_smp_processor_id() instead to get at the real value directly. Signed-off-by:
Yi Li <yi.li@analog.com> Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Ingo Molnar authored
Not sure whether this has been reported/fixed before. Today I built a Blackfin tool-chain from scratch for -tip testing, and it triggers: arch/blackfin/kernel/vmlinux.lds:1238: undefined section `.data_a_l1' referenced in expression and: arch/blackfin/kernel/vmlinux.lds:1238: undefined section `.text_data_l1' referenced in expression Now i dont have any way to test this linker script, but it now at least builds fine after fixing what appears to be typos in those assert statements. Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Graf Yang authored
Signed-off-by:
Graf Yang <graf.yang@analog.com> Signed-off-by:
-
Mike Frysinger authored
The majority of the time we are returning to user space, it is not in the fixed atomic code region. So rather than branch to a function where we check the PC and return, do the check inline and branch only when needed. Also, tweak some of the fixed code handling based on assumptions we are aware of but cannot be expressed in C. Signed-off-by: -
Barry Song authored
The ASoC drivers have dropped the redundant "-spi" suffix in the driver name, so update the board resources accordingly. Signed-off-by:
Barry Song <barry.song@analog.com> Signed-off-by:
-
Mike Frysinger authored
No one uses these functions, and some are duplicate of existing C code. So just punt the whole thing. Signed-off-by: -
Mike Frysinger authored
These hardware devices are dead and the drivers never cleaned up/merged, so punt the useless board resource info. Signed-off-by: -
Yi Li authored
Since the exception handler cannot cause exceptions, we cannot trace it without easily causing double faults and crashing the system. Signed-off-by:
-
Mike Frysinger authored
The BF522 and BF523 had their real max VCO values swapped. Signed-off-by: -
Graf Yang authored
We have an item to get this fixed, but in the mean time, disable selection via Kconfig dependencies. Signed-off-by:
-
Yi Li authored
The handling of updating the [DI]MEM_CONTROL MMRs does not follow proper sync procedures as laid out in the Blackfin programming manual. So rather than audit/fix every call location, create helper functions that do the right things in order to safely update these MMRs. Then convert all call sites to use these new helper functions. While we're fixing the code, drop the workaround for anomaly 05000125 as that anomaly applies to old versions of silicon that we do not support. Signed-off-by:
-
Barry Song authored
Update the ad1836 resources for the new ASoC driver. Signed-off-by:
-
Yi Li authored
Signed-off-by:
-
Barry Song authored
The board has some parallel flash hooked up to the async banks, so add appropriate physmap resources for it. Signed-off-by:
-
Roel Kluin authored
Check whether index is within bounds before testing the element. Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
-
Stefan Pledl authored
I think we have to use the physical dimensions [mm] of the display for .width and .heigth in struct bfin_bf54xfb_mach_info bf54x_lq043_data which are copied to fbinfo->var.height/.width in bf54x-lq043fb.c. linux/fb.h describes this values as 'height/weight of picture in mm' Otherwise QT calcs the wrong dpi value and the displayed fonts are very small. Signed-off-by:
Stefan Pledl <stefan.pledl@mesutronic.de> Signed-off-by:
-
Barry Song authored
The dm9000 driver expects two IORESOURCE_MEM to get at the device, so make sure we declare things properly. Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Michael Hennerich authored
Latest smc91x driver allows you to specify settings in board resources rather than needing CONFIG_BLACKFIN in the drivers/net/smc91x.h header. Signed-off-by:
-
Barry Song authored
The interrupt probe workaround doesn't work without hacks to common code, and the add-on card only needs a simple resistor to fix the problem, so drop the board-specific hack. Signed-off-by:
-
Graf Yang authored
Since the hardware only provides reporting for the last exception handled, and the values are valid only when executing the exception handler, we need to save the context for reporting at a later point. While we do this for one exception, it doesn't work properly when handling a second one as the original exception is clobbered by the double fault. So when double fault debugging is enabled, create a dedicated shadow of these values and save/restore out of there. Now the crash report properly displays the first exception as well as the second one. Signed-off-by:
-
Cliff Cai authored
One too many zeros means we run way faster than the codec can handle. Signed-off-by:
Cliff Cai <cliff.cai@analog.com> Signed-off-by:
-
Graf Yang authored
The protect_page() function was incorrectly setting up the hardware tables based on possible access capabilities rather than the actual requested values. This means we would grant more access to mmap-ed pages than we should have. Once we fix this, we need to tweak the signal generated by such accesses to aline ourselves with other ports. This allows the LTP mmap0{5,6,7} cases to run properly. Signed-off-by: -
Jean Delvare authored
I2C_BOARD_INFO() already sets .type, no need to set it again. Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Barry Song authored
Push the device table to the board resources as data interpretation can be changed on a per-board basis. Signed-off-by:
-
Sonic Zhang authored
The end of the stack may not be valid (and that could be OK), so do not attempt to parse it. If we do, we might use a bad pointer in kernel space which makes things panic(). Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com> Signed-off-by:
-
Yi Li authored
Signed-off-by:
-
Barry Song authored
Add the bf538 version of bfin_clear_PPI_STATUS() to match all other ports. Signed-off-by:
-
Stefan Pledl authored
The initial BF54x port included some defines to keep code simple across different processors, but it just ended up causing the UART0 DMA IRQs to be set to the UART1 channels. Signed-off-by:
-
Robin Getz authored
Allow hardware errors to be caught during early portions of booting, and leave something in the shadow console that people can use to debug their system with (to be printed out by the bootloader on next reset). This enables the hardare error interrupts in head.S, allowing us to find hardware errors when they happen (well, as much as you can with a hardware error) and prints out the trace if it is enabled. This will catch errors (like booting the wrong image on a 533) which previously resulted in a infinite loop/hang, as well as random hardware errors before before setup_arch(). To disable this debug only feature - turn off EARLY_PRINTK. Signed-off-by:
-
Robin Getz authored
Add a memory based shadow console to keep a copy of the printk buffer in a location which can be found externally. This allows bootloaders to locate and utilize the log buffer in case of silent (early/resume/etc...) crashes. Signed-off-by:
-
Mike Frysinger authored
The FDPIC arches support a standard set of ptrace requests so rather than define our own custom API, hook up those requests for common code to leverage. Signed-off-by: -
Mike Frysinger authored
Rather than defining the locks and initializing them all the time, only do so when we actually need them (i.e. the SRAM regions exist). This avoids dead data and code bloat during runtime. Signed-off-by: -
Sonic Zhang authored
Signed-off-by:
-
Michael Hennerich authored
The "TWI_KEYPAD" driver was renamed to "INPUT_PCF8574", so update the defines in the board resources accordingly. Signed-off-by:
-
Robin Getz authored
Remove code duplication, and only print out memory warnings when they are an actual problem. Signed-off-by:
-
Mike Frysinger authored
The current module relocation code has spotty handling wrt different memory regions (like L1 instruction). Rather than try to fix each little spot, use the new common memory functions to greatly simplify everything and make sure it is always correct. Signed-off-by:
-
