mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-25 21:54:06 +08:00
1394f03221
This adds support for the Analog Devices Blackfin processor architecture, and currently supports the BF533, BF532, BF531, BF537, BF536, BF534, and BF561 (Dual Core) devices, with a variety of development platforms including those avaliable from Analog Devices (BF533-EZKit, BF533-STAMP, BF537-STAMP, BF561-EZKIT), and Bluetechnix! Tinyboards. The Blackfin architecture was jointly developed by Intel and Analog Devices Inc. (ADI) as the Micro Signal Architecture (MSA) core and introduced it in December of 2000. Since then ADI has put this core into its Blackfin processor family of devices. The Blackfin core has the advantages of a clean, orthogonal,RISC-like microprocessor instruction set. It combines a dual-MAC (Multiply/Accumulate), state-of-the-art signal processing engine and single-instruction, multiple-data (SIMD) multimedia capabilities into a single instruction-set architecture. The Blackfin architecture, including the instruction set, is described by the ADSP-BF53x/BF56x Blackfin Processor Programming Reference http://blackfin.uclinux.org/gf/download/frsrelease/29/2549/Blackfin_PRM.pdf The Blackfin processor is already supported by major releases of gcc, and there are binary and source rpms/tarballs for many architectures at: http://blackfin.uclinux.org/gf/project/toolchain/frs There is complete documentation, including "getting started" guides available at: http://docs.blackfin.uclinux.org/ which provides links to the sources and patches you will need in order to set up a cross-compiling environment for bfin-linux-uclibc This patch, as well as the other patches (toolchain, distribution, uClibc) are actively supported by Analog Devices Inc, at: http://blackfin.uclinux.org/ We have tested this on LTP, and our test plan (including pass/fails) can be found at: http://docs.blackfin.uclinux.org/doku.php?id=testing_the_linux_kernel [m.kozlowski@tuxland.pl: balance parenthesis in blackfin header files] Signed-off-by: Bryan Wu <bryan.wu@analog.com> Signed-off-by: Mariusz Kozlowski <m.kozlowski@tuxland.pl> Signed-off-by: Aubrey Li <aubrey.li@analog.com> Signed-off-by: Jie Zhang <jie.zhang@analog.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
49 lines
1.2 KiB
Plaintext
49 lines
1.2 KiB
Plaintext
/*
|
|
* File: Documentation/blackfin/cache-lock.txt
|
|
* Based on:
|
|
* Author:
|
|
*
|
|
* Created:
|
|
* Description: This file contains the simple DMA Implementation for Blackfin
|
|
*
|
|
* Rev: $Id: cache-lock.txt 2384 2006-11-01 04:12:43Z magicyang $
|
|
*
|
|
* Modified:
|
|
* Copyright 2004-2006 Analog Devices Inc.
|
|
*
|
|
* Bugs: Enter bugs at http://blackfin.uclinux.org/
|
|
*
|
|
*/
|
|
|
|
How to lock your code in cache in uClinux/blackfin
|
|
--------------------------------------------------
|
|
|
|
There are only a few steps required to lock your code into the cache.
|
|
Currently you can lock the code by Way.
|
|
|
|
Below are the interface provided for locking the cache.
|
|
|
|
|
|
1. cache_grab_lock(int Ways);
|
|
|
|
This function grab the lock for locking your code into the cache specified
|
|
by Ways.
|
|
|
|
|
|
2. cache_lock(int Ways);
|
|
|
|
This function should be called after your critical code has been executed.
|
|
Once the critical code exits, the code is now loaded into the cache. This
|
|
function locks the code into the cache.
|
|
|
|
|
|
So, the example sequence will be:
|
|
|
|
cache_grab_lock(WAY0_L); /* Grab the lock */
|
|
|
|
critical_code(); /* Execute the code of interest */
|
|
|
|
cache_lock(WAY0_L); /* Lock the cache */
|
|
|
|
Where WAY0_L signifies WAY0 locking.
|