- 15 Dec, 2009 40 commits
-
-
Mike Frysinger authored
While we're moving the BF54x code, have the BF54xM variants select the normal BF54x values so that the rest of the Kconfig tree doesn't need to check the BF54xM variant everytime it wants to check the BF54x. Signed-off-by:Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
No point in returning to userspace just to have it immediately perform the RTS step. We have to update the PC anyways, so do the RTS too. Signed-off-by: -
Sonic Zhang authored
None of these vars/funcs were being used. Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com> Signed-off-by:
-
Mike Frysinger authored
It makes no sense to call this function with a NULL callback. Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
I don't think these defines were ever used. At any rate, we have common bit defines for all parts as well as a Kconfig option to declare the EBIU async timings, and no one has really complained about this so far. Signed-off-by: -
Mike Frysinger authored
Since we always use these ids as unsigned values, and we have some assert code to make sure they don't exceed a limit, avoid signed issues. Reported-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
-
Robin Getz authored
If we're double faulting, then we have to assume the VMAs are not safe as broken pointers here will prevent full trace output for the double fault. Shouldn't be a big problem though as rarely is a double fault caused by code in userspace. Signed-off-by:
Robin Getz <robin.getz@analog.com> Signed-off-by:
-
Mike Frysinger authored
This allows us to use any Blackfin toolchain to create kernel modules (such as the FDPIC bfin-linux-uclibc toolchain). Signed-off-by: -
Mike Frysinger authored
This matches similar documentation for the FRV FDPIC code. Signed-off-by: -
Philippe Gerum authored
Signed-off-by:
Philippe Gerum <rpm@xenomai.org> Signed-off-by:
Li Yi <yi.li@analog.com> Signed-off-by:
-
Philippe Gerum authored
Signed-off-by:
-
Philippe Gerum authored
Signed-off-by:
-
Philippe Gerum authored
Signed-off-by:
-
Valentin Yakovenkov authored
Signed-off-by:
Valentin Yakovenkov <yakovenkov@gmail.com> Signed-off-by:
-
Mike Frysinger authored
This is useful for quick tests where networks are faster than compression, and/or the compression code is broken. Reported-by:
Magnus Damm <damm@igel.co.jp> Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Robin Getz authored
User reports rarely include full information, so include this important tidbit up front. It's also good to know at a glance in general. Signed-off-by:
-
Mike Frysinger authored
Every Blackfin variant has the same DMA bit masks, so avoid duplicating them over and over in each mach header. Signed-off-by: -
Michael Hennerich authored
The driver changed from "isp1760-hcd" to "isp1760", so update resources to match. Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
No need to set MSTR in .ctl_reg as the Blackfin SPI bus driver does this already for all parts. Signed-off-by: -
Mike Frysinger authored
There's no point in having mask defines when the entire MMR value is a count or address. i.e. applying a mask of -1 is pointless. Signed-off-by: -
Mike Frysinger authored
There are no MXVR device drivers, and if someday there is, we can put these in a dedicated header rather than polluting the global namespace. Signed-off-by: -
Mike Frysinger authored
People should not be accessing OTP MMRs directly. They should instead go through the Blackfin ROM helper functions. Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
The watchdog code doesn't need these, and the other parts had these punted, so keep the global namespace clean. Signed-off-by: -
Mike Frysinger authored
The RTC driver code doesn't need these, and the other parts had these punted, so keep the global namespace clean. Signed-off-by: -
Mike Frysinger authored
No point in duplicating entire lists when we can simply tail into other parts for most of the MMRs. Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
All the other BF54x parts had these defines renamed to avoid collision, but it looks the BF542 was missed somehow. Signed-off-by: -
Michael Hennerich authored
The cache lock code was unused and punted, so punt the documentation too. Signed-off-by:
-
Mike Frysinger authored
We don't need the BKL and now people will stop looking at this. Signed-off-by: -
Mike Frysinger authored
The DMA channel status field was encoding redundant info wrt the DMA MMR config register, and it was doing an incomplete job of checking all DMA channels (some drivers write directly to the config register). So drop the tristate field in favor of a binary atomic field. This simplifies the code in general, removes the implicit need for sleeping, and forces the suspend code to handle all channels properly. Signed-off-by: -
Michael Hennerich authored
The driver was moved during the merge process, so update the defines to match the new location. Signed-off-by:
-
Mike Frysinger authored
Avoid including unnecessary headers all the time as well as circular includes with core requirements. Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
All the arches define a helper macro to make things easy for driver code. Reported-by:
Frank Van Hooft <frank@frankvh.com> Signed-off-by:
-
