Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
接近 2 年 前同步成功

通知 169
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 923a789b 编写于 作者: I Ingo Molnar
浏览文件
操作

Merge branch 'linus' into x86/cleanups 

Conflicts:
	arch/x86/kernel/reboot.c
上级 103ceffb b840d796
展开全部 隐藏空白更改
内联 并排
Showing with 39257 addition and 12817 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
Documentation/ABI/testing/sysfs-class-uwb_rc
浏览文件 @ 923a789b
......@@ -32,14 +32,16 @@ Contact: linux-usb@vger.kernel.org
Description:
Write:
<channel> [<bpst offset>]
<channel>
to start beaconing on a specific channel, or stop
beaconing if <channel> is -1. Valid channels depends
on the radio controller's supported band groups.
to force a specific channel to be used when beaconing,
or, if <channel> is -1, to prohibit beaconing. If
<channel> is 0, then the default channel selection
algorithm will be used. Valid channels depends on the
radio controller's supported band groups.
<bpst offset> may be used to try and join a specific
beacon group if more than one was found during a scan.
Reading returns the currently active channel, or -1 if
the radio controller is not beaconing.
What: /sys/class/uwb_rc/uwbN/scan
Date: July 2008
......
Documentation/RCU/00-INDEX
浏览文件 @ 923a789b
......@@ -16,6 +16,8 @@ RTFP.txt
- List of RCU papers (bibliography) going back to 1980.
torture.txt
- RCU Torture Test Operation (CONFIG_RCU_TORTURE_TEST)
trace.txt
- CONFIG_RCU_TRACE debugfs files and formats
UP.txt
- RCU on Uniprocessor Systems
whatisRCU.txt
......
Documentation/RCU/trace.txt 0 → 100644
浏览文件 @ 923a789b
CONFIG_RCU_TRACE debugfs Files and Formats
The rcupreempt and rcutree implementations of RCU provide debugfs trace
output that summarizes counters and state. This information is useful for
debugging RCU itself, and can sometimes also help to debug abuses of RCU.
Note that the rcuclassic implementation of RCU does not provide debugfs
trace output.
The following sections describe the debugfs files and formats for
preemptable RCU (rcupreempt) and hierarchical RCU (rcutree).
Preemptable RCU debugfs Files and Formats
This implementation of RCU provides three debugfs files under the
top-level directory RCU: rcu/rcuctrs (which displays the per-CPU
counters used by preemptable RCU) rcu/rcugp (which displays grace-period
counters), and rcu/rcustats (which internal counters for debugging RCU).
The output of "cat rcu/rcuctrs" looks as follows:
CPU last cur F M
0 5 -5 0 0
1 -1 0 0 0
2 0 1 0 0
3 0 1 0 0
4 0 1 0 0
5 0 1 0 0
6 0 2 0 0
7 0 -1 0 0
8 0 1 0 0
ggp = 26226, state = waitzero
The per-CPU fields are as follows:
o "CPU" gives the CPU number. Offline CPUs are not displayed.
o "last" gives the value of the counter that is being decremented
for the current grace period phase. In the example above,
the counters sum to 4, indicating that there are still four
RCU read-side critical sections still running that started
before the last counter flip.
o "cur" gives the value of the counter that is currently being
both incremented (by rcu_read_lock()) and decremented (by
rcu_read_unlock()). In the example above, the counters sum to
1, indicating that there is only one RCU read-side critical section
still running that started after the last counter flip.
o "F" indicates whether RCU is waiting for this CPU to acknowledge
a counter flip. In the above example, RCU is not waiting on any,
which is consistent with the state being "waitzero" rather than
"waitack".
o "M" indicates whether RCU is waiting for this CPU to execute a
memory barrier. In the above example, RCU is not waiting on any,
which is consistent with the state being "waitzero" rather than
"waitmb".
o "ggp" is the global grace-period counter.
o "state" is the RCU state, which can be one of the following:
o "idle": there is no grace period in progress.
o "waitack": RCU just incremented the global grace-period
counter, which has the effect of reversing the roles of
the "last" and "cur" counters above, and is waiting for
all the CPUs to acknowledge the flip. Once the flip has
been acknowledged, CPUs will no longer be incrementing
what are now the "last" counters, so that their sum will
decrease monotonically down to zero.
o "waitzero": RCU is waiting for the sum of the "last" counters
to decrease to zero.
o "waitmb": RCU is waiting for each CPU to execute a memory
barrier, which ensures that instructions from a given CPU's
last RCU read-side critical section cannot be reordered
with instructions following the memory-barrier instruction.
The output of "cat rcu/rcugp" looks as follows:
oldggp=48870 newggp=48873
Note that reading from this file provokes a synchronize_rcu(). The
"oldggp" value is that of "ggp" from rcu/rcuctrs above, taken before
executing the synchronize_rcu(), and the "newggp" value is also the
"ggp" value, but taken after the synchronize_rcu() command returns.
The output of "cat rcu/rcugp" looks as follows:
na=1337955 nl=40 wa=1337915 wl=44 da=1337871 dl=0 dr=1337871 di=1337871
1=50989 e1=6138 i1=49722 ie1=82 g1=49640 a1=315203 ae1=265563 a2=49640
z1=1401244 ze1=1351605 z2=49639 m1=5661253 me1=5611614 m2=49639
These are counters tracking internal preemptable-RCU events, however,
some of them may be useful for debugging algorithms using RCU. In
particular, the "nl", "wl", and "dl" values track the number of RCU
callbacks in various states. The fields are as follows:
o "na" is the total number of RCU callbacks that have been enqueued
since boot.
o "nl" is the number of RCU callbacks waiting for the previous
grace period to end so that they can start waiting on the next
grace period.
o "wa" is the total number of RCU callbacks that have started waiting
for a grace period since boot. "na" should be roughly equal to
"nl" plus "wa".
o "wl" is the number of RCU callbacks currently waiting for their
grace period to end.
o "da" is the total number of RCU callbacks whose grace periods
have completed since boot. "wa" should be roughly equal to
"wl" plus "da".
o "dr" is the total number of RCU callbacks that have been removed
from the list of callbacks ready to invoke. "dr" should be roughly
equal to "da".
o "di" is the total number of RCU callbacks that have been invoked
since boot. "di" should be roughly equal to "da", though some
early versions of preemptable RCU had a bug so that only the
last CPU's count of invocations was displayed, rather than the
sum of all CPU's counts.
o "1" is the number of calls to rcu_try_flip(). This should be
roughly equal to the sum of "e1", "i1", "a1", "z1", and "m1"
described below. In other words, the number of times that
the state machine is visited should be equal to the sum of the
number of times that each state is visited plus the number of
times that the state-machine lock acquisition failed.
o "e1" is the number of times that rcu_try_flip() was unable to
acquire the fliplock.
o "i1" is the number of calls to rcu_try_flip_idle().
o "ie1" is the number of times rcu_try_flip_idle() exited early
due to the calling CPU having no work for RCU.
o "g1" is the number of times that rcu_try_flip_idle() decided
to start a new grace period. "i1" should be roughly equal to
"ie1" plus "g1".
o "a1" is the number of calls to rcu_try_flip_waitack().
o "ae1" is the number of times that rcu_try_flip_waitack() found
that at least one CPU had not yet acknowledge the new grace period
(AKA "counter flip").
o "a2" is the number of time rcu_try_flip_waitack() found that
all CPUs had acknowledged. "a1" should be roughly equal to
"ae1" plus "a2". (This particular output was collected on
a 128-CPU machine, hence the smaller-than-usual fraction of
calls to rcu_try_flip_waitack() finding all CPUs having already
acknowledged.)
o "z1" is the number of calls to rcu_try_flip_waitzero().
o "ze1" is the number of times that rcu_try_flip_waitzero() found
that not all of the old RCU read-side critical sections had
completed.
o "z2" is the number of times that rcu_try_flip_waitzero() finds
the sum of the counters equal to zero, in other words, that
all of the old RCU read-side critical sections had completed.
The value of "z1" should be roughly equal to "ze1" plus
"z2".
o "m1" is the number of calls to rcu_try_flip_waitmb().
o "me1" is the number of times that rcu_try_flip_waitmb() finds
that at least one CPU has not yet executed a memory barrier.
o "m2" is the number of times that rcu_try_flip_waitmb() finds that
all CPUs have executed a memory barrier.
Hierarchical RCU debugfs Files and Formats
This implementation of RCU provides three debugfs files under the
top-level directory RCU: rcu/rcudata (which displays fields in struct
rcu_data), rcu/rcugp (which displays grace-period counters), and
rcu/rcuhier (which displays the struct rcu_node hierarchy).
The output of "cat rcu/rcudata" looks as follows:
rcu:
0 c=4011 g=4012 pq=1 pqc=4011 qp=0 rpfq=1 rp=3c2a dt=23301/73 dn=2 df=1882 of=0 ri=2126 ql=2 b=10
1 c=4011 g=4012 pq=1 pqc=4011 qp=0 rpfq=3 rp=39a6 dt=78073/1 dn=2 df=1402 of=0 ri=1875 ql=46 b=10
2 c=4010 g=4010 pq=1 pqc=4010 qp=0 rpfq=-5 rp=1d12 dt=16646/0 dn=2 df=3140 of=0 ri=2080 ql=0 b=10
3 c=4012 g=4013 pq=1 pqc=4012 qp=1 rpfq=3 rp=2b50 dt=21159/1 dn=2 df=2230 of=0 ri=1923 ql=72 b=10
4 c=4012 g=4013 pq=1 pqc=4012 qp=1 rpfq=3 rp=1644 dt=5783/1 dn=2 df=3348 of=0 ri=2805 ql=7 b=10
5 c=4012 g=4013 pq=0 pqc=4011 qp=1 rpfq=3 rp=1aac dt=5879/1 dn=2 df=3140 of=0 ri=2066 ql=10 b=10
6 c=4012 g=4013 pq=1 pqc=4012 qp=1 rpfq=3 rp=ed8 dt=5847/1 dn=2 df=3797 of=0 ri=1266 ql=10 b=10
7 c=4012 g=4013 pq=1 pqc=4012 qp=1 rpfq=3 rp=1fa2 dt=6199/1 dn=2 df=2795 of=0 ri=2162 ql=28 b=10
rcu_bh:
0 c=-268 g=-268 pq=1 pqc=-268 qp=0 rpfq=-145 rp=21d6 dt=23301/73 dn=2 df=0 of=0 ri=0 ql=0 b=10
1 c=-268 g=-268 pq=1 pqc=-268 qp=1 rpfq=-170 rp=20ce dt=78073/1 dn=2 df=26 of=0 ri=5 ql=0 b=10
2 c=-268 g=-268 pq=1 pqc=-268 qp=1 rpfq=-83 rp=fbd dt=16646/0 dn=2 df=28 of=0 ri=4 ql=0 b=10
3 c=-268 g=-268 pq=1 pqc=-268 qp=0 rpfq=-105 rp=178c dt=21159/1 dn=2 df=28 of=0 ri=2 ql=0 b=10
4 c=-268 g=-268 pq=1 pqc=-268 qp=1 rpfq=-30 rp=b54 dt=5783/1 dn=2 df=32 of=0 ri=0 ql=0 b=10
5 c=-268 g=-268 pq=1 pqc=-268 qp=1 rpfq=-29 rp=df5 dt=5879/1 dn=2 df=30 of=0 ri=3 ql=0 b=10
6 c=-268 g=-268 pq=1 pqc=-268 qp=1 rpfq=-28 rp=788 dt=5847/1 dn=2 df=32 of=0 ri=0 ql=0 b=10
7 c=-268 g=-268 pq=1 pqc=-268 qp=1 rpfq=-53 rp=1098 dt=6199/1 dn=2 df=30 of=0 ri=3 ql=0 b=10
The first section lists the rcu_data structures for rcu, the second for
rcu_bh. Each section has one line per CPU, or eight for this 8-CPU system.
The fields are as follows:
o The number at the beginning of each line is the CPU number.
CPUs numbers followed by an exclamation mark are offline,
but have been online at least once since boot. There will be
no output for CPUs that have never been online, which can be
a good thing in the surprisingly common case where NR_CPUS is
substantially larger than the number of actual CPUs.
o "c" is the count of grace periods that this CPU believes have
completed. CPUs in dynticks idle mode may lag quite a ways
behind, for example, CPU 4 under "rcu" above, which has slept
through the past 25 RCU grace periods. It is not unusual to
see CPUs lagging by thousands of grace periods.
o "g" is the count of grace periods that this CPU believes have
started. Again, CPUs in dynticks idle mode may lag behind.
If the "c" and "g" values are equal, this CPU has already
reported a quiescent state for the last RCU grace period that
it is aware of, otherwise, the CPU believes that it owes RCU a
quiescent state.
o "pq" indicates that this CPU has passed through a quiescent state
for the current grace period. It is possible for "pq" to be
"1" and "c" different than "g", which indicates that although
the CPU has passed through a quiescent state, either (1) this
CPU has not yet reported that fact, (2) some other CPU has not
yet reported for this grace period, or (3) both.
o "pqc" indicates which grace period the last-observed quiescent
state for this CPU corresponds to. This is important for handling
the race between CPU 0 reporting an extended dynticks-idle
quiescent state for CPU 1 and CPU 1 suddenly waking up and
reporting its own quiescent state. If CPU 1 was the last CPU
for the current grace period, then the CPU that loses this race
will attempt to incorrectly mark CPU 1 as having checked in for
the next grace period!
o "qp" indicates that RCU still expects a quiescent state from
this CPU.
o "rpfq" is the number of rcu_pending() calls on this CPU required
to induce this CPU to invoke force_quiescent_state().
o "rp" is low-order four hex digits of the count of how many times
rcu_pending() has been invoked on this CPU.
o "dt" is the current value of the dyntick counter that is incremented
when entering or leaving dynticks idle state, either by the
scheduler or by irq. The number after the "/" is the interrupt
nesting depth when in dyntick-idle state, or one greater than
the interrupt-nesting depth otherwise.
This field is displayed only for CONFIG_NO_HZ kernels.
o "dn" is the current value of the dyntick counter that is incremented
when entering or leaving dynticks idle state via NMI. If both
the "dt" and "dn" values are even, then this CPU is in dynticks
idle mode and may be ignored by RCU. If either of these two
counters is odd, then RCU must be alert to the possibility of
an RCU read-side critical section running on this CPU.
This field is displayed only for CONFIG_NO_HZ kernels.
o "df" is the number of times that some other CPU has forced a
quiescent state on behalf of this CPU due to this CPU being in
dynticks-idle state.
This field is displayed only for CONFIG_NO_HZ kernels.
o "of" is the number of times that some other CPU has forced a
quiescent state on behalf of this CPU due to this CPU being
offline. In a perfect world, this might neve happen, but it
turns out that offlining and onlining a CPU can take several grace
periods, and so there is likely to be an extended period of time
when RCU believes that the CPU is online when it really is not.
Please note that erring in the other direction (RCU believing a
CPU is offline when it is really alive and kicking) is a fatal
error, so it makes sense to err conservatively.
o "ri" is the number of times that RCU has seen fit to send a
reschedule IPI to this CPU in order to get it to report a
quiescent state.
o "ql" is the number of RCU callbacks currently residing on
this CPU. This is the total number of callbacks, regardless
of what state they are in (new, waiting for grace period to
start, waiting for grace period to end, ready to invoke).
o "b" is the batch limit for this CPU. If more than this number
of RCU callbacks is ready to invoke, then the remainder will
be deferred.
The output of "cat rcu/rcugp" looks as follows:
rcu: completed=33062 gpnum=33063
rcu_bh: completed=464 gpnum=464
Again, this output is for both "rcu" and "rcu_bh". The fields are
taken from the rcu_state structure, and are as follows:
o "completed" is the number of grace periods that have completed.
It is comparable to the "c" field from rcu/rcudata in that a
CPU whose "c" field matches the value of "completed" is aware
that the corresponding RCU grace period has completed.
o "gpnum" is the number of grace periods that have started. It is
comparable to the "g" field from rcu/rcudata in that a CPU
whose "g" field matches the value of "gpnum" is aware that the
corresponding RCU grace period has started.
If these two fields are equal (as they are for "rcu_bh" above),
then there is no grace period in progress, in other words, RCU
is idle. On the other hand, if the two fields differ (as they
do for "rcu" above), then an RCU grace period is in progress.
The output of "cat rcu/rcuhier" looks as follows, with very long lines:
c=6902 g=6903 s=2 jfq=3 j=72c7 nfqs=13142/nfqsng=0(13142) fqlh=6
1/1 0:127 ^0
3/3 0:35 ^0 0/0 36:71 ^1 0/0 72:107 ^2 0/0 108:127 ^3
3/3f 0:5 ^0 2/3 6:11 ^1 0/0 12:17 ^2 0/0 18:23 ^3 0/0 24:29 ^4 0/0 30:35 ^5 0/0 36:41 ^0 0/0 42:47 ^1 0/0 48:53 ^2 0/0 54:59 ^3 0/0 60:65 ^4 0/0 66:71 ^5 0/0 72:77 ^0 0/0 78:83 ^1 0/0 84:89 ^2 0/0 90:95 ^3 0/0 96:101 ^4 0/0 102:107 ^5 0/0 108:113 ^0 0/0 114:119 ^1 0/0 120:125 ^2 0/0 126:127 ^3
rcu_bh:
c=-226 g=-226 s=1 jfq=-5701 j=72c7 nfqs=88/nfqsng=0(88) fqlh=0
0/1 0:127 ^0
0/3 0:35 ^0 0/0 36:71 ^1 0/0 72:107 ^2 0/0 108:127 ^3
0/3f 0:5 ^0 0/3 6:11 ^1 0/0 12:17 ^2 0/0 18:23 ^3 0/0 24:29 ^4 0/0 30:35 ^5 0/0 36:41 ^0 0/0 42:47 ^1 0/0 48:53 ^2 0/0 54:59 ^3 0/0 60:65 ^4 0/0 66:71 ^5 0/0 72:77 ^0 0/0 78:83 ^1 0/0 84:89 ^2 0/0 90:95 ^3 0/0 96:101 ^4 0/0 102:107 ^5 0/0 108:113 ^0 0/0 114:119 ^1 0/0 120:125 ^2 0/0 126:127 ^3
This is once again split into "rcu" and "rcu_bh" portions. The fields are
as follows:
o "c" is exactly the same as "completed" under rcu/rcugp.
o "g" is exactly the same as "gpnum" under rcu/rcugp.
o "s" is the "signaled" state that drives force_quiescent_state()'s
state machine.
o "jfq" is the number of jiffies remaining for this grace period
before force_quiescent_state() is invoked to help push things
along. Note that CPUs in dyntick-idle mode thoughout the grace
period will not report on their own, but rather must be check by
some other CPU via force_quiescent_state().
o "j" is the low-order four hex digits of the jiffies counter.
Yes, Paul did run into a number of problems that turned out to
be due to the jiffies counter no longer counting. Why do you ask?
o "nfqs" is the number of calls to force_quiescent_state() since
boot.
o "nfqsng" is the number of useless calls to force_quiescent_state(),
where there wasn't actually a grace period active. This can
happen due to races. The number in parentheses is the difference
between "nfqs" and "nfqsng", or the number of times that
force_quiescent_state() actually did some real work.
o "fqlh" is the number of calls to force_quiescent_state() that
exited immediately (without even being counted in nfqs above)
due to contention on ->fqslock.
o Each element of the form "1/1 0:127 ^0" represents one struct
rcu_node. Each line represents one level of the hierarchy, from
root to leaves. It is best to think of the rcu_data structures
as forming yet another level after the leaves. Note that there
might be either one, two, or three levels of rcu_node structures,
depending on the relationship between CONFIG_RCU_FANOUT and
CONFIG_NR_CPUS.
o The numbers separated by the "/" are the qsmask followed
by the qsmaskinit. The qsmask will have one bit
set for each entity in the next lower level that
has not yet checked in for the current grace period.
The qsmaskinit will have one bit for each entity that is
currently expected to check in during each grace period.
The value of qsmaskinit is assigned to that of qsmask
at the beginning of each grace period.
For example, for "rcu", the qsmask of the first entry
of the lowest level is 0x14, meaning that we are still
waiting for CPUs 2 and 4 to check in for the current
grace period.
o The numbers separated by the ":" are the range of CPUs
served by this struct rcu_node. This can be helpful
in working out how the hierarchy is wired together.
For example, the first entry at the lowest level shows
"0:5", indicating that it covers CPUs 0 through 5.
o The number after the "^" indicates the bit in the
next higher level rcu_node structure that this
rcu_node structure corresponds to.
For example, the first entry at the lowest level shows
"^0", indicating that it corresponds to bit zero in
the first entry at the middle level.
Documentation/arm/pxa/mfp.txt 0 → 100644
浏览文件 @ 923a789b
MFP Configuration for PXA2xx/PXA3xx Processors
Eric Miao <eric.miao@marvell.com>
MFP stands for Multi-Function Pin, which is the pin-mux logic on PXA3xx and
later PXA series processors. This document describes the existing MFP API,
and how board/platform driver authors could make use of it.
Basic Concept
===============
Unlike the GPIO alternate function settings on PXA25x and PXA27x, a new MFP
mechanism is introduced from PXA3xx to completely move the pin-mux functions
out of the GPIO controller. In addition to pin-mux configurations, the MFP
also controls the low power state, driving strength, pull-up/down and event
detection of each pin. Below is a diagram of internal connections between
the MFP logic and the remaining SoC peripherals:
+--------+
| |--(GPIO19)--+
| GPIO | |
| |--(GPIO...) |
+--------+ |
| +---------+
+--------+ +------>| |
| PWM2 |--(PWM_OUT)-------->| MFP |
+--------+ +------>| |-------> to external PAD
| +---->| |
+--------+ | | +-->| |
| SSP2 |---(TXD)----+ | | +---------+
+--------+ | |
| |
+--------+ | |
| Keypad |--(MKOUT4)----+ |
+--------+ |
|
+--------+ |
| UART2 |---(TXD)--------+
+--------+
NOTE: the external pad is named as MFP_PIN_GPIO19, it doesn't necessarily
mean it's dedicated for GPIO19, only as a hint that internally this pin
can be routed from GPIO19 of the GPIO controller.
To better understand the change from PXA25x/PXA27x GPIO alternate function
to this new MFP mechanism, here are several key points:
1. GPIO controller on PXA3xx is now a dedicated controller, same as other
internal controllers like PWM, SSP and UART, with 128 internal signals
which can be routed to external through one or more MFPs (e.g. GPIO<0>
can be routed through either MFP_PIN_GPIO0 as well as MFP_PIN_GPIO0_2,
see arch/arm/mach-pxa/mach/include/mfp-pxa300.h)
2. Alternate function configuration is removed from this GPIO controller,
the remaining functions are pure GPIO-specific, i.e.
- GPIO signal level control
- GPIO direction control
- GPIO level change detection
3. Low power state for each pin is now controlled by MFP, this means the
PGSRx registers on PXA2xx are now useless on PXA3xx
4. Wakeup detection is now controlled by MFP, PWER does not control the
wakeup from GPIO(s) any more, depending on the sleeping state, ADxER
(as defined in pxa3xx-regs.h) controls the wakeup from MFP
NOTE: with such a clear separation of MFP and GPIO, by GPIO<xx> we normally
mean it is a GPIO signal, and by MFP<xxx> or pin xxx, we mean a physical
pad (or ball).
MFP API Usage
===============
For board code writers, here are some guidelines:
1. include ONE of the following header files in your <board>.c:
- #include <mach/mfp-pxa25x.h>
- #include <mach/mfp-pxa27x.h>
- #include <mach/mfp-pxa300.h>
- #include <mach/mfp-pxa320.h>
- #include <mach/mfp-pxa930.h>
NOTE: only one file in your <board>.c, depending on the processors used,
because pin configuration definitions may conflict in these file (i.e.
same name, different meaning and settings on different processors). E.g.
for zylonite platform, which support both PXA300/PXA310 and PXA320, two
separate files are introduced: zylonite_pxa300.c and zylonite_pxa320.c
(in addition to handle MFP configuration differences, they also handle
the other differences between the two combinations).
NOTE: PXA300 and PXA310 are almost identical in pin configurations (with
PXA310 supporting some additional ones), thus the difference is actually
covered in a single mfp-pxa300.h.
2. prepare an array for the initial pin configurations, e.g.:
static unsigned long mainstone_pin_config[] __initdata = {
/* Chip Select */
GPIO15_nCS_1,
/* LCD - 16bpp Active TFT */
GPIOxx_TFT_LCD_16BPP,
GPIO16_PWM0_OUT, /* Backlight */
/* MMC */
GPIO32_MMC_CLK,
GPIO112_MMC_CMD,
GPIO92_MMC_DAT_0,
GPIO109_MMC_DAT_1,
GPIO110_MMC_DAT_2,
GPIO111_MMC_DAT_3,
...
/* GPIO */
GPIO1_GPIO | WAKEUP_ON_EDGE_BOTH,
};
a) once the pin configurations are passed to pxa{2xx,3xx}_mfp_config(),
and written to the actual registers, they are useless and may discard,
adding '__initdata' will help save some additional bytes here.
b) when there is only one possible pin configurations for a component,
some simplified definitions can be used, e.g. GPIOxx_TFT_LCD_16BPP on
PXA25x and PXA27x processors
c) if by board design, a pin can be configured to wake up the system
from low power state, it can be 'OR'ed with any of:
WAKEUP_ON_EDGE_BOTH
WAKEUP_ON_EDGE_RISE
WAKEUP_ON_EDGE_FALL
WAKEUP_ON_LEVEL_HIGH - specifically for enabling of keypad GPIOs,
to indicate that this pin has the capability of wake-up the system,
and on which edge(s). This, however, doesn't necessarily mean the
pin _will_ wakeup the system, it will only when set_irq_wake() is
invoked with the corresponding GPIO IRQ (GPIO_IRQ(xx) or gpio_to_irq())
and eventually calls gpio_set_wake() for the actual register setting.
d) although PXA3xx MFP supports edge detection on each pin, the
internal logic will only wakeup the system when those specific bits
in ADxER registers are set, which can be well mapped to the
corresponding peripheral, thus set_irq_wake() can be called with
the peripheral IRQ to enable the wakeup.
MFP on PXA3xx
===============
Every external I/O pad on PXA3xx (excluding those for special purpose) has
one MFP logic associated, and is controlled by one MFP register (MFPR).
The MFPR has the following bit definitions (for PXA300/PXA310/PXA320):
31 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+-------------------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| RESERVED |PS|PU|PD| DRIVE |SS|SD|SO|EC|EF|ER|--| AF_SEL |
+-------------------------+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Bit 3: RESERVED
Bit 4: EDGE_RISE_EN - enable detection of rising edge on this pin
Bit 5: EDGE_FALL_EN - enable detection of falling edge on this pin
Bit 6: EDGE_CLEAR - disable edge detection on this pin
Bit 7: SLEEP_OE_N - enable outputs during low power modes
Bit 8: SLEEP_DATA - output data on the pin during low power modes
Bit 9: SLEEP_SEL - selection control for low power modes signals
Bit 13: PULLDOWN_EN - enable the internal pull-down resistor on this pin
Bit 14: PULLUP_EN - enable the internal pull-up resistor on this pin
Bit 15: PULL_SEL - pull state controlled by selected alternate function
(0) or by PULL{UP,DOWN}_EN bits (1)
Bit 0 - 2: AF_SEL - alternate function selection, 8 possibilities, from 0-7
Bit 10-12: DRIVE - drive strength and slew rate
0b000 - fast 1mA
0b001 - fast 2mA
0b002 - fast 3mA
0b003 - fast 4mA
0b004 - slow 6mA
0b005 - fast 6mA
0b006 - slow 10mA
0b007 - fast 10mA
MFP Design for PXA2xx/PXA3xx
==============================
Due to the difference of pin-mux handling between PXA2xx and PXA3xx, a unified
MFP API is introduced to cover both series of processors.
The basic idea of this design is to introduce definitions for all possible pin
configurations, these definitions are processor and platform independent, and
the actual API invoked to convert these definitions into register settings and
make them effective there-after.
Files Involved
--------------
- arch/arm/mach-pxa/include/mach/mfp.h
for
1. Unified pin definitions - enum constants for all configurable pins
2. processor-neutral bit definitions for a possible MFP configuration
- arch/arm/mach-pxa/include/mach/mfp-pxa3xx.h
for PXA3xx specific MFPR register bit definitions and PXA3xx common pin
configurations
- arch/arm/mach-pxa/include/mach/mfp-pxa2xx.h
for PXA2xx specific definitions and PXA25x/PXA27x common pin configurations
- arch/arm/mach-pxa/include/mach/mfp-pxa25x.h
arch/arm/mach-pxa/include/mach/mfp-pxa27x.h
arch/arm/mach-pxa/include/mach/mfp-pxa300.h
arch/arm/mach-pxa/include/mach/mfp-pxa320.h
arch/arm/mach-pxa/include/mach/mfp-pxa930.h
for processor specific definitions
- arch/arm/mach-pxa/mfp-pxa3xx.c
- arch/arm/mach-pxa/mfp-pxa2xx.c
for implementation of the pin configuration to take effect for the actual
processor.
Pin Configuration
-----------------
The following comments are copied from mfp.h (see the actual source code
for most updated info)
/*
* a possible MFP configuration is represented by a 32-bit integer
*
* bit 0.. 9 - MFP Pin Number (1024 Pins Maximum)
* bit 10..12 - Alternate Function Selection
* bit 13..15 - Drive Strength
* bit 16..18 - Low Power Mode State
* bit 19..20 - Low Power Mode Edge Detection
* bit 21..22 - Run Mode Pull State
*
* to facilitate the definition, the following macros are provided
*
* MFP_CFG_DEFAULT - default MFP configuration value, with
* alternate function = 0,
* drive strength = fast 3mA (MFP_DS03X)
* low power mode = default
* edge detection = none
*
* MFP_CFG - default MFPR value with alternate function
* MFP_CFG_DRV - default MFPR value with alternate function and
* pin drive strength
* MFP_CFG_LPM - default MFPR value with alternate function and
* low power mode
* MFP_CFG_X - default MFPR value with alternate function,
* pin drive strength and low power mode
*/
Examples of pin configurations are:
#define GPIO94_SSP3_RXD MFP_CFG_X(GPIO94, AF1, DS08X, FLOAT)
which reads GPIO94 can be configured as SSP3_RXD, with alternate function
selection of 1, driving strength of 0b101, and a float state in low power
modes.
NOTE: this is the default setting of this pin being configured as SSP3_RXD
which can be modified a bit in board code, though it is not recommended to
do so, simply because this default setting is usually carefully encoded,
and is supposed to work in most cases.
Register Settings
-----------------
Register settings on PXA3xx for a pin configuration is actually very
straight-forward, most bits can be converted directly into MFPR value
in a easier way. Two sets of MFPR values are calculated: the run-time
ones and the low power mode ones, to allow different settings.
The conversion from a generic pin configuration to the actual register
settings on PXA2xx is a bit complicated: many registers are involved,
including GAFRx, GPDRx, PGSRx, PWER, PKWR, PFER and PRER. Please see
mfp-pxa2xx.c for how the conversion is made.
Documentation/block/biodoc.txt
浏览文件 @ 923a789b
......@@ -914,7 +914,7 @@ I/O scheduler, a.k.a. elevator, is implemented in two layers. Generic dispatch
queue and specific I/O schedulers. Unless stated otherwise, elevator is used
to refer to both parts and I/O scheduler to specific I/O schedulers.
Block layer implements generic dispatch queue in ll_rw_blk.c and elevator.c.
Block layer implements generic dispatch queue in block/*.c.
The generic dispatch queue is responsible for properly ordering barrier
requests, requeueing, handling non-fs requests and all other subtleties.
......@@ -926,8 +926,8 @@ be built inside the kernel. Each queue can choose different one and can also
change to another one dynamically.
A block layer call to the i/o scheduler follows the convention elv_xxx(). This
calls elevator_xxx_fn in the elevator switch (drivers/block/elevator.c). Oh,
xxx and xxx might not match exactly, but use your imagination. If an elevator
calls elevator_xxx_fn in the elevator switch (block/elevator.c). Oh, xxx
and xxx might not match exactly, but use your imagination. If an elevator
doesn't implement a function, the switch does nothing or some minimal house
keeping work.
......
Documentation/cpu-hotplug.txt
浏览文件 @ 923a789b
......@@ -50,16 +50,17 @@ additional_cpus=n (*) Use this to limit hotpluggable cpus. This option sets
cpu_possible_map = cpu_present_map + additional_cpus
(*) Option valid only for following architectures
- x86_64, ia64
- ia64
ia64 and x86_64 use the number of disabled local apics in ACPI tables MADT
to determine the number of potentially hot-pluggable cpus. The implementation
should only rely on this to count the # of cpus, but *MUST* not rely on the
apicid values in those tables for disabled apics. In the event BIOS doesn't
mark such hot-pluggable cpus as disabled entries, one could use this
parameter "additional_cpus=x" to represent those cpus in the cpu_possible_map.
ia64 uses the number of disabled local apics in ACPI tables MADT to
determine the number of potentially hot-pluggable cpus. The implementation
should only rely on this to count the # of cpus, but *MUST* not rely
on the apicid values in those tables for disabled apics. In the event
BIOS doesn't mark such hot-pluggable cpus as disabled entries, one could
use this parameter "additional_cpus=x" to represent those cpus in the
cpu_possible_map.
possible_cpus=n [s390 only] use this to set hotpluggable cpus.
possible_cpus=n [s390,x86_64] use this to set hotpluggable cpus.
This option sets possible_cpus bits in
cpu_possible_map. Thus keeping the numbers of bits set
constant even if the machine gets rebooted.
......
Documentation/dvb/technisat.txt 0 → 100644
浏览文件 @ 923a789b
How to set up the Technisat devices
===================================
1) Find out what device you have
================================
First start your linux box with a shipped kernel:
lspci -vvv for a PCI device (lsusb -vvv for an USB device) will show you for example:
02:0b.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 02)
dmesg | grep frontend may show you for example:
DVB: registering frontend 0 (Conexant CX24123/CX24109)...
2) Kernel compilation:
======================
If the Technisat is the only TV device in your box get rid of unnecessary modules and check this one:
"Multimedia devices" => "Customise analog and hybrid tuner modules to build"
In this directory uncheck every driver which is activated there.
Then please activate:
2a) Main module part:
a.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters"
b.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC PCI" in case of a PCI card OR
c.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Technisat/B2C2 Air/Sky/Cable2PC USB" in case of an USB 1.1 adapter
d.)"Multimedia devices" => "DVB/ATSC adapters" => "Technisat/B2C2 FlexcopII(b) and FlexCopIII adapters" => "Enable debug for the B2C2 FlexCop drivers"
Notice: d.) is helpful for troubleshooting
2b) Frontend module part:
1.) Revision 2.3:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "Zarlink VP310/MT312/ZL10313 based"
2.) Revision 2.6:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "ST STV0299 based"
3.) Revision 2.7:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "Samsung S5H1420 based"
c.)"Multimedia devices" => "Customise DVB frontends" => "Integrant ITD1000 Zero IF tuner for DVB-S/DSS"
d.)"Multimedia devices" => "Customise DVB frontends" => "ISL6421 SEC controller"
4.) Revision 2.8:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "Conexant CX24113/CX24128 tuner for DVB-S/DSS"
c.)"Multimedia devices" => "Customise DVB frontends" => "Conexant CX24123 based"
d.)"Multimedia devices" => "Customise DVB frontends" => "ISL6421 SEC controller"
5.) DVB-T card:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "Zarlink MT352 based"
6.) DVB-C card:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "ST STV0297 based"
7.) ATSC card 1st generation:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "Broadcom BCM3510"
8.) ATSC card 2nd generation:
a.)"Multimedia devices" => "Customise DVB frontends" => "Customise the frontend modules to build"
b.)"Multimedia devices" => "Customise DVB frontends" => "NxtWave Communications NXT2002/NXT2004 based"
c.)"Multimedia devices" => "Customise DVB frontends" => "LG Electronics LGDT3302/LGDT3303 based"
Author: Uwe Bugla <uwe.bugla@gmx.de> December 2008
Documentation/fb/pxafb.txt
浏览文件 @ 923a789b
......@@ -5,9 +5,13 @@ The driver supports the following options, either via
options=<OPTIONS> when modular or video=pxafb:<OPTIONS> when built in.
For example:
modprobe pxafb options=mode:640x480-8,passive
modprobe pxafb options=vmem:2M,mode:640x480-8,passive
or on the kernel command line
video=pxafb:mode:640x480-8,passive
video=pxafb:vmem:2M,mode:640x480-8,passive
vmem: VIDEO_MEM_SIZE
Amount of video memory to allocate (can be suffixed with K or M
for kilobytes or megabytes)
mode:XRESxYRES[-BPP]
XRES == LCCR1_PPL + 1
......@@ -52,3 +56,87 @@ outputen:POLARITY
pixclockpol:POLARITY
pixel clock polarity
0 => falling edge, 1 => rising edge
Overlay Support for PXA27x and later LCD controllers
====================================================
PXA27x and later processors support overlay1 and overlay2 on-top of the
base framebuffer (although under-neath the base is also possible). They
support palette and no-palette RGB formats, as well as YUV formats (only
available on overlay2). These overlays have dedicated DMA channels and
behave in a similar way as a framebuffer.
However, there are some differences between these overlay framebuffers
and normal framebuffers, as listed below:
1. overlay can start at a 32-bit word aligned position within the base
framebuffer, which means they have a start (x, y). This information
is encoded into var->nonstd (no, var->xoffset and var->yoffset are
not for such purpose).
2. overlay framebuffer is allocated dynamically according to specified
'struct fb_var_screeninfo', the amount is decided by:
var->xres_virtual * var->yres_virtual * bpp
bpp = 16 -- for RGB565 or RGBT555
= 24 -- for YUV444 packed
= 24 -- for YUV444 planar
= 16 -- for YUV422 planar (1 pixel = 1 Y + 1/2 Cb + 1/2 Cr)
= 12 -- for YUV420 planar (1 pixel = 1 Y + 1/4 Cb + 1/4 Cr)
NOTE:
a. overlay does not support panning in x-direction, thus
var->xres_virtual will always be equal to var->xres
b. line length of overlay(s) must be on a 32-bit word boundary,
for YUV planar modes, it is a requirement for the component
with minimum bits per pixel, e.g. for YUV420, Cr component
for one pixel is actually 2-bits, it means the line length
should be a multiple of 16-pixels
c. starting horizontal position (XPOS) should start on a 32-bit
word boundary, otherwise the fb_check_var() will just fail.
d. the rectangle of the overlay should be within the base plane,
otherwise fail
Applications should follow the sequence below to operate an overlay
framebuffer:
a. open("/dev/fb[1-2]", ...)
b. ioctl(fd, FBIOGET_VSCREENINFO, ...)
c. modify 'var' with desired parameters:
1) var->xres and var->yres
2) larger var->yres_virtual if more memory is required,
usually for double-buffering
3) var->nonstd for starting (x, y) and color format
4) var->{red, green, blue, transp} if RGB mode is to be used
d. ioctl(fd, FBIOPUT_VSCREENINFO, ...)
e. ioctl(fd, FBIOGET_FSCREENINFO, ...)
f. mmap
g. ...
3. for YUV planar formats, these are actually not supported within the
framebuffer framework, application has to take care of the offsets
and lengths of each component within the framebuffer.
4. var->nonstd is used to pass starting (x, y) position and color format,
the detailed bit fields are shown below:
31 23 20 10 0
+-----------------+---+----------+----------+
| ... unused ... |FOR| XPOS | YPOS |
+-----------------+---+----------+----------+
FOR - color format, as defined by OVERLAY_FORMAT_* in pxafb.h
0 - RGB
1 - YUV444 PACKED
2 - YUV444 PLANAR
3 - YUV422 PLANAR
4 - YUR420 PLANAR
XPOS - starting horizontal position
YPOS - starting vertical position
Documentation/feature-removal-schedule.txt
浏览文件 @ 923a789b
......@@ -310,15 +310,6 @@ Who: Krzysztof Piotr Oledzki <ole@ans.pl>
---------------------------
What: ide-scsi (BLK_DEV_IDESCSI)
When: 2.6.29
Why: The 2.6 kernel supports direct writing to ide CD drives, which
eliminates the need for ide-scsi. The new method is more
efficient in every way.
Who: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
---------------------------
What: i2c_attach_client(), i2c_detach_client(), i2c_driver->detach_client()
When: 2.6.29 (ideally) or 2.6.30 (more likely)
Why: Deprecated by the new (standard) device driver binding model. Use
......
Documentation/filesystems/Locking
浏览文件 @ 923a789b
......@@ -394,7 +394,6 @@ prototypes:
unsigned long (*get_unmapped_area)(struct file *, unsigned long,
unsigned long, unsigned long, unsigned long);
int (*check_flags)(int);
int (*dir_notify)(struct file *, unsigned long);
};
locking rules:
......@@ -424,7 +423,6 @@ sendfile: no
sendpage: no
get_unmapped_area: no
check_flags: no
dir_notify: no
->llseek() locking has moved from llseek to the individual llseek
implementations. If your fs is not using generic_file_llseek, you
......
Documentation/filesystems/devpts.txt 0 → 100644
浏览文件 @ 923a789b
To support containers, we now allow multiple instances of devpts filesystem,
such that indices of ptys allocated in one instance are independent of indices
allocated in other instances of devpts.
To preserve backward compatibility, this support for multiple instances is
enabled only if:
- CONFIG_DEVPTS_MULTIPLE_INSTANCES=y, and
- '-o newinstance' mount option is specified while mounting devpts
IOW, devpts now supports both single-instance and multi-instance semantics.
If CONFIG_DEVPTS_MULTIPLE_INSTANCES=n, there is no change in behavior and
this referred to as the "legacy" mode. In this mode, the new mount options
(-o newinstance and -o ptmxmode) will be ignored with a 'bogus option' message
on console.
If CONFIG_DEVPTS_MULTIPLE_INSTANCES=y and devpts is mounted without the
'newinstance' option (as in current start-up scripts) the new mount binds
to the initial kernel mount of devpts. This mode is referred to as the
'single-instance' mode and the current, single-instance semantics are
preserved, i.e PTYs are common across the system.
The only difference between this single-instance mode and the legacy mode
is the presence of new, '/dev/pts/ptmx' node with permissions 0000, which
can safely be ignored.
If CONFIG_DEVPTS_MULTIPLE_INSTANCES=y and 'newinstance' option is specified,
the mount is considered to be in the multi-instance mode and a new instance
of the devpts fs is created. Any ptys created in this instance are independent
of ptys in other instances of devpts. Like in the single-instance mode, the
/dev/pts/ptmx node is present. To effectively use the multi-instance mode,
open of /dev/ptmx must be a redirected to '/dev/pts/ptmx' using a symlink or
bind-mount.
Eg: A container startup script could do the following:
$ chmod 0666 /dev/pts/ptmx
$ rm /dev/ptmx
$ ln -s pts/ptmx /dev/ptmx
$ ns_exec -cm /bin/bash
# We are now in new container
$ umount /dev/pts
$ mount -t devpts -o newinstance lxcpts /dev/pts
$ sshd -p 1234
where 'ns_exec -cm /bin/bash' calls clone() with CLONE_NEWNS flag and execs
/bin/bash in the child process. A pty created by the sshd is not visible in
the original mount of /dev/pts.
User-space changes
------------------
In multi-instance mode (i.e '-o newinstance' mount option is specified at least
once), following user-space issues should be noted.
1. If -o newinstance mount option is never used, /dev/pts/ptmx can be ignored
and no change is needed to system-startup scripts.
2. To effectively use multi-instance mode (i.e -o newinstance is specified)
administrators or startup scripts should "redirect" open of /dev/ptmx to
/dev/pts/ptmx using either a bind mount or symlink.
$ mount -t devpts -o newinstance devpts /dev/pts
followed by either
$ rm /dev/ptmx
$ ln -s pts/ptmx /dev/ptmx
$ chmod 666 /dev/pts/ptmx
or
$ mount -o bind /dev/pts/ptmx /dev/ptmx
3. The '/dev/ptmx -> pts/ptmx' symlink is the preferred method since it
enables better error-reporting and treats both single-instance and
multi-instance mounts similarly.
But this method requires that system-startup scripts set the mode of
/dev/pts/ptmx correctly (default mode is 0000). The scripts can set the
mode by, either
- adding ptmxmode mount option to devpts entry in /etc/fstab, or
- using 'chmod 0666 /dev/pts/ptmx'
4. If multi-instance mode mount is needed for containers, but the system
startup scripts have not yet been updated, container-startup scripts
should bind mount /dev/ptmx to /dev/pts/ptmx to avoid breaking single-
instance mounts.
Or, in general, container-startup scripts should use:
mount -t devpts -o newinstance -o ptmxmode=0666 devpts /dev/pts
if [ ! -L /dev/ptmx ]; then
mount -o bind /dev/pts/ptmx /dev/ptmx
fi
When all devpts mounts are multi-instance, /dev/ptmx can permanently be
a symlink to pts/ptmx and the bind mount can be ignored.
5. A multi-instance mount that is not accompanied by the /dev/ptmx to
/dev/pts/ptmx redirection would result in an unusable/unreachable pty.
mount -t devpts -o newinstance lxcpts /dev/pts
immediately followed by:
open("/dev/ptmx")
would create a pty, say /dev/pts/7, in the initial kernel mount.
But /dev/pts/7 would be invisible in the new mount.
6. The permissions for /dev/pts/ptmx node should be specified when mounting
/dev/pts, using the '-o ptmxmode=%o' mount option (default is 0000).
mount -t devpts -o newinstance -o ptmxmode=0644 devpts /dev/pts
The permissions can be later be changed as usual with 'chmod'.
chmod 666 /dev/pts/ptmx
7. A mount of devpts without the 'newinstance' option results in binding to
initial kernel mount. This behavior while preserving legacy semantics,
does not provide strict isolation in a container environment. i.e by
mounting devpts without the 'newinstance' option, a container could
get visibility into the 'host' or root container's devpts.
To workaround this and have strict isolation, all mounts of devpts,
including the mount in the root container, should use the newinstance
option.
Documentation/filesystems/files.txt
浏览文件 @ 923a789b
......@@ -76,13 +76,13 @@ the fdtable structure -
5. Handling of the file structures is special. Since the look-up
of the fd (fget()/fget_light()) are lock-free, it is possible
that look-up may race with the last put() operation on the
file structure. This is avoided using atomic_inc_not_zero()
file structure. This is avoided using atomic_long_inc_not_zero()
on ->f_count :
rcu_read_lock();
file = fcheck_files(files, fd);
if (file) {
if (atomic_inc_not_zero(&file->f_count))
if (atomic_long_inc_not_zero(&file->f_count))
*fput_needed = 1;
else
/* Didn't get the reference, someone's freed */
......@@ -92,7 +92,7 @@ the fdtable structure -
....
return file;
atomic_inc_not_zero() detects if refcounts is already zero or
atomic_long_inc_not_zero() detects if refcounts is already zero or
goes to zero during increment. If it does, we fail
fget()/fget_light().
......
Documentation/filesystems/vfs.txt
浏览文件 @ 923a789b
......@@ -733,7 +733,6 @@ struct file_operations {
ssize_t (*sendpage) (struct file *, struct page *, int, size_t, loff_t *, int);
unsigned long (*get_unmapped_area)(struct file *, unsigned long, unsigned long, unsigned long, unsigned long);
int (*check_flags)(int);
int (*dir_notify)(struct file *filp, unsigned long arg);
int (*flock) (struct file *, int, struct file_lock *);
ssize_t (*splice_write)(struct pipe_inode_info *, struct file *, size_t, unsigned int);
ssize_t (*splice_read)(struct file *, struct pipe_inode_info *, size_t, unsigned int);
......@@ -800,8 +799,6 @@ otherwise noted.
check_flags: called by the fcntl(2) system call for F_SETFL command
dir_notify: called by the fcntl(2) system call for F_NOTIFY command
flock: called by the flock(2) system call
splice_write: called by the VFS to splice data from a pipe to a file. This
......@@ -931,7 +928,7 @@ manipulate dentries:
d_lookup: look up a dentry given its parent and path name component
It looks up the child of that given name from the dcache
hash table. If it is found, the reference count is incremented
and the dentry is returned. The caller must use d_put()
and the dentry is returned. The caller must use dput()
to free the dentry when it finishes using it.
For further information on dentry locking, please refer to the document
......
Documentation/filesystems/xfs.txt
浏览文件 @ 923a789b
......@@ -229,10 +229,6 @@ The following sysctls are available for the XFS filesystem:
ISGID bit is cleared if the irix_sgid_inherit compatibility sysctl
is set.
fs.xfs.restrict_chown (Min: 0 Default: 1 Max: 1)
Controls whether unprivileged users can use chown to "give away"
a file to another user.
fs.xfs.inherit_sync (Min: 0 Default: 1 Max: 1)
Setting this to "1" will cause the "sync" flag set
by the xfs_io(8) chattr command on a directory to be
......
Documentation/lguest/lguest.c
浏览文件 @ 923a789b
......@@ -481,51 +481,6 @@ static unsigned long load_initrd(const char *name, unsigned long mem)
/* We return the initrd size. */
return len;
}
/* Once we know how much memory we have we can construct simple linear page
* tables which set virtual == physical which will get the Guest far enough
* into the boot to create its own.
*
* We lay them out of the way, just below the initrd (which is why we need to
* know its size here). */
static unsigned long setup_pagetables(unsigned long mem,
unsigned long initrd_size)
{
unsigned long *pgdir, *linear;
unsigned int mapped_pages, i, linear_pages;
unsigned int ptes_per_page = getpagesize()/sizeof(void *);
mapped_pages = mem/getpagesize();
/* Each PTE page can map ptes_per_page pages: how many do we need? */
linear_pages = (mapped_pages + ptes_per_page-1)/ptes_per_page;
/* We put the toplevel page directory page at the top of memory. */
pgdir = from_guest_phys(mem) - initrd_size - getpagesize();
/* Now we use the next linear_pages pages as pte pages */
linear = (void *)pgdir - linear_pages*getpagesize();
/* Linear mapping is easy: put every page's address into the mapping in
* order. PAGE_PRESENT contains the flags Present, Writable and
* Executable. */
for (i = 0; i < mapped_pages; i++)
linear[i] = ((i * getpagesize()) | PAGE_PRESENT);
/* The top level points to the linear page table pages above. */
for (i = 0; i < mapped_pages; i += ptes_per_page) {
pgdir[i/ptes_per_page]
= ((to_guest_phys(linear) + i*sizeof(void *))
| PAGE_PRESENT);
}
verbose("Linear mapping of %u pages in %u pte pages at %#lx\n",
mapped_pages, linear_pages, to_guest_phys(linear));
/* We return the top level (guest-physical) address: the kernel needs
* to know where it is. */
return to_guest_phys(pgdir);
}
/*:*/
/* Simple routine to roll all the commandline arguments together with spaces
......@@ -548,13 +503,13 @@ static void concat(char *dst, char *args[])
/*L:185 This is where we actually tell the kernel to initialize the Guest. We
* saw the arguments it expects when we looked at initialize() in lguest_user.c:
* the base of Guest "physical" memory, the top physical page to allow, the
* top level pagetable and the entry point for the Guest. */
static int tell_kernel(unsigned long pgdir, unsigned long start)
* the base of Guest "physical" memory, the top physical page to allow and the
* entry point for the Guest. */
static int tell_kernel(unsigned long start)
{
unsigned long args[] = { LHREQ_INITIALIZE,
(unsigned long)guest_base,
guest_limit / getpagesize(), pgdir, start };
guest_limit / getpagesize(), start };
int fd;
verbose("Guest: %p - %p (%#lx)\n",
......@@ -1030,7 +985,7 @@ static void update_device_status(struct device *dev)
/* Zero out the virtqueues. */
for (vq = dev->vq; vq; vq = vq->next) {
memset(vq->vring.desc, 0,
vring_size(vq->config.num, getpagesize()));
vring_size(vq->config.num, LGUEST_VRING_ALIGN));
lg_last_avail(vq) = 0;
}
} else if (dev->desc->status & VIRTIO_CONFIG_S_FAILED) {
......@@ -1211,7 +1166,7 @@ static void add_virtqueue(struct device *dev, unsigned int num_descs,
void *p;
/* First we need some memory for this virtqueue. */
pages = (vring_size(num_descs, getpagesize()) + getpagesize() - 1)
pages = (vring_size(num_descs, LGUEST_VRING_ALIGN) + getpagesize() - 1)
/ getpagesize();
p = get_pages(pages);
......@@ -1228,7 +1183,7 @@ static void add_virtqueue(struct device *dev, unsigned int num_descs,
vq->config.pfn = to_guest_phys(p) / getpagesize();
/* Initialize the vring. */
vring_init(&vq->vring, num_descs, p, getpagesize());
vring_init(&vq->vring, num_descs, p, LGUEST_VRING_ALIGN);
/* Append virtqueue to this device's descriptor. We use
* device_config() to get the end of the device's current virtqueues;
......@@ -1941,7 +1896,7 @@ int main(int argc, char *argv[])
{
/* Memory, top-level pagetable, code startpoint and size of the
* (optional) initrd. */
unsigned long mem = 0, pgdir, start, initrd_size = 0;
unsigned long mem = 0, start, initrd_size = 0;
/* Two temporaries and the /dev/lguest file descriptor. */
int i, c, lguest_fd;
/* The boot information for the Guest. */
......@@ -2040,9 +1995,6 @@ int main(int argc, char *argv[])
boot->hdr.type_of_loader = 0xFF;
}
/* Set up the initial linear pagetables, starting below the initrd. */
pgdir = setup_pagetables(mem, initrd_size);
/* The Linux boot header contains an "E820" memory map: ours is a
* simple, single region. */
boot->e820_entries = 1;
......@@ -2064,7 +2016,7 @@ int main(int argc, char *argv[])
/* We tell the kernel to initialize the Guest: this returns the open
* /dev/lguest file descriptor. */
lguest_fd = tell_kernel(pgdir, start);
lguest_fd = tell_kernel(start);
/* We clone off a thread, which wakes the Launcher whenever one of the
* input file descriptors needs attention. We call this the Waker, and
......
Documentation/lockstat.txt
浏览文件 @ 923a789b
......@@ -71,35 +71,50 @@ Look at the current lock statistics:
# less /proc/lock_stat
01 lock_stat version 0.2
01 lock_stat version 0.3
02 -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
03 class name con-bounces contentions waittime-min waittime-max waittime-total acq-bounces acquisitions holdtime-min holdtime-max holdtime-total
04 -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
05
06 &inode->i_data.tree_lock-W: 15 21657 0.18 1093295.30 11547131054.85 58 10415 0.16 87.51 6387.60
07 &inode->i_data.tree_lock-R: 0 0 0.00 0.00 0.00 23302 231198 0.25 8.45 98023.38
08 --------------------------
09 &inode->i_data.tree_lock 0 [<ffffffff8027c08f>] add_to_page_cache+0x5f/0x190
10
11 ...............................................................................................................................................................................................
12
13 dcache_lock: 1037 1161 0.38 45.32 774.51 6611 243371 0.15 306.48 77387.24
14 -----------
15 dcache_lock 180 [<ffffffff802c0d7e>] sys_getcwd+0x11e/0x230
16 dcache_lock 165 [<ffffffff802c002a>] d_alloc+0x15a/0x210
17 dcache_lock 33 [<ffffffff8035818d>] _atomic_dec_and_lock+0x4d/0x70
18 dcache_lock 1 [<ffffffff802beef8>] shrink_dcache_parent+0x18/0x130
06 &mm->mmap_sem-W: 233 538 18446744073708 22924.27 607243.51 1342 45806 1.71 8595.89 1180582.34
07 &mm->mmap_sem-R: 205 587 18446744073708 28403.36 731975.00 1940 412426 0.58 187825.45 6307502.88
08 ---------------
09 &mm->mmap_sem 487 [<ffffffff8053491f>] do_page_fault+0x466/0x928
10 &mm->mmap_sem 179 [<ffffffff802a6200>] sys_mprotect+0xcd/0x21d
11 &mm->mmap_sem 279 [<ffffffff80210a57>] sys_mmap+0x75/0xce
12 &mm->mmap_sem 76 [<ffffffff802a490b>] sys_munmap+0x32/0x59
13 ---------------
14 &mm->mmap_sem 270 [<ffffffff80210a57>] sys_mmap+0x75/0xce
15 &mm->mmap_sem 431 [<ffffffff8053491f>] do_page_fault+0x466/0x928
16 &mm->mmap_sem 138 [<ffffffff802a490b>] sys_munmap+0x32/0x59
17 &mm->mmap_sem 145 [<ffffffff802a6200>] sys_mprotect+0xcd/0x21d
18
19 ...............................................................................................................................................................................................
20
21 dcache_lock: 621 623 0.52 118.26 1053.02 6745 91930 0.29 316.29 118423.41
22 -----------
23 dcache_lock 179 [<ffffffff80378274>] _atomic_dec_and_lock+0x34/0x54
24 dcache_lock 113 [<ffffffff802cc17b>] d_alloc+0x19a/0x1eb
25 dcache_lock 99 [<ffffffff802ca0dc>] d_rehash+0x1b/0x44
26 dcache_lock 104 [<ffffffff802cbca0>] d_instantiate+0x36/0x8a
27 -----------
28 dcache_lock 192 [<ffffffff80378274>] _atomic_dec_and_lock+0x34/0x54
29 dcache_lock 98 [<ffffffff802ca0dc>] d_rehash+0x1b/0x44
30 dcache_lock 72 [<ffffffff802cc17b>] d_alloc+0x19a/0x1eb
31 dcache_lock 112 [<ffffffff802cbca0>] d_instantiate+0x36/0x8a
This excerpt shows the first two lock class statistics. Line 01 shows the
output version - each time the format changes this will be updated. Line 02-04
show the header with column descriptions. Lines 05-10 and 13-18 show the actual
show the header with column descriptions. Lines 05-18 and 20-31 show the actual
statistics. These statistics come in two parts; the actual stats separated by a
short separator (line 08, 14) from the contention points.
short separator (line 08, 13) from the contention points.
The first lock (05-10) is a read/write lock, and shows two lines above the
The first lock (05-18) is a read/write lock, and shows two lines above the
short separator. The contention points don't match the column descriptors,
they have two: contentions and [<IP>] symbol.
they have two: contentions and [<IP>] symbol. The second set of contention
points are the points we're contending with.
The integer part of the time values is in us.
View the top contending locks:
......
Documentation/scsi/cxgb3i.txt 0 → 100644
浏览文件 @ 923a789b
Chelsio S3 iSCSI Driver for Linux
Introduction
============
The Chelsio T3 ASIC based Adapters (S310, S320, S302, S304, Mezz cards, etc.
series of products) supports iSCSI acceleration and iSCSI Direct Data Placement
(DDP) where the hardware handles the expensive byte touching operations, such
as CRC computation and verification, and direct DMA to the final host memory
destination:
- iSCSI PDU digest generation and verification
On transmitting, Chelsio S3 h/w computes and inserts the Header and
Data digest into the PDUs.
On receiving, Chelsio S3 h/w computes and verifies the Header and
Data digest of the PDUs.
- Direct Data Placement (DDP)
S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
payload into pre-posted final destination host-memory buffers based
on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
in Data-Out PDUs.
- PDU Transmit and Recovery
On transmitting, S3 h/w accepts the complete PDU (header + data)
from the host driver, computes and inserts the digests, decomposes
the PDU into multiple TCP segments if necessary, and transmit all
the TCP segments onto the wire. It handles TCP retransmission if
needed.
On receving, S3 h/w recovers the iSCSI PDU by reassembling TCP
segments, separating the header and data, calculating and verifying
the digests, then forwards the header to the host. The payload data,
if possible, will be directly placed into the pre-posted host DDP
buffer. Otherwise, the payload data will be sent to the host too.
The cxgb3i driver interfaces with open-iscsi initiator and provides the iSCSI
acceleration through Chelsio hardware wherever applicable.
Using the cxgb3i Driver
=======================
The following steps need to be taken to accelerates the open-iscsi initiator:
1. Load the cxgb3i driver: "modprobe cxgb3i"
The cxgb3i module registers a new transport class "cxgb3i" with open-iscsi.
* in the case of recompiling the kernel, the cxgb3i selection is located at
Device Drivers
SCSI device support --->
[*] SCSI low-level drivers --->
<M> Chelsio S3xx iSCSI support
2. Create an interface file located under /etc/iscsi/ifaces/ for the new
transport class "cxgb3i".
The content of the file should be in the following format:
iface.transport_name = cxgb3i
iface.net_ifacename = <ethX>
iface.ipaddress = <iscsi ip address>
* if iface.ipaddress is specified, <iscsi ip address> needs to be either the
same as the ethX's ip address or an address on the same subnet. Make
sure the ip address is unique in the network.
3. edit /etc/iscsi/iscsid.conf
The default setting for MaxRecvDataSegmentLength (131072) is too big,
replace "node.conn[0].iscsi.MaxRecvDataSegmentLength" to be a value no
bigger than 15360 (for example 8192):
node.conn[0].iscsi.MaxRecvDataSegmentLength = 8192
* The login would fail for a normal session if MaxRecvDataSegmentLength is
too big. A error message in the format of
"cxgb3i: ERR! MaxRecvSegmentLength <X> too big. Need to be <= <Y>."
would be logged to dmesg.
4. To direct open-iscsi traffic to go through cxgb3i's accelerated path,
"-I <iface file name>" option needs to be specified with most of the
iscsiadm command. <iface file name> is the transport interface file created
in step 2.
Documentation/usb/wusb-cbaf
浏览文件 @ 923a789b
......@@ -80,12 +80,6 @@ case $1 in
start)
for dev in ${2:-$hdevs}
do
uwb_rc=$(readlink -f $dev/uwb_rc)
if cat $uwb_rc/beacon | grep -q -- "-1"
then
echo 13 0 > $uwb_rc/beacon
echo I: started beaconing on ch 13 on $(basename $uwb_rc) >&2
fi
echo $host_CHID > $dev/wusb_chid
echo I: started host $(basename $dev) >&2
done
......@@ -95,9 +89,6 @@ case $1 in
do
echo 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > $dev/wusb_chid
echo I: stopped host $(basename $dev) >&2
uwb_rc=$(readlink -f $dev/uwb_rc)
echo -1 | cat > $uwb_rc/beacon
echo I: stopped beaconing on $(basename $uwb_rc) >&2
done
;;
set-chid)
......
Documentation/video4linux/API.html
浏览文件 @ 923a789b
<TITLE>V4L API</TITLE>
<H1>Video For Linux APIs</H1>
<table border=0>
<tr>
<td>
<A HREF=http://www.linuxtv.org/downloads/video4linux/API/V4L1_API.html>
V4L original API</a>
</td><td>
Obsoleted by V4L2 API
</td></tr><tr><td>
<A HREF=http://www.linuxtv.org/downloads/video4linux/API/V4L2_API>
V4L2 API</a>
</td><td>
Should be used for new projects
</td></tr>
</table>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type" />
<title>V4L API</title>
</head>
<body>
<h1>Video For Linux APIs</h1>
<table border="0">
<tr>
<td>
<a href="http://www.linuxtv.org/downloads/video4linux/API/V4L1_API.html">V4L original API</a>
</td>
<td>
Obsoleted by V4L2 API
</td>
</tr>
<tr>
<td>
<a href="http://www.linuxtv.org/downloads/video4linux/API/V4L2_API">V4L2 API</a>
</td>
<td>Should be used for new projects
</td>
</tr>
</table>
</body>
</html>
Documentation/video4linux/CARDLIST.bttv
浏览文件 @ 923a789b
......@@ -104,8 +104,8 @@
103 -> Grand X-Guard / Trust 814PCI [0304:0102]
104 -> Nebula Electronics DigiTV [0071:0101]
105 -> ProVideo PV143 [aa00:1430,aa00:1431,aa00:1432,aa00:1433,aa03:1433]
106 -> PHYTEC VD-009-X1 MiniDIN (bt878)
107 -> PHYTEC VD-009-X1 Combi (bt878)
106 -> PHYTEC VD-009-X1 VD-011 MiniDIN (bt878)
107 -> PHYTEC VD-009-X1 VD-011 Combi (bt878)
108 -> PHYTEC VD-009 MiniDIN (bt878)
109 -> PHYTEC VD-009 Combi (bt878)
110 -> IVC-100 [ff00:a132]
......@@ -151,3 +151,6 @@
150 -> Geovision GV-600 [008a:763c]
151 -> Kozumi KTV-01C
152 -> Encore ENL TV-FM-2 [1000:1801]
153 -> PHYTEC VD-012 (bt878)
154 -> PHYTEC VD-012-X1 (bt878)
155 -> PHYTEC VD-012-X2 (bt878)
Documentation/video4linux/CARDLIST.cx23885
浏览文件 @ 923a789b
......@@ -11,3 +11,4 @@
10 -> DViCO FusionHDTV7 Dual Express [18ac:d618]
11 -> DViCO FusionHDTV DVB-T Dual Express [18ac:db78]
12 -> Leadtek Winfast PxDVR3200 H [107d:6681]
13 -> Compro VideoMate E650F [185b:e800]
Documentation/video4linux/CARDLIST.cx88
浏览文件 @ 923a789b
......@@ -2,7 +2,7 @@
1 -> Hauppauge WinTV 34xxx models [0070:3400,0070:3401]
2 -> GDI Black Gold [14c7:0106,14c7:0107]
3 -> PixelView [1554:4811]
4 -> ATI TV Wonder Pro [1002:00f8]
4 -> ATI TV Wonder Pro [1002:00f8,1002:00f9]
5 -> Leadtek Winfast 2000XP Expert [107d:6611,107d:6613]
6 -> AverTV Studio 303 (M126) [1461:000b]
7 -> MSI TV-@nywhere Master [1462:8606]
......@@ -74,3 +74,6 @@
73 -> TeVii S420 DVB-S [d420:9022]
74 -> Prolink Pixelview Global Extreme [1554:4976]
75 -> PROF 7300 DVB-S/S2 [B033:3033]
76 -> SATTRADE ST4200 DVB-S/S2 [b200:4200]
77 -> TBS 8910 DVB-S [8910:8888]
78 -> Prof 6200 DVB-S [b022:3022]
Documentation/video4linux/CARDLIST.em28xx
浏览文件 @ 923a789b
0 -> Unknown EM2800 video grabber (em2800) [eb1a:2800]
1 -> Unknown EM2750/28xx video grabber (em2820/em2840) [eb1a:2820,eb1a:2860,eb1a:2861,eb1a:2870,eb1a:2881,eb1a:2883]
1 -> Unknown EM2750/28xx video grabber (em2820/em2840) [eb1a:2820,eb1a:2821,eb1a:2860,eb1a:2861,eb1a:2870,eb1a:2881,eb1a:2883]
2 -> Terratec Cinergy 250 USB (em2820/em2840) [0ccd:0036]
3 -> Pinnacle PCTV USB 2 (em2820/em2840) [2304:0208]
4 -> Hauppauge WinTV USB 2 (em2820/em2840) [2040:4200,2040:4201]
......@@ -12,9 +12,9 @@
11 -> Terratec Hybrid XS (em2880) [0ccd:0042]
12 -> Kworld PVR TV 2800 RF (em2820/em2840)
13 -> Terratec Prodigy XS (em2880) [0ccd:0047]
14 -> Pixelview Prolink PlayTV USB 2.0 (em2820/em2840) [eb1a:2821]
14 -> Pixelview Prolink PlayTV USB 2.0 (em2820/em2840)
15 -> V-Gear PocketTV (em2800)
16 -> Hauppauge WinTV HVR 950 (em2883) [2040:6513,2040:6517,2040:651b,2040:651f]
16 -> Hauppauge WinTV HVR 950 (em2883) [2040:6513,2040:6517,2040:651b]
17 -> Pinnacle PCTV HD Pro Stick (em2880) [2304:0227]
18 -> Hauppauge WinTV HVR 900 (R2) (em2880) [2040:6502]
19 -> PointNix Intra-Oral Camera (em2860)
......@@ -27,7 +27,6 @@
26 -> Hercules Smart TV USB 2.0 (em2820/em2840)
27 -> Pinnacle PCTV USB 2 (Philips FM1216ME) (em2820/em2840)
28 -> Leadtek Winfast USB II Deluxe (em2820/em2840)
29 -> Pinnacle Dazzle DVC 100 (em2820/em2840)
30 -> Videology 20K14XUSB USB2.0 (em2820/em2840)
31 -> Usbgear VD204v9 (em2821)
32 -> Supercomp USB 2.0 TV (em2821)
......@@ -57,3 +56,5 @@
56 -> Pinnacle Hybrid Pro (2) (em2882) [2304:0226]
57 -> Kworld PlusTV HD Hybrid 330 (em2883) [eb1a:a316]
58 -> Compro VideoMate ForYou/Stereo (em2820/em2840) [185b:2041]
60 -> Hauppauge WinTV HVR 850 (em2883) [2040:651f]
61 -> Pixelview PlayTV Box 4 USB 2.0 (em2820/em2840)
Documentation/video4linux/CARDLIST.saa7134
浏览文件 @ 923a789b
......@@ -10,7 +10,7 @@
9 -> Medion 5044
10 -> Kworld/KuroutoShikou SAA7130-TVPCI
11 -> Terratec Cinergy 600 TV [153b:1143]
12 -> Medion 7134 [16be:0003]
12 -> Medion 7134 [16be:0003,16be:5000]
13 -> Typhoon TV+Radio 90031
14 -> ELSA EX-VISION 300TV [1048:226b]
15 -> ELSA EX-VISION 500TV [1048:226a]
......@@ -151,3 +151,4 @@
150 -> Zogis Real Angel 220
151 -> ADS Tech Instant HDTV [1421:0380]
152 -> Asus Tiger Rev:1.00 [1043:4857]
153 -> Kworld Plus TV Analog Lite PCI [17de:7128]
Documentation/video4linux/README.cx88
浏览文件 @ 923a789b
cx8800 release notes
====================
......@@ -10,21 +9,20 @@ current status
video
- Basically works.
- Some minor image quality glitches.
- For now only capture, overlay support isn't completed yet.
- For now, only capture and read(). Overlay isn't supported.
audio
- The chip specs for the on-chip TV sound decoder are next
to useless :-/
- Neverless the builtin TV sound decoder starts working now,
at least for PAL-BG. Other TV norms need other code ...
at least for some standards.
FOR ANY REPORTS ON THIS PLEASE MENTION THE TV NORM YOU ARE
USING.
- Most tuner chips do provide mono sound, which may or may not
be useable depending on the board design. With the Hauppauge
cards it works, so there is mono sound available as fallback.
- audio data dma (i.e. recording without loopback cable to the
sound card) should be possible, but there is no code yet ...
sound card) is supported via cx88-alsa.
vbi
- Code present. Works for NTSC closed caption. PAL and other
......
Documentation/video4linux/gspca.txt
浏览文件 @ 923a789b
......@@ -50,9 +50,14 @@ ov519 045e:028c Micro$oft xbox cam
spca508 0461:0815 Micro Innovation IC200
sunplus 0461:0821 Fujifilm MV-1
zc3xx 0461:0a00 MicroInnovation WebCam320
stv06xx 046d:0840 QuickCam Express
stv06xx 046d:0850 LEGO cam / QuickCam Web
stv06xx 046d:0870 Dexxa WebCam USB
spca500 046d:0890 Logitech QuickCam traveler
vc032x 046d:0892 Logitech Orbicam
vc032x 046d:0896 Logitech Orbicam
vc032x 046d:0897 Logitech QuickCam for Dell notebooks
zc3xx 046d:089d Logitech QuickCam E2500
zc3xx 046d:08a0 Logitech QC IM
zc3xx 046d:08a1 Logitech QC IM 0x08A1 +sound
zc3xx 046d:08a2 Labtec Webcam Pro
......@@ -169,6 +174,9 @@ spca500 06bd:0404 Agfa CL20
spca500 06be:0800 Optimedia
sunplus 06d6:0031 Trust 610 LCD PowerC@m Zoom
spca506 06e1:a190 ADS Instant VCD
ov534 06f8:3002 Hercules Blog Webcam
ov534 06f8:3003 Hercules Dualpix HD Weblog
sonixj 06f8:3004 Hercules Classic Silver
spca508 0733:0110 ViewQuest VQ110
spca508 0130:0130 Clone Digital Webcam 11043
spca501 0733:0401 Intel Create and Share
......@@ -199,7 +207,8 @@ sunplus 08ca:2050 Medion MD 41437
sunplus 08ca:2060 Aiptek PocketDV5300
tv8532 0923:010f ICM532 cams
mars 093a:050f Mars-Semi Pc-Camera
pac207 093a:2460 PAC207 Qtec Webcam 100
pac207 093a:2460 Qtec Webcam 100
pac207 093a:2461 HP Webcam
pac207 093a:2463 Philips SPC 220 NC
pac207 093a:2464 Labtec Webcam 1200
pac207 093a:2468 PAC207
......@@ -213,10 +222,13 @@ pac7311 093a:2603 PAC7312
pac7311 093a:2608 Trust WB-3300p
pac7311 093a:260e Gigaware VGA PC Camera, Trust WB-3350p, SIGMA cam 2350
pac7311 093a:260f SnakeCam
pac7311 093a:2620 Apollo AC-905
pac7311 093a:2621 PAC731x
pac7311 093a:2622 Genius Eye 312
pac7311 093a:2624 PAC7302
pac7311 093a:2626 Labtec 2200
pac7311 093a:262a Webcam 300k
pac7311 093a:262c Philips SPC 230 NC
zc3xx 0ac8:0302 Z-star Vimicro zc0302
vc032x 0ac8:0321 Vimicro generic vc0321
vc032x 0ac8:0323 Vimicro Vc0323
......@@ -249,11 +261,13 @@ sonixj 0c45:60c0 Sangha Sn535
sonixj 0c45:60ec SN9C105+MO4000
sonixj 0c45:60fb Surfer NoName
sonixj 0c45:60fc LG-LIC300
sonixj 0c45:60fe Microdia Audio
sonixj 0c45:6128 Microdia/Sonix SNP325
sonixj 0c45:612a Avant Camera
sonixj 0c45:612c Typhoon Rasy Cam 1.3MPix
sonixj 0c45:6130 Sonix Pccam
sonixj 0c45:6138 Sn9c120 Mo4000
sonixj 0c45:613a Microdia Sonix PC Camera
sonixj 0c45:613b Surfer SN-206
sonixj 0c45:613c Sonix Pccam168
sonixj 0c45:6143 Sonix Pccam168
......@@ -263,6 +277,9 @@ etoms 102c:6251 Qcam xxxxxx VGA
zc3xx 10fd:0128 Typhoon Webshot II USB 300k 0x0128
spca561 10fd:7e50 FlyCam Usb 100
zc3xx 10fd:8050 Typhoon Webshot II USB 300k
ov534 1415:2000 Sony HD Eye for PS3 (SLEH 00201)
pac207 145f:013a Trust WB-1300N
vc032x 15b8:6002 HP 2.0 Megapixel rz406aa
spca501 1776:501c Arowana 300K CMOS Camera
t613 17a1:0128 TASCORP JPEG Webcam, NGS Cyclops
vc032x 17ef:4802 Lenovo Vc0323+MI1310_SOC
......
Documentation/video4linux/v4l2-framework.txt 0 → 100644
浏览文件 @ 923a789b
Overview of the V4L2 driver framework
=====================================
This text documents the various structures provided by the V4L2 framework and
their relationships.
Introduction
------------
The V4L2 drivers tend to be very complex due to the complexity of the
hardware: most devices have multiple ICs, export multiple device nodes in
/dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
(IR) devices.
Especially the fact that V4L2 drivers have to setup supporting ICs to
do audio/video muxing/encoding/decoding makes it more complex than most.
Usually these ICs are connected to the main bridge driver through one or
more I2C busses, but other busses can also be used. Such devices are
called 'sub-devices'.
For a long time the framework was limited to the video_device struct for
creating V4L device nodes and video_buf for handling the video buffers
(note that this document does not discuss the video_buf framework).
This meant that all drivers had to do the setup of device instances and
connecting to sub-devices themselves. Some of this is quite complicated
to do right and many drivers never did do it correctly.
There is also a lot of common code that could never be refactored due to
the lack of a framework.
So this framework sets up the basic building blocks that all drivers
need and this same framework should make it much easier to refactor
common code into utility functions shared by all drivers.
Structure of a driver
---------------------
All drivers have the following structure:
1) A struct for each device instance containing the device state.
2) A way of initializing and commanding sub-devices (if any).
3) Creating V4L2 device nodes (/dev/videoX, /dev/vbiX, /dev/radioX and
/dev/vtxX) and keeping track of device-node specific data.
4) Filehandle-specific structs containing per-filehandle data.
This is a rough schematic of how it all relates:
device instances
|
+-sub-device instances
|
\-V4L2 device nodes
|
\-filehandle instances
Structure of the framework
--------------------------
The framework closely resembles the driver structure: it has a v4l2_device
struct for the device instance data, a v4l2_subdev struct to refer to
sub-device instances, the video_device struct stores V4L2 device node data
and in the future a v4l2_fh struct will keep track of filehandle instances
(this is not yet implemented).
struct v4l2_device
------------------
Each device instance is represented by a struct v4l2_device (v4l2-device.h).
Very simple devices can just allocate this struct, but most of the time you
would embed this struct inside a larger struct.
You must register the device instance:
v4l2_device_register(struct device *dev, struct v4l2_device *v4l2_dev);
Registration will initialize the v4l2_device struct and link dev->driver_data
to v4l2_dev. Registration will also set v4l2_dev->name to a value derived from
dev (driver name followed by the bus_id, to be precise). You may change the
name after registration if you want.
The first 'dev' argument is normally the struct device pointer of a pci_dev,
usb_device or platform_device.
You unregister with:
v4l2_device_unregister(struct v4l2_device *v4l2_dev);
Unregistering will also automatically unregister all subdevs from the device.
Sometimes you need to iterate over all devices registered by a specific
driver. This is usually the case if multiple device drivers use the same
hardware. E.g. the ivtvfb driver is a framebuffer driver that uses the ivtv
hardware. The same is true for alsa drivers for example.
You can iterate over all registered devices as follows:
static int callback(struct device *dev, void *p)
{
struct v4l2_device *v4l2_dev = dev_get_drvdata(dev);
/* test if this device was inited */
if (v4l2_dev == NULL)
return 0;
...
return 0;
}
int iterate(void *p)
{
struct device_driver *drv;
int err;
/* Find driver 'ivtv' on the PCI bus.
pci_bus_type is a global. For USB busses use usb_bus_type. */
drv = driver_find("ivtv", &pci_bus_type);
/* iterate over all ivtv device instances */
err = driver_for_each_device(drv, NULL, p, callback);
put_driver(drv);
return err;
}
Sometimes you need to keep a running counter of the device instance. This is
commonly used to map a device instance to an index of a module option array.
The recommended approach is as follows:
static atomic_t drv_instance = ATOMIC_INIT(0);
static int __devinit drv_probe(struct pci_dev *dev,
const struct pci_device_id *pci_id)
{
...
state->instance = atomic_inc_return(&drv_instance) - 1;
}
struct v4l2_subdev
------------------
Many drivers need to communicate with sub-devices. These devices can do all
sort of tasks, but most commonly they handle audio and/or video muxing,
encoding or decoding. For webcams common sub-devices are sensors and camera
controllers.
Usually these are I2C devices, but not necessarily. In order to provide the
driver with a consistent interface to these sub-devices the v4l2_subdev struct
(v4l2-subdev.h) was created.
Each sub-device driver must have a v4l2_subdev struct. This struct can be
stand-alone for simple sub-devices or it might be embedded in a larger struct
if more state information needs to be stored. Usually there is a low-level
device struct (e.g. i2c_client) that contains the device data as setup
by the kernel. It is recommended to store that pointer in the private
data of v4l2_subdev using v4l2_set_subdevdata(). That makes it easy to go
from a v4l2_subdev to the actual low-level bus-specific device data.
You also need a way to go from the low-level struct to v4l2_subdev. For the
common i2c_client struct the i2c_set_clientdata() call is used to store a
v4l2_subdev pointer, for other busses you may have to use other methods.
From the bridge driver perspective you load the sub-device module and somehow
obtain the v4l2_subdev pointer. For i2c devices this is easy: you call
i2c_get_clientdata(). For other busses something similar needs to be done.
Helper functions exists for sub-devices on an I2C bus that do most of this
tricky work for you.
Each v4l2_subdev contains function pointers that sub-device drivers can
implement (or leave NULL if it is not applicable). Since sub-devices can do
so many different things and you do not want to end up with a huge ops struct
of which only a handful of ops are commonly implemented, the function pointers
are sorted according to category and each category has its own ops struct.
The top-level ops struct contains pointers to the category ops structs, which
may be NULL if the subdev driver does not support anything from that category.
It looks like this:
struct v4l2_subdev_core_ops {
int (*g_chip_ident)(struct v4l2_subdev *sd, struct v4l2_chip_ident *chip);
int (*log_status)(struct v4l2_subdev *sd);
int (*init)(struct v4l2_subdev *sd, u32 val);
...
};
struct v4l2_subdev_tuner_ops {
...
};
struct v4l2_subdev_audio_ops {
...
};
struct v4l2_subdev_video_ops {
...
};
struct v4l2_subdev_ops {
const struct v4l2_subdev_core_ops *core;
const struct v4l2_subdev_tuner_ops *tuner;
const struct v4l2_subdev_audio_ops *audio;
const struct v4l2_subdev_video_ops *video;
};
The core ops are common to all subdevs, the other categories are implemented
depending on the sub-device. E.g. a video device is unlikely to support the
audio ops and vice versa.
This setup limits the number of function pointers while still making it easy
to add new ops and categories.
A sub-device driver initializes the v4l2_subdev struct using:
v4l2_subdev_init(subdev, &ops);
Afterwards you need to initialize subdev->name with a unique name and set the
module owner. This is done for you if you use the i2c helper functions.
A device (bridge) driver needs to register the v4l2_subdev with the
v4l2_device:
int err = v4l2_device_register_subdev(device, subdev);
This can fail if the subdev module disappeared before it could be registered.
After this function was called successfully the subdev->dev field points to
the v4l2_device.
You can unregister a sub-device using:
v4l2_device_unregister_subdev(subdev);
Afterwards the subdev module can be unloaded and subdev->dev == NULL.
You can call an ops function either directly:
err = subdev->ops->core->g_chip_ident(subdev, &chip);
but it is better and easier to use this macro:
err = v4l2_subdev_call(subdev, core, g_chip_ident, &chip);
The macro will to the right NULL pointer checks and returns -ENODEV if subdev
is NULL, -ENOIOCTLCMD if either subdev->core or subdev->core->g_chip_ident is
NULL, or the actual result of the subdev->ops->core->g_chip_ident ops.
It is also possible to call all or a subset of the sub-devices:
v4l2_device_call_all(dev, 0, core, g_chip_ident, &chip);
Any subdev that does not support this ops is skipped and error results are
ignored. If you want to check for errors use this:
err = v4l2_device_call_until_err(dev, 0, core, g_chip_ident, &chip);
Any error except -ENOIOCTLCMD will exit the loop with that error. If no
errors (except -ENOIOCTLCMD) occured, then 0 is returned.
The second argument to both calls is a group ID. If 0, then all subdevs are
called. If non-zero, then only those whose group ID match that value will
be called. Before a bridge driver registers a subdev it can set subdev->grp_id
to whatever value it wants (it's 0 by default). This value is owned by the
bridge driver and the sub-device driver will never modify or use it.
The group ID gives the bridge driver more control how callbacks are called.
For example, there may be multiple audio chips on a board, each capable of
changing the volume. But usually only one will actually be used when the
user want to change the volume. You can set the group ID for that subdev to
e.g. AUDIO_CONTROLLER and specify that as the group ID value when calling
v4l2_device_call_all(). That ensures that it will only go to the subdev
that needs it.
The advantage of using v4l2_subdev is that it is a generic struct and does
not contain any knowledge about the underlying hardware. So a driver might
contain several subdevs that use an I2C bus, but also a subdev that is
controlled through GPIO pins. This distinction is only relevant when setting
up the device, but once the subdev is registered it is completely transparent.
I2C sub-device drivers
----------------------
Since these drivers are so common, special helper functions are available to
ease the use of these drivers (v4l2-common.h).
The recommended method of adding v4l2_subdev support to an I2C driver is to
embed the v4l2_subdev struct into the state struct that is created for each
I2C device instance. Very simple devices have no state struct and in that case
you can just create a v4l2_subdev directly.
A typical state struct would look like this (where 'chipname' is replaced by
the name of the chip):
struct chipname_state {
struct v4l2_subdev sd;
... /* additional state fields */
};
Initialize the v4l2_subdev struct as follows:
v4l2_i2c_subdev_init(&state->sd, client, subdev_ops);
This function will fill in all the fields of v4l2_subdev and ensure that the
v4l2_subdev and i2c_client both point to one another.
You should also add a helper inline function to go from a v4l2_subdev pointer
to a chipname_state struct:
static inline struct chipname_state *to_state(struct v4l2_subdev *sd)
{
return container_of(sd, struct chipname_state, sd);
}
Use this to go from the v4l2_subdev struct to the i2c_client struct:
struct i2c_client *client = v4l2_get_subdevdata(sd);
And this to go from an i2c_client to a v4l2_subdev struct:
struct v4l2_subdev *sd = i2c_get_clientdata(client);
Finally you need to make a command function to make driver->command()
call the right subdev_ops functions:
static int subdev_command(struct i2c_client *client, unsigned cmd, void *arg)
{
return v4l2_subdev_command(i2c_get_clientdata(client), cmd, arg);
}
If driver->command is never used then you can leave this out. Eventually the
driver->command usage should be removed from v4l.
Make sure to call v4l2_device_unregister_subdev(sd) when the remove() callback
is called. This will unregister the sub-device from the bridge driver. It is
safe to call this even if the sub-device was never registered.
The bridge driver also has some helper functions it can use:
struct v4l2_subdev *sd = v4l2_i2c_new_subdev(adapter, "module_foo", "chipid", 0x36);
This loads the given module (can be NULL if no module needs to be loaded) and
calls i2c_new_device() with the given i2c_adapter and chip/address arguments.
If all goes well, then it registers the subdev with the v4l2_device. It gets
the v4l2_device by calling i2c_get_adapdata(adapter), so you should make sure
that adapdata is set to v4l2_device when you setup the i2c_adapter in your
driver.
You can also use v4l2_i2c_new_probed_subdev() which is very similar to
v4l2_i2c_new_subdev(), except that it has an array of possible I2C addresses
that it should probe. Internally it calls i2c_new_probed_device().
Both functions return NULL if something went wrong.
struct video_device
-------------------
The actual device nodes in the /dev directory are created using the
video_device struct (v4l2-dev.h). This struct can either be allocated
dynamically or embedded in a larger struct.
To allocate it dynamically use:
struct video_device *vdev = video_device_alloc();
if (vdev == NULL)
return -ENOMEM;
vdev->release = video_device_release;
If you embed it in a larger struct, then you must set the release()
callback to your own function:
struct video_device *vdev = &my_vdev->vdev;
vdev->release = my_vdev_release;
The release callback must be set and it is called when the last user
of the video device exits.
The default video_device_release() callback just calls kfree to free the
allocated memory.
You should also set these fields:
- parent: set to the parent device (same device as was used to register
v4l2_device).
- name: set to something descriptive and unique.
- fops: set to the file_operations struct.
- ioctl_ops: if you use the v4l2_ioctl_ops to simplify ioctl maintenance
(highly recommended to use this and it might become compulsory in the
future!), then set this to your v4l2_ioctl_ops struct.
If you use v4l2_ioctl_ops, then you should set .unlocked_ioctl to
__video_ioctl2 or .ioctl to video_ioctl2 in your file_operations struct.
video_device registration
-------------------------
Next you register the video device: this will create the character device
for you.
err = video_register_device(vdev, VFL_TYPE_GRABBER, -1);
if (err) {
video_device_release(vdev); // or kfree(my_vdev);
return err;
}
Which device is registered depends on the type argument. The following
types exist:
VFL_TYPE_GRABBER: videoX for video input/output devices
VFL_TYPE_VBI: vbiX for vertical blank data (i.e. closed captions, teletext)
VFL_TYPE_RADIO: radioX for radio tuners
VFL_TYPE_VTX: vtxX for teletext devices (deprecated, don't use)
The last argument gives you a certain amount of control over the device
kernel number used (i.e. the X in videoX). Normally you will pass -1 to
let the v4l2 framework pick the first free number. But if a driver creates
many devices, then it can be useful to have different video devices in
separate ranges. For example, video capture devices start at 0, video
output devices start at 16.
So you can use the last argument to specify a minimum kernel number and
the v4l2 framework will try to pick the first free number that is equal
or higher to what you passed. If that fails, then it will just pick the
first free number.
Whenever a device node is created some attributes are also created for you.
If you look in /sys/class/video4linux you see the devices. Go into e.g.
video0 and you will see 'name' and 'index' attributes. The 'name' attribute
is the 'name' field of the video_device struct. The 'index' attribute is
a device node index that can be assigned by the driver, or that is calculated
for you.
If you call video_register_device(), then the index is just increased by
1 for each device node you register. The first video device node you register
always starts off with 0.
Alternatively you can call video_register_device_index() which is identical
to video_register_device(), but with an extra index argument. Here you can
pass a specific index value (between 0 and 31) that should be used.
Users can setup udev rules that utilize the index attribute to make fancy
device names (e.g. 'mpegX' for MPEG video capture device nodes).
After the device was successfully registered, then you can use these fields:
- vfl_type: the device type passed to video_register_device.
- minor: the assigned device minor number.
- num: the device kernel number (i.e. the X in videoX).
- index: the device index number (calculated or set explicitly using
video_register_device_index).
If the registration failed, then you need to call video_device_release()
to free the allocated video_device struct, or free your own struct if the
video_device was embedded in it. The vdev->release() callback will never
be called if the registration failed, nor should you ever attempt to
unregister the device if the registration failed.
video_device cleanup
--------------------
When the video device nodes have to be removed, either during the unload
of the driver or because the USB device was disconnected, then you should
unregister them:
video_unregister_device(vdev);
This will remove the device nodes from sysfs (causing udev to remove them
from /dev).
After video_unregister_device() returns no new opens can be done.
However, in the case of USB devices some application might still have one
of these device nodes open. You should block all new accesses to read,
write, poll, etc. except possibly for certain ioctl operations like
queueing buffers.
When the last user of the video device node exits, then the vdev->release()
callback is called and you can do the final cleanup there.
video_device helper functions
-----------------------------
There are a few useful helper functions:
You can set/get driver private data in the video_device struct using:
void *video_get_drvdata(struct video_device *dev);
void video_set_drvdata(struct video_device *dev, void *data);
Note that you can safely call video_set_drvdata() before calling
video_register_device().
And this function:
struct video_device *video_devdata(struct file *file);
returns the video_device belonging to the file struct.
The final helper function combines video_get_drvdata with
video_devdata:
void *video_drvdata(struct file *file);
You can go from a video_device struct to the v4l2_device struct using:
struct v4l2_device *v4l2_dev = dev_get_drvdata(vdev->parent);
MAINTAINERS
浏览文件 @ 923a789b
......@@ -1755,6 +1755,13 @@ L: linuxppc-dev@ozlabs.org
L: linux-i2c@vger.kernel.org
S: Maintained
FREESCALE IMX / MXC FRAMEBUFFER DRIVER
P: Sascha Hauer
M: kernel@pengutronix.de
L: linux-fbdev-devel@lists.sourceforge.net (moderated for non-subscribers)
L: linux-arm-kernel@lists.arm.linux.org.uk (subscribers-only)
S: Maintained
FREESCALE SOC FS_ENET DRIVER
P: Pantelis Antoniou
M: pantelis.antoniou@gmail.com
......@@ -2042,6 +2049,12 @@ M: mikulas@artax.karlin.mff.cuni.cz
W: http://artax.karlin.mff.cuni.cz/~mikulas/vyplody/hpfs/index-e.cgi
S: Maintained
HSO 3G Modem Driver (hso.c)
P: Denis Joseph Barrow
M: d.barow@option.com
W: http://www.pharscape.org
S: Maintained
HTCPEN TOUCHSCREEN DRIVER
P: Pau Oliva Fora
M: pof@eslack.org
......@@ -2139,11 +2152,6 @@ M: Gadi Oxman <gadio@netvision.net.il>
L: linux-kernel@vger.kernel.org
S: Maintained
IDE-SCSI DRIVER
L: linux-ide@vger.kernel.org
L: linux-scsi@vger.kernel.org
S: Orphan
IDLE-I7300
P: Andy Henroid
M: andrew.d.henroid@intel.com
......@@ -2534,8 +2542,6 @@ W: http://kvm.qumranet.com
S: Supported
KERNEL VIRTUAL MACHINE For Itanium (KVM/IA64)
P: Anthony Xu
M: anthony.xu@intel.com
P: Xiantao Zhang
M: xiantao.zhang@intel.com
L: kvm-ia64@vger.kernel.org
......@@ -2628,13 +2634,13 @@ W: http://www.hansenpartnership.com/voyager
S: Maintained
LINUX FOR POWERPC (32-BIT AND 64-BIT)
P: Paul Mackerras
M: paulus@samba.org
P: Benjamin Herrenschmidt
M: benh@kernel.crashing.org
P: Paul Mackerras
M: paulus@samba.org
W: http://www.penguinppc.org/
L: linuxppc-dev@ozlabs.org
T: git kernel.org:/pub/scm/linux/kernel/git/paulus/powerpc.git
T: git kernel.org:/pub/scm/linux/kernel/git/benh/powerpc.git
S: Supported
LINUX FOR POWER MACINTOSH
......
Makefile
浏览文件 @ 923a789b
......@@ -205,13 +205,14 @@ ifeq ($(ARCH),x86_64)
SRCARCH := x86
endif
# Where to locate arch specific headers
# Additional ARCH settings for sparc
ifeq ($(ARCH),sparc64)
hdr-arch := sparc
else
hdr-arch := $(SRCARCH)
SRCARCH := sparc
endif
# Where to locate arch specific headers
hdr-arch := $(SRCARCH)
KCONFIG_CONFIG ?= .config
# SHELL used by kbuild
......
arch/Kconfig
浏览文件 @ 923a789b
......@@ -6,6 +6,8 @@ config OPROFILE
tristate "OProfile system profiling (EXPERIMENTAL)"
depends on PROFILING
depends on HAVE_OPROFILE
select TRACING
select RING_BUFFER
help
OProfile is a profiling system capable of profiling the
whole system, include the kernel, kernel modules, libraries,
......
arch/alpha/include/asm/io.h
浏览文件 @ 923a789b
......@@ -96,9 +96,6 @@ static inline dma_addr_t __deprecated isa_page_to_bus(struct page *page)
return page_to_phys(page);
}
/* This depends on working iommu. */
#define BIO_VMERGE_BOUNDARY (alpha_mv.mv_pci_tbi ? PAGE_SIZE : 0)
/* Maximum PIO space address supported? */
#define IO_SPACE_LIMIT 0xffff
......
arch/alpha/include/asm/smp.h
浏览文件 @ 923a789b
......@@ -45,7 +45,6 @@ extern struct cpuinfo_alpha cpu_data[NR_CPUS];
#define raw_smp_processor_id() (current_thread_info()->cpu)
extern int smp_num_cpus;
#define cpu_possible_map cpu_present_map
extern void arch_send_call_function_single_ipi(int cpu);
extern void arch_send_call_function_ipi(cpumask_t mask);
......
arch/alpha/kernel/init_task.c
浏览文件 @ 923a789b
......@@ -8,7 +8,6 @@
#include <asm/uaccess.h>
static struct fs_struct init_fs = INIT_FS;
static struct signal_struct init_signals = INIT_SIGNALS(init_signals);
static struct sighand_struct init_sighand = INIT_SIGHAND(init_sighand);
struct mm_struct init_mm = INIT_MM(init_mm);
......
arch/alpha/kernel/irq.c
浏览文件 @ 923a789b
......@@ -55,7 +55,7 @@ int irq_select_affinity(unsigned int irq)
last_cpu = cpu;
irq_desc[irq].affinity = cpumask_of_cpu(cpu);
irq_desc[irq].chip->set_affinity(irq, cpumask_of_cpu(cpu));
irq_desc[irq].chip->set_affinity(irq, cpumask_of(cpu));
return 0;
}
#endif /* CONFIG_SMP */
......
arch/alpha/kernel/process.c
浏览文件 @ 923a789b
......@@ -94,6 +94,7 @@ common_shutdown_1(void *generic_ptr)
flags |= 0x00040000UL; /* "remain halted" */
*pflags = flags;
cpu_clear(cpuid, cpu_present_map);
cpu_clear(cpuid, cpu_possible_map);
halt();
}
#endif
......@@ -120,6 +121,7 @@ common_shutdown_1(void *generic_ptr)
#ifdef CONFIG_SMP
/* Wait for the secondaries to halt. */
cpu_clear(boot_cpuid, cpu_present_map);
cpu_clear(boot_cpuid, cpu_possible_map);
while (cpus_weight(cpu_present_map))
barrier();
#endif
......
arch/alpha/kernel/smp.c
浏览文件 @ 923a789b
......@@ -70,11 +70,6 @@ enum ipi_message_type {
/* Set to a secondary's cpuid when it comes online. */
static int smp_secondary_alive __devinitdata = 0;
/* Which cpus ids came online. */
cpumask_t cpu_online_map;
EXPORT_SYMBOL(cpu_online_map);
int smp_num_probed; /* Internal processor count */
int smp_num_cpus = 1; /* Number that came online. */
EXPORT_SYMBOL(smp_num_cpus);
......@@ -440,6 +435,7 @@ setup_smp(void)
((char *)cpubase + i*hwrpb->processor_size);
if ((cpu->flags & 0x1cc) == 0x1cc) {
smp_num_probed++;
cpu_set(i, cpu_possible_map);
cpu_set(i, cpu_present_map);
cpu->pal_revision = boot_cpu_palrev;
}
......@@ -473,6 +469,7 @@ smp_prepare_cpus(unsigned int max_cpus)
/* Nothing to do on a UP box, or when told not to. */
if (smp_num_probed == 1 || max_cpus == 0) {
cpu_possible_map = cpumask_of_cpu(boot_cpuid);
cpu_present_map = cpumask_of_cpu(boot_cpuid);
printk(KERN_INFO "SMP mode deactivated.\n");
return;
......
arch/alpha/kernel/sys_dp264.c
浏览文件 @ 923a789b
......@@ -177,19 +177,19 @@ cpu_set_irq_affinity(unsigned int irq, cpumask_t affinity)
}
static void
dp264_set_affinity(unsigned int irq, cpumask_t affinity)
dp264_set_affinity(unsigned int irq, const struct cpumask *affinity)
{
spin_lock(&dp264_irq_lock);
cpu_set_irq_affinity(irq, affinity);
cpu_set_irq_affinity(irq, *affinity);
tsunami_update_irq_hw(cached_irq_mask);
spin_unlock(&dp264_irq_lock);
}
static void
clipper_set_affinity(unsigned int irq, cpumask_t affinity)
clipper_set_affinity(unsigned int irq, const struct cpumask *affinity)
{
spin_lock(&dp264_irq_lock);
cpu_set_irq_affinity(irq - 16, affinity);
cpu_set_irq_affinity(irq - 16, *affinity);
tsunami_update_irq_hw(cached_irq_mask);
spin_unlock(&dp264_irq_lock);
}
......
arch/alpha/kernel/sys_titan.c
浏览文件 @ 923a789b
......@@ -158,10 +158,10 @@ titan_cpu_set_irq_affinity(unsigned int irq, cpumask_t affinity)
}
static void
titan_set_irq_affinity(unsigned int irq, cpumask_t affinity)
titan_set_irq_affinity(unsigned int irq, const struct cpumask *affinity)
{
spin_lock(&titan_irq_lock);
titan_cpu_set_irq_affinity(irq - 16, affinity);
titan_cpu_set_irq_affinity(irq - 16, *affinity);
titan_update_irq_hw(titan_cached_irq_mask);
spin_unlock(&titan_irq_lock);
}
......
arch/arm/Kconfig
浏览文件 @ 923a789b
......@@ -156,7 +156,6 @@ config ARCH_MTD_XIP
bool
config GENERIC_HARDIRQS_NO__DO_IRQ
bool
def_bool y
if OPROFILE
......@@ -201,6 +200,7 @@ choice
config ARCH_AAEC2000
bool "Agilent AAEC-2000 based"
select CPU_ARM920T
select ARM_AMBA
select HAVE_CLK
help
......@@ -210,6 +210,7 @@ config ARCH_INTEGRATOR
bool "ARM Ltd. Integrator family"
select ARM_AMBA
select HAVE_CLK
select COMMON_CLKDEV
select ICST525
help
Support for ARM's Integrator platform.
......@@ -218,6 +219,7 @@ config ARCH_REALVIEW
bool "ARM Ltd. RealView family"
select ARM_AMBA
select HAVE_CLK
select COMMON_CLKDEV
select ICST307
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
......@@ -229,6 +231,7 @@ config ARCH_VERSATILE
select ARM_AMBA
select ARM_VIC
select HAVE_CLK
select COMMON_CLKDEV
select ICST307
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
......@@ -243,22 +246,15 @@ config ARCH_AT91
This enables support for systems based on the Atmel AT91RM9200,
AT91SAM9 and AT91CAP9 processors.
config ARCH_CLPS7500
bool "Cirrus CL-PS7500FE"
select TIMER_ACORN
select ISA
select NO_IOPORT
select ARCH_SPARSEMEM_ENABLE
help
Support for the Cirrus Logic PS7500FE system-on-a-chip.
config ARCH_CLPS711X
bool "Cirrus Logic CLPS711x/EP721x-based"
select CPU_ARM720T
help
Support for Cirrus Logic 711x/721x based boards.
config ARCH_EBSA110
bool "EBSA-110"
select CPU_SA110
select ISA
select NO_IOPORT
help
......@@ -269,16 +265,19 @@ config ARCH_EBSA110
config ARCH_EP93XX
bool "EP93xx-based"
select CPU_ARM920T
select ARM_AMBA
select ARM_VIC
select GENERIC_GPIO
select HAVE_CLK
select COMMON_CLKDEV
select ARCH_REQUIRE_GPIOLIB
help
This enables support for the Cirrus EP93xx series of CPUs.
config ARCH_FOOTBRIDGE
bool "FootBridge"
select CPU_SA110
select FOOTBRIDGE
help
Support for systems based on the DC21285 companion chip
......@@ -286,18 +285,23 @@ config ARCH_FOOTBRIDGE
config ARCH_NETX
bool "Hilscher NetX based"
select CPU_ARM926T
select ARM_VIC
select GENERIC_CLOCKEVENTS
select GENERIC_TIME
help
This enables support for systems based on the Hilscher NetX Soc
config ARCH_H720X
bool "Hynix HMS720x-based"
select CPU_ARM720T
select ISA_DMA_API
help
This enables support for systems based on the Hynix HMS720x
config ARCH_IMX
bool "IMX"
select CPU_ARM920T
select GENERIC_GPIO
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
......@@ -307,6 +311,7 @@ config ARCH_IMX
config ARCH_IOP13XX
bool "IOP13xx-based"
depends on MMU
select CPU_XSC3
select PLAT_IOP
select PCI
select ARCH_SUPPORTS_MSI
......@@ -317,6 +322,7 @@ config ARCH_IOP13XX
config ARCH_IOP32X
bool "IOP32x-based"
depends on MMU
select CPU_XSCALE
select PLAT_IOP
select PCI
select GENERIC_GPIO
......@@ -328,6 +334,7 @@ config ARCH_IOP32X
config ARCH_IOP33X
bool "IOP33x-based"
depends on MMU
select CPU_XSCALE
select PLAT_IOP
select PCI
select GENERIC_GPIO
......@@ -338,6 +345,7 @@ config ARCH_IOP33X
config ARCH_IXP23XX
bool "IXP23XX-based"
depends on MMU
select CPU_XSC3
select PCI
help
Support for Intel's IXP23xx (XScale) family of processors.
......@@ -345,6 +353,7 @@ config ARCH_IXP23XX
config ARCH_IXP2000
bool "IXP2400/2800-based"
depends on MMU
select CPU_XSCALE
select PCI
help
Support for Intel's IXP2400/2800 (XScale) family of processors.
......@@ -352,6 +361,7 @@ config ARCH_IXP2000
config ARCH_IXP4XX
bool "IXP4xx-based"
depends on MMU
select CPU_XSCALE
select GENERIC_GPIO
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
......@@ -361,6 +371,7 @@ config ARCH_IXP4XX
config ARCH_L7200
bool "LinkUp-L7200"
select CPU_ARM720T
select FIQ
help
Say Y here if you intend to run this kernel on a LinkUp Systems
......@@ -374,7 +385,9 @@ config ARCH_L7200
config ARCH_KIRKWOOD
bool "Marvell Kirkwood"
select CPU_FEROCEON
select PCI
select GENERIC_GPIO
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
......@@ -384,13 +397,16 @@ config ARCH_KIRKWOOD
config ARCH_KS8695
bool "Micrel/Kendin KS8695"
select CPU_ARM922T
select GENERIC_GPIO
select ARCH_REQUIRE_GPIOLIB
help
Support for Micrel/Kendin KS8695 "Centaur" (ARM922T) based
System-on-Chip devices.
config ARCH_NS9XXX
bool "NetSilicon NS9xxx"
select CPU_ARM926T
select GENERIC_GPIO
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
......@@ -403,6 +419,7 @@ config ARCH_NS9XXX
config ARCH_LOKI
bool "Marvell Loki (88RC8480)"
select CPU_FEROCEON
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
......@@ -411,7 +428,9 @@ config ARCH_LOKI
config ARCH_MV78XX0
bool "Marvell MV78xx0"
select CPU_FEROCEON
select PCI
select GENERIC_GPIO
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select PLAT_ORION
......@@ -432,6 +451,7 @@ config ARCH_MXC
config ARCH_ORION5X
bool "Marvell Orion"
depends on MMU
select CPU_FEROCEON
select PCI
select GENERIC_GPIO
select GENERIC_TIME
......@@ -444,6 +464,7 @@ config ARCH_ORION5X
config ARCH_PNX4008
bool "Philips Nexperia PNX4008 Mobile"
select CPU_ARM926T
select HAVE_CLK
help
This enables support for Philips PNX4008 mobile platform.
......@@ -454,6 +475,7 @@ config ARCH_PXA
select ARCH_MTD_XIP
select GENERIC_GPIO
select HAVE_CLK
select COMMON_CLKDEV
select ARCH_REQUIRE_GPIOLIB
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
......@@ -477,6 +499,7 @@ config ARCH_RPC
config ARCH_SA1100
bool "SA1100-based"
select CPU_SA1100
select ISA
select ARCH_SPARSEMEM_ENABLE
select ARCH_MTD_XIP
......@@ -498,8 +521,16 @@ config ARCH_S3C2410
BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
the Samsung SMDK2410 development board (and derivatives).
config ARCH_S3C64XX
bool "Samsung S3C64XX"
select GENERIC_GPIO
select HAVE_CLK
help
Samsung S3C64XX series based systems
config ARCH_SHARK
bool "Shark"
select CPU_SA110
select ISA
select ISA_DMA
select ZONE_DMA
......@@ -510,6 +541,7 @@ config ARCH_SHARK
config ARCH_LH7A40X
bool "Sharp LH7A40X"
select CPU_ARM922T
select ARCH_DISCONTIGMEM_ENABLE if !LH7A40X_CONTIGMEM
select ARCH_SPARSEMEM_ENABLE if !LH7A40X_CONTIGMEM
help
......@@ -520,6 +552,7 @@ config ARCH_LH7A40X
config ARCH_DAVINCI
bool "TI DaVinci"
select CPU_ARM926T
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
select GENERIC_GPIO
......@@ -541,6 +574,7 @@ config ARCH_OMAP
config ARCH_MSM
bool "Qualcomm MSM"
select CPU_V6
select GENERIC_TIME
select GENERIC_CLOCKEVENTS
help
......@@ -549,6 +583,13 @@ config ARCH_MSM
interface to the ARM9 modem processor which runs the baseband stack
and controls some vital subsystems (clock and power control, etc).
config ARCH_W90X900
bool "Nuvoton W90X900 CPU"
select CPU_ARM926T
help
Support for Nuvoton (Winbond logic dept.) ARM9 processor,You
can login www.mcuos.com or www.nuvoton.com to know more.
endchoice
source "arch/arm/mach-clps711x/Kconfig"
......@@ -590,6 +631,7 @@ source "arch/arm/mach-orion5x/Kconfig"
source "arch/arm/mach-kirkwood/Kconfig"
source "arch/arm/plat-s3c24xx/Kconfig"
source "arch/arm/plat-s3c64xx/Kconfig"
source "arch/arm/plat-s3c/Kconfig"
if ARCH_S3C2410
......@@ -601,6 +643,11 @@ source "arch/arm/mach-s3c2442/Kconfig"
source "arch/arm/mach-s3c2443/Kconfig"
endif
if ARCH_S3C64XX
source "arch/arm/mach-s3c6400/Kconfig"
source "arch/arm/mach-s3c6410/Kconfig"
endif
source "arch/arm/mach-lh7a40x/Kconfig"
source "arch/arm/mach-imx/Kconfig"
......@@ -627,6 +674,8 @@ source "arch/arm/mach-ks8695/Kconfig"
source "arch/arm/mach-msm/Kconfig"
source "arch/arm/mach-w90x900/Kconfig"
# Definitions to make life easier
config ARCH_ACORN
bool
......@@ -781,7 +830,7 @@ config HOTPLUG_CPU
config LOCAL_TIMERS
bool "Use local timer interrupts"
depends on SMP && (REALVIEW_EB_ARM11MP || MACH_REALVIEW_PB11MP)
depends on SMP && (REALVIEW_EB_ARM11MP || MACH_REALVIEW_PB11MP || REALVIEW_EB_A9MP)
default y
help
Enable support for local timers on SMP platforms, rather then the
......
arch/arm/Makefile
浏览文件 @ 923a789b
......@@ -76,6 +76,7 @@ tune-$(CONFIG_CPU_SA110) :=-mtune=strongarm110
tune-$(CONFIG_CPU_SA1100) :=-mtune=strongarm1100
tune-$(CONFIG_CPU_XSCALE) :=$(call cc-option,-mtune=xscale,-mtune=strongarm110) -Wa,-mcpu=xscale
tune-$(CONFIG_CPU_XSC3) :=$(call cc-option,-mtune=xscale,-mtune=strongarm110) -Wa,-mcpu=xscale
tune-$(CONFIG_CPU_FEROCEON) :=$(call cc-option,-mtune=marvell-f,-mtune=xscale)
tune-$(CONFIG_CPU_V6) :=$(call cc-option,-mtune=arm1136j-s,-mtune=strongarm)
ifeq ($(CONFIG_AEABI),y)
......@@ -96,7 +97,6 @@ textofs-y := 0x00008000
machine-$(CONFIG_ARCH_RPC) := rpc
machine-$(CONFIG_ARCH_EBSA110) := ebsa110
machine-$(CONFIG_ARCH_CLPS7500) := clps7500
machine-$(CONFIG_FOOTBRIDGE) := footbridge
machine-$(CONFIG_ARCH_SHARK) := shark
machine-$(CONFIG_ARCH_SA1100) := sa1100
......@@ -121,7 +121,10 @@ endif
machine-$(CONFIG_ARCH_OMAP3) := omap2
plat-$(CONFIG_ARCH_OMAP) := omap
machine-$(CONFIG_ARCH_S3C2410) := s3c2410 s3c2400 s3c2412 s3c2440 s3c2442 s3c2443
machine-$(CONFIG_ARCH_S3C24A0) := s3c24a0
plat-$(CONFIG_PLAT_S3C24XX) := s3c24xx s3c
machine-$(CONFIG_ARCH_S3C64XX) := s3c6400 s3c6410
plat-$(CONFIG_PLAT_S3C64XX) := s3c64xx s3c
machine-$(CONFIG_ARCH_LH7A40X) := lh7a40x
machine-$(CONFIG_ARCH_VERSATILE) := versatile
machine-$(CONFIG_ARCH_IMX) := imx
......@@ -139,11 +142,13 @@ endif
plat-$(CONFIG_ARCH_MXC) := mxc
machine-$(CONFIG_ARCH_MX2) := mx2
machine-$(CONFIG_ARCH_MX3) := mx3
machine-$(CONFIG_ARCH_MX1) := mx1
machine-$(CONFIG_ARCH_ORION5X) := orion5x
plat-$(CONFIG_PLAT_ORION) := orion
machine-$(CONFIG_ARCH_MSM) := msm
machine-$(CONFIG_ARCH_LOKI) := loki
machine-$(CONFIG_ARCH_MV78XX0) := mv78xx0
machine-$(CONFIG_ARCH_W90X900) := w90x900
ifeq ($(CONFIG_ARCH_EBSA110),y)
# This is what happens if you forget the IOCS16 line.
......
arch/arm/boot/compressed/Makefile
浏览文件 @ 923a789b
......@@ -23,10 +23,6 @@ ifeq ($(CONFIG_ARCH_L7200),y)
OBJS += head-l7200.o
endif
ifeq ($(CONFIG_ARCH_CLPS7500),y)
HEAD = head-clps7500.o
endif
ifeq ($(CONFIG_ARCH_P720T),y)
# Borrow this code from SA1100
OBJS += head-sa1100.o
......
arch/arm/boot/compressed/head-clps7500.S 已删除 100644 → 0
浏览文件 @ 103ceffb
/*
* linux/arch/arm/boot/compressed/head-clps7500.S
*
* Copyright (C) 1999, 2000, 2001 Nexus Electronics Ltd
*/
/* There are three different ways the kernel can be
booted on a 7500 system: from Angel (loaded in RAM), from
16-bit ROM or from 32-bit Flash. Luckily, a single kernel
image does for them all. */
/* This branch is taken if the CPU memory width matches the
actual device in use. The default at power on is 16 bits
so we must be prepared for a mismatch. */
.section ".start", "ax"
2:
b 1f
.word 0xffff
.word 0xb632 @ mov r11, #0x03200000
.word 0xe3a0
.word 0x0000 @ mov r0, #0
.word 0xe3a0
.word 0x0080 @ strb r0, [r11, #0x80]
.word 0xe5cb
.word 0xf000 @ mov pc, #0
.word 0xe3a0
1:
adr r1, 2b
teq r1, #0
bne .Langel
/* This is a direct-from-ROM boot. Copy the kernel into
RAM and run it there. */
mov r0, #0x30
mcr p15, 0, r0, c1, c0, 0
mov r0, #0x13
msr cpsr_cxsf, r0
mov r12, #0x03000000 @ point to LEDs
orr r12, r12, #0x00020000
orr r12, r12, #0xba00
mov r0, #0x5500
str r0, [r12]
mov r0, #0x10000000
orr r0, r0, #0x8000
mov r4, r0
ldr r2, =_end
2:
ldr r3, [r1], #4
str r3, [r0], #4
teq r0, r2
bne 2b
mov r0, #0xff00
str r0, [r12]
1:
mov r12, #0x03000000 @ point to LEDs
orr r12, r12, #0x00020000
orr r12, r12, #0xba00
mov r0, #0xfe00
str r0, [r12]
adr lr, 1f
mov r0, #0
mov r1, #14 /* MACH_TYPE_CLPS7500 */
mov pc, lr
.Langel:
#ifdef CONFIG_ANGELBOOT
/* Call Angel to switch into SVC mode. */
mov r0, #0x17
swi 0x123456
#endif
/* Ensure all interrupts are off and MMU disabled */
mrs r0, cpsr
orr r0, r0, #0xc0
msr cpsr_cxsf, r0
adr lr, 1b
orr lr, lr, #0x10000000
mov r0, #0x30 @ MMU off
mcr p15, 0, r0, c1, c0, 0
mov r0, r0
mov pc, lr
.ltorg
1:
/* And the rest */
#include "head.S"
arch/arm/boot/compressed/head.S
浏览文件 @ 923a789b
......@@ -624,6 +624,12 @@ proc_types:
b __armv4_mmu_cache_off
b __armv4_mmu_cache_flush
.word 0x56056930
.word 0xff0ffff0 @ PXA935
b __armv4_mmu_cache_on
b __armv4_mmu_cache_off
b __armv4_mmu_cache_flush
.word 0x56050000 @ Feroceon
.word 0xff0f0000
b __armv4_mmu_cache_on
......@@ -717,6 +723,9 @@ __armv7_mmu_cache_off:
bl __armv7_mmu_cache_flush
mov r0, #0
mcr p15, 0, r0, c8, c7, 0 @ invalidate whole TLB
mcr p15, 0, r0, c7, c5, 6 @ invalidate BTC
mcr p15, 0, r0, c7, c10, 4 @ DSB
mcr p15, 0, r0, c7, c5, 4 @ ISB
mov pc, r12
__arm6_mmu_cache_off:
......@@ -778,12 +787,13 @@ __armv6_mmu_cache_flush:
__armv7_mmu_cache_flush:
mrc p15, 0, r10, c0, c1, 5 @ read ID_MMFR1
tst r10, #0xf << 16 @ hierarchical cache (ARMv7)
beq hierarchical
mov r10, #0
beq hierarchical
mcr p15, 0, r10, c7, c14, 0 @ clean+invalidate D
b iflush
hierarchical:
stmfd sp!, {r0-r5, r7, r9-r11}
mcr p15, 0, r10, c7, c10, 5 @ DMB
stmfd sp!, {r0-r5, r7, r9, r11}
mrc p15, 1, r0, c0, c0, 1 @ read clidr
ands r3, r0, #0x7000000 @ extract loc from clidr
mov r3, r3, lsr #23 @ left align loc bit field
......@@ -820,12 +830,14 @@ skip:
cmp r3, r10
bgt loop1
finished:
ldmfd sp!, {r0-r5, r7, r9, r11}
mov r10, #0 @ swith back to cache level 0
mcr p15, 2, r10, c0, c0, 0 @ select current cache level in cssr
ldmfd sp!, {r0-r5, r7, r9-r11}
iflush:
mcr p15, 0, r10, c7, c10, 4 @ DSB
mcr p15, 0, r10, c7, c5, 0 @ invalidate I+BTB
mcr p15, 0, r10, c7, c10, 4 @ drain WB
mcr p15, 0, r10, c7, c10, 4 @ DSB
mcr p15, 0, r10, c7, c5, 4 @ ISB
mov pc, lr
__armv5tej_mmu_cache_flush:
......
arch/arm/boot/compressed/misc.c
浏览文件 @ 923a789b
......@@ -86,6 +86,8 @@ static void putstr(const char *ptr)
#define __ptr_t void *
#define memzero(s,n) __memzero(s,n)
/*
* Optimised C version of memzero for the ARM.
*/
......
arch/arm/common/Kconfig
浏览文件 @ 923a789b
......@@ -33,3 +33,6 @@ config SHARPSL_PM
config SHARP_SCOOP
bool
config COMMON_CLKDEV
bool
arch/arm/common/Makefile
浏览文件 @ 923a789b
......@@ -17,3 +17,4 @@ obj-$(CONFIG_SHARP_SCOOP) += scoop.o
obj-$(CONFIG_ARCH_IXP2000) += uengine.o
obj-$(CONFIG_ARCH_IXP23XX) += uengine.o
obj-$(CONFIG_PCI_HOST_ITE8152) += it8152.o
obj-$(CONFIG_COMMON_CLKDEV) += clkdev.o
arch/arm/common/clkdev.c 0 → 100644
浏览文件 @ 923a789b
/*
* arch/arm/common/clkdev.c
*
* Copyright (C) 2008 Russell King.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
*
* Helper for the clk API to assist looking up a struct clk.
*/
#include <linux/module.h>
#include <linux/kernel.h>
#include <linux/device.h>
#include <linux/list.h>
#include <linux/errno.h>
#include <linux/err.h>
#include <linux/string.h>
#include <linux/mutex.h>
#include <asm/clkdev.h>
#include <mach/clkdev.h>
static LIST_HEAD(clocks);
static DEFINE_MUTEX(clocks_mutex);
static struct clk *clk_find(const char *dev_id, const char *con_id)
{
struct clk_lookup *p;
struct clk *clk = NULL;
int match, best = 0;
list_for_each_entry(p, &clocks, node) {
if ((p->dev_id && !dev_id) || (p->con_id && !con_id))
continue;
match = 0;
if (p->dev_id)
match += 2 * (strcmp(p->dev_id, dev_id) == 0);
if (p->con_id)
match += 1 * (strcmp(p->con_id, con_id) == 0);
if (match == 0)
continue;
if (match > best) {
clk = p->clk;
best = match;
}
}
return clk;
}
struct clk *clk_get(struct device *dev, const char *con_id)
{
const char *dev_id = dev ? dev_name(dev) : NULL;
struct clk *clk;
mutex_lock(&clocks_mutex);
clk = clk_find(dev_id, con_id);
if (clk && !__clk_get(clk))
clk = NULL;
mutex_unlock(&clocks_mutex);
return clk ? clk : ERR_PTR(-ENOENT);
}
EXPORT_SYMBOL(clk_get);
void clk_put(struct clk *clk)
{
__clk_put(clk);
}
EXPORT_SYMBOL(clk_put);
void clkdev_add(struct clk_lookup *cl)
{
mutex_lock(&clocks_mutex);
list_add_tail(&cl->node, &clocks);
mutex_unlock(&clocks_mutex);
}
EXPORT_SYMBOL(clkdev_add);
#define MAX_DEV_ID 20
#define MAX_CON_ID 16
struct clk_lookup_alloc {
struct clk_lookup cl;
char dev_id[MAX_DEV_ID];
char con_id[MAX_CON_ID];
};
struct clk_lookup *clkdev_alloc(struct clk *clk, const char *con_id,
const char *dev_fmt, ...)
{
struct clk_lookup_alloc *cla;
cla = kzalloc(sizeof(*cla), GFP_KERNEL);
if (!cla)
return NULL;
cla->cl.clk = clk;
if (con_id) {
strlcpy(cla->con_id, con_id, sizeof(cla->con_id));
cla->cl.con_id = cla->con_id;
}
if (dev_fmt) {
va_list ap;
va_start(ap, dev_fmt);
vscnprintf(cla->dev_id, sizeof(cla->dev_id), dev_fmt, ap);
cla->cl.dev_id = cla->dev_id;
va_end(ap);
}
return &cla->cl;
}
EXPORT_SYMBOL(clkdev_alloc);
/*
* clkdev_drop - remove a clock dynamically allocated
*/
void clkdev_drop(struct clk_lookup *cl)
{
mutex_lock(&clocks_mutex);
list_del(&cl->node);
mutex_unlock(&clocks_mutex);
kfree(cl);
}
EXPORT_SYMBOL(clkdev_drop);
arch/arm/common/gic.c
浏览文件 @ 923a789b
......@@ -109,11 +109,11 @@ static void gic_unmask_irq(unsigned int irq)
}
#ifdef CONFIG_SMP
static void gic_set_cpu(unsigned int irq, cpumask_t mask_val)
static void gic_set_cpu(unsigned int irq, const struct cpumask *mask_val)
{
void __iomem *reg = gic_dist_base(irq) + GIC_DIST_TARGET + (gic_irq(irq) & ~3);
unsigned int shift = (irq % 4) * 8;
unsigned int cpu = first_cpu(mask_val);
unsigned int cpu = cpumask_first(mask_val);
u32 val;
spin_lock(&irq_controller_lock);
......
arch/arm/common/locomo.c
浏览文件 @ 923a789b
......@@ -1108,6 +1108,7 @@ void locomo_frontlight_set(struct locomo_dev *dev, int duty, int vr, int bpwf)
locomo_writel(bpwf | LOCOMO_ALC_EN, lchip->base + LOCOMO_FRONTLIGHT + LOCOMO_ALS);
spin_unlock_irqrestore(&lchip->lock, flags);
}
EXPORT_SYMBOL(locomo_frontlight_set);
/*
* LoCoMo "Register Access Bus."
......
arch/arm/common/vic.c
浏览文件 @ 923a789b
......@@ -69,12 +69,12 @@ void __init vic_init(void __iomem *base, unsigned int irq_start,
/*
* Make sure we clear all existing interrupts
*/
writel(0, base + VIC_VECT_ADDR);
writel(0, base + VIC_PL190_VECT_ADDR);
for (i = 0; i < 19; i++) {
unsigned int value;
value = readl(base + VIC_VECT_ADDR);
writel(value, base + VIC_VECT_ADDR);
value = readl(base + VIC_PL190_VECT_ADDR);
writel(value, base + VIC_PL190_VECT_ADDR);
}
for (i = 0; i < 16; i++) {
......@@ -82,7 +82,7 @@ void __init vic_init(void __iomem *base, unsigned int irq_start,
writel(VIC_VECT_CNTL_ENABLE | i, reg);
}
writel(32, base + VIC_DEF_VECT_ADDR);
writel(32, base + VIC_PL190_DEF_VECT_ADDR);
for (i = 0; i < 32; i++) {
unsigned int irq = irq_start + i;
......
arch/arm/configs/eseries_pxa_defconfig
浏览文件 @ 923a789b
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.26
# Sat Jul 26 22:28:46 2008
# Linux kernel version: 2.6.28-rc8
# Wed Dec 24 23:35:45 2008
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
......@@ -22,8 +22,6 @@ CONFIG_RWSEM_GENERIC_SPINLOCK=y
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_SUPPORTS_AOUT=y
CONFIG_ZONE_DMA=y
CONFIG_ARCH_MTD_XIP=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_VECTORS_BASE=0xffff0000
......@@ -48,8 +46,7 @@ CONFIG_SYSVIPC_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_CGROUPS is not set
# CONFIG_GROUP_SCHED is not set
CONFIG_SYSFS_DEPRECATED=y
CONFIG_SYSFS_DEPRECATED_V2=y
# CONFIG_SYSFS_DEPRECATED_V2 is not set
# CONFIG_RELAY is not set
# CONFIG_NAMESPACES is not set
# CONFIG_BLK_DEV_INITRD is not set
......@@ -58,13 +55,12 @@ CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_SYSCTL_SYSCALL_CHECK=y
# CONFIG_KALLSYMS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_COMPAT_BRK=y
# CONFIG_COMPAT_BRK is not set
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
......@@ -73,6 +69,7 @@ CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
......@@ -80,15 +77,10 @@ CONFIG_SLAB=y
# CONFIG_PROFILING is not set
# CONFIG_MARKERS is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS is not set
# CONFIG_HAVE_IOREMAP_PROT is not set
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
# CONFIG_HAVE_ARCH_TRACEHOOK is not set
# CONFIG_HAVE_DMA_ATTRS is not set
# CONFIG_USE_GENERIC_SMP_HELPERS is not set
CONFIG_HAVE_CLK=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_HAVE_GENERIC_DMA_COHERENT=y
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
......@@ -112,14 +104,15 @@ CONFIG_BLOCK=y
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"
CONFIG_CLASSIC_RCU=y
CONFIG_FREEZER=y
#
# System Type
......@@ -129,7 +122,6 @@ CONFIG_CLASSIC_RCU=y
# CONFIG_ARCH_REALVIEW is not set
# CONFIG_ARCH_VERSATILE is not set
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_CLPS7500 is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
......@@ -160,7 +152,8 @@ CONFIG_ARCH_PXA=y
# CONFIG_ARCH_LH7A40X is not set
# CONFIG_ARCH_DAVINCI is not set
# CONFIG_ARCH_OMAP is not set
# CONFIG_ARCH_MSM7X00A is not set
# CONFIG_ARCH_MSM is not set
# CONFIG_ARCH_W90X900 is not set
#
# Intel PXA2xx/PXA3xx Implementations
......@@ -169,8 +162,10 @@ CONFIG_ARCH_PXA=y
# CONFIG_ARCH_LUBBOCK is not set
# CONFIG_MACH_LOGICPD_PXA270 is not set
# CONFIG_MACH_MAINSTONE is not set
# CONFIG_MACH_MP900C is not set
# CONFIG_ARCH_PXA_IDP is not set
# CONFIG_PXA_SHARPSL is not set
# CONFIG_ARCH_VIPER is not set
CONFIG_ARCH_PXA_ESERIES=y
CONFIG_MACH_E330=y
CONFIG_MACH_E350=y
......@@ -178,7 +173,8 @@ CONFIG_MACH_E740=y
CONFIG_MACH_E750=y
CONFIG_MACH_E400=y
CONFIG_MACH_E800=y
# CONFIG_MACH_TRIZEPS4 is not set
# CONFIG_TRIZEPS_PXA is not set
# CONFIG_MACH_H5000 is not set
# CONFIG_MACH_EM_X270 is not set
# CONFIG_MACH_COLIBRI is not set
# CONFIG_MACH_ZYLONITE is not set
......@@ -186,12 +182,15 @@ CONFIG_MACH_E800=y
# CONFIG_MACH_TAVOREVB is not set
# CONFIG_MACH_SAAR is not set
# CONFIG_MACH_ARMCORE is not set
# CONFIG_MACH_CM_X300 is not set
# CONFIG_MACH_MAGICIAN is not set
# CONFIG_MACH_MIOA701 is not set
# CONFIG_MACH_PCM027 is not set
# CONFIG_ARCH_PXA_PALM is not set
# CONFIG_PXA_EZX is not set
CONFIG_PXA25x=y
# CONFIG_PXA_PWM is not set
CONFIG_PXA_HAVE_BOARD_IRQS=y
#
# Boot options
......@@ -222,6 +221,7 @@ CONFIG_CPU_CP15_MMU=y
# CONFIG_OUTER_CACHE is not set
CONFIG_IWMMXT=y
CONFIG_XSCALE_PMU=y
CONFIG_COMMON_CLKDEV=y
#
# Bus support
......@@ -237,6 +237,7 @@ CONFIG_PCMCIA_IOCTL=y
#
# PC-card bridges
#
CONFIG_PCMCIA_PXA2XX=m
#
# Kernel Features
......@@ -245,25 +246,30 @@ CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
# CONFIG_PREEMPT is not set
CONFIG_HZ=100
CONFIG_AEABI=y
CONFIG_OABI_COMPAT=y
# CONFIG_ARCH_DISCONTIGMEM_ENABLE is not set
CONFIG_ARCH_FLATMEM_HAS_HOLES=y
# CONFIG_ARCH_SPARSEMEM_DEFAULT is not set
# CONFIG_ARCH_SELECT_MEMORY_MODEL is not set
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
# CONFIG_SPARSEMEM_VMEMMAP_ENABLE is not set
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_SPLIT_PTLOCK_CPUS=4096
# CONFIG_RESOURCES_64BIT is not set
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
# CONFIG_PHYS_ADDR_T_64BIT is not set
CONFIG_ZONE_DMA_FLAG=0
CONFIG_VIRT_TO_BUS=y
CONFIG_UNEVICTABLE_LRU=y
CONFIG_ALIGNMENT_TRAP=y
#
......@@ -277,9 +283,10 @@ CONFIG_KEXEC=y
CONFIG_ATAGS_PROC=y
#
# CPU Frequency scaling
# CPU Power Management
#
# CONFIG_CPU_FREQ is not set
# CONFIG_CPU_IDLE is not set
#
# Floating point emulation
......@@ -296,6 +303,8 @@ CONFIG_FPE_NWFPE=y
# Userspace binary formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
CONFIG_HAVE_AOUT=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=y
......@@ -309,10 +318,6 @@ CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_APM_EMULATION is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
#
# Networking
#
CONFIG_NET=y
#
......@@ -339,7 +344,7 @@ CONFIG_IP_FIB_HASH=y
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
CONFIG_INET_TUNNEL=y
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
......@@ -350,25 +355,7 @@ CONFIG_INET_TCP_DIAG=y
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
CONFIG_IPV6=y
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_IPV6_ROUTER_PREF is not set
# CONFIG_IPV6_OPTIMISTIC_DAD is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_MIP6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
CONFIG_INET6_XFRM_MODE_TRANSPORT=y
CONFIG_INET6_XFRM_MODE_TUNNEL=y
CONFIG_INET6_XFRM_MODE_BEET=y
# CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION is not set
CONFIG_IPV6_SIT=y
CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_IPV6_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
......@@ -376,6 +363,7 @@ CONFIG_IPV6_NDISC_NODETYPE=y
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
......@@ -421,25 +409,18 @@ CONFIG_IRDA_FAST_RR=y
#
# Dongle support
#
# CONFIG_KINGSUN_DONGLE is not set
# CONFIG_KSDAZZLE_DONGLE is not set
# CONFIG_KS959_DONGLE is not set
#
# FIR device drivers
#
# CONFIG_USB_IRDA is not set
# CONFIG_SIGMATEL_FIR is not set
CONFIG_PXA_FICP=y
# CONFIG_MCS_FIR is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
#
# Wireless
#
# CONFIG_PHONET is not set
CONFIG_WIRELESS=y
CONFIG_CFG80211=m
CONFIG_NL80211=y
CONFIG_WIRELESS_OLD_REGULATORY=y
CONFIG_WIRELESS_EXT=y
CONFIG_WIRELESS_EXT_SYSFS=y
CONFIG_MAC80211=m
......@@ -448,7 +429,9 @@ CONFIG_MAC80211=m
# Rate control algorithm selection
#
CONFIG_MAC80211_RC_PID=y
# CONFIG_MAC80211_RC_MINSTREL is not set
CONFIG_MAC80211_RC_DEFAULT_PID=y
# CONFIG_MAC80211_RC_DEFAULT_MINSTREL is not set
CONFIG_MAC80211_RC_DEFAULT="pid"
# CONFIG_MAC80211_MESH is not set
# CONFIG_MAC80211_LEDS is not set
......@@ -539,11 +522,12 @@ CONFIG_MTD_NAND=m
# CONFIG_MTD_NAND_VERIFY_WRITE is not set
# CONFIG_MTD_NAND_ECC_SMC is not set
# CONFIG_MTD_NAND_MUSEUM_IDS is not set
# CONFIG_MTD_NAND_GPIO is not set
CONFIG_MTD_NAND_IDS=m
# CONFIG_MTD_NAND_DISKONCHIP is not set
# CONFIG_MTD_NAND_SHARPSL is not set
CONFIG_MTD_NAND_TMIO=m
# CONFIG_MTD_NAND_PLATFORM is not set
# CONFIG_MTD_ALAUDA is not set
# CONFIG_MTD_ONENAND is not set
#
......@@ -556,13 +540,13 @@ CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_MISC_DEVICES=y
# CONFIG_EEPROM_93CX6 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_C2PORT is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
......@@ -632,37 +616,25 @@ CONFIG_NETDEVICES=y
CONFIG_WLAN_80211=y
# CONFIG_PCMCIA_RAYCS is not set
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
CONFIG_HERMES=m
CONFIG_PCMCIA_HERMES=m
# CONFIG_PCMCIA_SPECTRUM is not set
# CONFIG_ATMEL is not set
# CONFIG_AIRO_CS is not set
# CONFIG_PCMCIA_WL3501 is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
# CONFIG_RTL8187 is not set
# CONFIG_MAC80211_HWSIM is not set
# CONFIG_P54_COMMON is not set
# CONFIG_IWLWIFI_LEDS is not set
# CONFIG_HOSTAP is not set
# CONFIG_B43 is not set
# CONFIG_B43LEGACY is not set
# CONFIG_ZD1211RW is not set
# CONFIG_RT2X00 is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
CONFIG_NET_PCMCIA=y
# CONFIG_PCMCIA_3C589 is not set
# CONFIG_PCMCIA_3C574 is not set
# CONFIG_PCMCIA_FMVJ18X is not set
CONFIG_PCMCIA_PCNET=m
# CONFIG_PCMCIA_PCNET is not set
# CONFIG_PCMCIA_NMCLAN is not set
# CONFIG_PCMCIA_SMC91C92 is not set
# CONFIG_PCMCIA_XIRC2PS is not set
......@@ -714,13 +686,11 @@ CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
# CONFIG_TOUCHSCREEN_TOUCHWIN is not set
# CONFIG_TOUCHSCREEN_UCB1400 is not set
CONFIG_TOUCHSCREEN_WM97XX=m
CONFIG_TOUCHSCREEN_WM9705=y
CONFIG_TOUCHSCREEN_WM9712=y
CONFIG_TOUCHSCREEN_WM9713=y
# CONFIG_TOUCHSCREEN_WM97XX_MAINSTONE is not set
# CONFIG_TOUCHSCREEN_USB_COMPOSITE is not set
# CONFIG_TOUCHSCREEN_TOUCHIT213 is not set
# CONFIG_INPUT_MISC is not set
......@@ -749,11 +719,13 @@ CONFIG_DEVKMEM=y
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_PXA is not set
CONFIG_SERIAL_PXA=y
# CONFIG_SERIAL_PXA_CONSOLE is not set
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=m
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_R3964 is not set
......@@ -772,6 +744,10 @@ CONFIG_ARCH_REQUIRE_GPIOLIB=y
CONFIG_GPIOLIB=y
# CONFIG_GPIO_SYSFS is not set
#
# Memory mapped GPIO expanders:
#
#
# I2C GPIO expanders:
#
......@@ -786,12 +762,14 @@ CONFIG_GPIOLIB=y
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set
# CONFIG_THERMAL is not set
# CONFIG_THERMAL_HWMON is not set
# CONFIG_WATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
#
# Sonics Silicon Backplane
#
CONFIG_SSB_POSSIBLE=y
# CONFIG_SSB is not set
#
......@@ -799,8 +777,13 @@ CONFIG_SSB_POSSIBLE=y
#
CONFIG_MFD_CORE=y
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_ASIC3 is not set
# CONFIG_HTC_EGPIO is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_UCB1400_CORE is not set
CONFIG_MFD_TMIO=y
CONFIG_MFD_T7L66XB=y
CONFIG_MFD_TC6387XB=y
CONFIG_MFD_TC6393XB=y
#
......@@ -827,6 +810,7 @@ CONFIG_MFD_TC6393XB=y
CONFIG_FB=y
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_BOOT_VESA_SUPPORT is not set
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
......@@ -851,8 +835,10 @@ CONFIG_FB_PXA=y
# CONFIG_FB_PXA_PARAMETERS is not set
# CONFIG_FB_MBX is not set
CONFIG_FB_W100=y
# CONFIG_FB_AM200EPD is not set
# CONFIG_FB_TMIO is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=y
# CONFIG_LCD_ILI9320 is not set
......@@ -886,6 +872,7 @@ CONFIG_FONT_MINI_4x6=y
# CONFIG_FONT_10x18 is not set
# CONFIG_LOGO is not set
CONFIG_SOUND=y
CONFIG_SOUND_OSS_CORE=y
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
......@@ -899,14 +886,18 @@ CONFIG_SND_SUPPORT_OLD_API=y
CONFIG_SND_VERBOSE_PROCFS=y
CONFIG_SND_VERBOSE_PRINTK=y
# CONFIG_SND_DEBUG is not set
CONFIG_SND_VMASTER=y
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_DRIVERS=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
# CONFIG_SND_AC97_POWER_SAVE is not set
CONFIG_SND_ARM=y
CONFIG_SND_PXA2XX_LIB=m
CONFIG_SND_PXA2XX_LIB_AC97=y
# CONFIG_SND_PXA2XX_AC97 is not set
# CONFIG_SND_USB is not set
# CONFIG_SND_PCMCIA is not set
CONFIG_SND_SOC=m
CONFIG_SND_SOC_AC97_BUS=y
......@@ -920,133 +911,19 @@ CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set
# CONFIG_HIDRAW is not set
# CONFIG_HID_PID is not set
#
# USB Input Devices
# Special HID drivers
#
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
# CONFIG_USB_ARCH_HAS_OHCI is not set
# CONFIG_USB_ARCH_HAS_EHCI is not set
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
# CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
#
# Miscellaneous USB options
#
# CONFIG_USB_DEVICEFS is not set
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_WDM is not set
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#
#
# may also be needed; see USB_STORAGE Help for more information
#
# CONFIG_USB_STORAGE is not set
# CONFIG_USB_LIBUSUAL is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
CONFIG_USB_MON=y
#
# USB port drivers
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_ISIGHTFW is not set
CONFIG_USB_GADGET=y
# CONFIG_USB_GADGET_DEBUG_FILES is not set
CONFIG_USB_GADGET_SELECTED=y
# CONFIG_USB_GADGET_AMD5536UDC is not set
# CONFIG_USB_GADGET_ATMEL_USBA is not set
# CONFIG_USB_GADGET_FSL_USB2 is not set
# CONFIG_USB_GADGET_NET2280 is not set
CONFIG_USB_GADGET_PXA25X=y
CONFIG_USB_PXA25X=y
CONFIG_USB_PXA25X_SMALL=y
# CONFIG_USB_GADGET_M66592 is not set
# CONFIG_USB_GADGET_PXA27X is not set
# CONFIG_USB_GADGET_GOKU is not set
# CONFIG_USB_GADGET_LH7A40X is not set
# CONFIG_USB_GADGET_OMAP is not set
# CONFIG_USB_GADGET_S3C2410 is not set
# CONFIG_USB_GADGET_AT91 is not set
# CONFIG_USB_GADGET_DUMMY_HCD is not set
# CONFIG_USB_GADGET_DUALSPEED is not set
# CONFIG_USB_ZERO is not set
CONFIG_USB_ETH=m
# CONFIG_USB_ETH_RNDIS is not set
# CONFIG_USB_GADGETFS is not set
# CONFIG_USB_FILE_STORAGE is not set
# CONFIG_USB_G_SERIAL is not set
# CONFIG_USB_MIDI_GADGET is not set
# CONFIG_USB_G_PRINTER is not set
# CONFIG_USB_CDC_COMPOSITE is not set
CONFIG_HID_COMPAT=y
# CONFIG_USB_SUPPORT is not set
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_UNSAFE_RESUME=y
#
# MMC/SD Card Drivers
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_BOUNCE=y
......@@ -1054,14 +931,18 @@ CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_MMC_TEST is not set
#
# MMC/SD Host Controller Drivers
# MMC/SD/SDIO Host Controller Drivers
#
# CONFIG_MMC_PXA is not set
# CONFIG_MMC_SDHCI is not set
CONFIG_MMC_TMIO=y
# CONFIG_MEMSTICK is not set
# CONFIG_ACCESSIBILITY is not set
# CONFIG_NEW_LEDS is not set
CONFIG_RTC_LIB=y
# CONFIG_RTC_CLASS is not set
# CONFIG_DMADEVICES is not set
# CONFIG_REGULATOR is not set
# CONFIG_UIO is not set
#
......@@ -1070,11 +951,17 @@ CONFIG_RTC_LIB=y
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_EXT2_FS_XIP is not set
# CONFIG_EXT3_FS is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
# CONFIG_EXT4_FS is not set
CONFIG_JBD=m
CONFIG_FS_MBCACHE=m
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
CONFIG_FILE_LOCKING=y
# CONFIG_XFS_FS is not set
# CONFIG_OCFS2_FS is not set
CONFIG_DNOTIFY=y
......@@ -1106,6 +993,7 @@ CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
......@@ -1142,6 +1030,7 @@ CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_REGISTER_V4 is not set
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
......@@ -1228,13 +1117,15 @@ CONFIG_FRAME_WARN=1024
# CONFIG_DEBUG_BUGVERBOSE is not set
# CONFIG_DEBUG_MEMORY_INIT is not set
CONFIG_FRAME_POINTER=y
# CONFIG_RCU_CPU_STALL_DETECTOR is not set
# CONFIG_LATENCYTOP is not set
CONFIG_HAVE_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
# CONFIG_FTRACE is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_CONTEXT_SWITCH_TRACER is not set
CONFIG_SYSCTL_SYSCALL_CHECK=y
CONFIG_HAVE_FUNCTION_TRACER=y
#
# Tracers
#
# CONFIG_DYNAMIC_PRINTK_DEBUG is not set
# CONFIG_SAMPLES is not set
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_DEBUG_USER is not set
......@@ -1244,15 +1135,23 @@ CONFIG_HAVE_ARCH_KGDB=y
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
# CONFIG_SECURITYFS is not set
# CONFIG_SECURITY_FILE_CAPABILITIES is not set
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
# CONFIG_CRYPTO_FIPS is not set
CONFIG_CRYPTO_ALGAPI=m
CONFIG_CRYPTO_ALGAPI2=m
CONFIG_CRYPTO_AEAD2=m
CONFIG_CRYPTO_BLKCIPHER=m
CONFIG_CRYPTO_BLKCIPHER2=m
CONFIG_CRYPTO_HASH2=m
CONFIG_CRYPTO_RNG2=m
CONFIG_CRYPTO_MANAGER=m
CONFIG_CRYPTO_MANAGER2=m
# CONFIG_CRYPTO_GF128MUL is not set
# CONFIG_CRYPTO_NULL is not set
# CONFIG_CRYPTO_CRYPTD is not set
......@@ -1324,14 +1223,17 @@ CONFIG_CRYPTO_ARC4=m
#
# CONFIG_CRYPTO_DEFLATE is not set
# CONFIG_CRYPTO_LZO is not set
#
# Random Number Generation
#
# CONFIG_CRYPTO_ANSI_CPRNG is not set
CONFIG_CRYPTO_HW=y
#
# Library routines
#
CONFIG_BITREVERSE=y
# CONFIG_GENERIC_FIND_FIRST_BIT is not set
# CONFIG_GENERIC_FIND_NEXT_BIT is not set
CONFIG_CRC_CCITT=y
# CONFIG_CRC16 is not set
# CONFIG_CRC_T10DIF is not set
......
arch/arm/configs/h5000_defconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/kirkwood_defconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/ks8695_defconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/mx31moboard_defconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/mx31pdk_defconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/neocore926_defconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/netx_defconfig
浏览文件 @ 923a789b
......@@ -728,9 +728,9 @@ CONFIG_RTC_CLASS=m
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
#
# RTC drivers
......
arch/arm/configs/omap3_pandora_defconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/omap_ldp_defconfig
浏览文件 @ 923a789b
......@@ -316,7 +316,82 @@ CONFIG_BINFMT_MISC=y
#
# CONFIG_PM is not set
CONFIG_ARCH_SUSPEND_POSSIBLE=y
# CONFIG_NET is not set
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_UNIX=y
CONFIG_XFRM=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
CONFIG_XFRM_MIGRATE=y
# CONFIG_XFRM_STATISTICS is not set
CONFIG_NET_KEY=y
CONFIG_NET_KEY_MIGRATE=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_INET_XFRM_MODE_TRANSPORT=y
CONFIG_INET_XFRM_MODE_TUNNEL=y
CONFIG_INET_XFRM_MODE_BEET=y
# CONFIG_INET_LRO is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_NET_DSA is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_CAN is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set
# CONFIG_PHONET is not set
# CONFIG_WIRELESS is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set
#
# Device Drivers
......@@ -332,6 +407,8 @@ CONFIG_PREVENT_FIRMWARE_BUILD=y
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
......@@ -390,6 +467,54 @@ CONFIG_SCSI_LOWLEVEL=y
# CONFIG_SCSI_DH is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set
CONFIG_NETDEVICES=y
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_VETH is not set
# CONFIG_PHYLIB is not set
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_AX88796 is not set
# CONFIG_SMC91X is not set
# CONFIG_DM9000 is not set
# CONFIG_ENC28J60 is not set
CONFIG_SMC911X=y
# CONFIG_IBM_NEW_EMAC_ZMII is not set
# CONFIG_IBM_NEW_EMAC_RGMII is not set
# CONFIG_IBM_NEW_EMAC_TAH is not set
# CONFIG_IBM_NEW_EMAC_EMAC4 is not set
# CONFIG_IBM_NEW_EMAC_NO_FLOW_CTRL is not set
# CONFIG_IBM_NEW_EMAC_MAL_CLR_ICINTSTAT is not set
# CONFIG_IBM_NEW_EMAC_MAL_COMMON_ERR is not set
# CONFIG_B44 is not set
CONFIG_NETDEV_1000=y
CONFIG_NETDEV_10000=y
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set
# CONFIG_IWLWIFI_LEDS is not set
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
#
# Input device support
......@@ -816,6 +941,27 @@ CONFIG_TMPFS=y
# CONFIG_ROMFS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
CONFIG_ROOT_NFS=y
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_REGISTER_V4 is not set
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
......
arch/arm/configs/picotux200_defconfig
浏览文件 @ 923a789b
......@@ -1069,9 +1069,9 @@ CONFIG_RTC_CLASS=m
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=m
CONFIG_RTC_INTF_PROC=m
CONFIG_RTC_INTF_DEV=m
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
#
......
arch/arm/configs/realview_defconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/s3c6400_defconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/configs/w90p910_defconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/cacheflush.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/clkdev.h 0 → 100644
浏览文件 @ 923a789b
/*
* arch/arm/include/asm/clkdev.h
*
* Copyright (C) 2008 Russell King.
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free Software Foundation.
*
* Helper for the clk API to assist looking up a struct clk.
*/
#ifndef __ASM_CLKDEV_H
#define __ASM_CLKDEV_H
struct clk;
struct clk_lookup {
struct list_head node;
const char *dev_id;
const char *con_id;
struct clk *clk;
};
struct clk_lookup *clkdev_alloc(struct clk *clk, const char *con_id,
const char *dev_fmt, ...);
void clkdev_add(struct clk_lookup *cl);
void clkdev_drop(struct clk_lookup *cl);
#endif
arch/arm/include/asm/dma-mapping.h
浏览文件 @ 923a789b
......@@ -69,7 +69,9 @@ extern void dma_cache_maint(const void *kaddr, size_t size, int rw);
*/
static inline int dma_supported(struct device *dev, u64 mask)
{
return dev->dma_mask && *dev->dma_mask != 0;
if (mask < ISA_DMA_THRESHOLD)
return 0;
return 1;
}
static inline int dma_set_mask(struct device *dev, u64 dma_mask)
......
arch/arm/include/asm/dma.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/hardware/vic.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/hwcap.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/io.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/irq.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/memory.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/mmu_context.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/mtd-xip.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/page.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/processor.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/setup.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/smp.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/string.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/system.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/include/asm/uaccess.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/armksyms.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/ftrace.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/head-common.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/module.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/thumbee.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/lib/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/lib/memset.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-aaec2000/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-aaec2000/clock.c 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-aaec2000/core.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-aaec2000/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/at91cap9.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/board-cam60.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/board-cap9adk.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/board-neocore926.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/sam9_smc.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-at91/sam9_smc.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-clps7500/Makefile.boot 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/core.c 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/acornfb.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/io.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/irq.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/irqs.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/memory.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/system.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/timex.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-clps7500/include/mach/vmalloc.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-davinci/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-davinci/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/adssphere.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/core.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/edb9302.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/edb9302a.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/edb9307.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/edb9307a.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/edb9312.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/edb9315.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/edb9315a.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/gesbc9312.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/include/mach/clkdev.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-ep93xx/micro9.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ep93xx/ts72xx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-footbridge/cats-hw.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-footbridge/common.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-footbridge/dc21285.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-footbridge/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-footbridge/ebsa285.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-footbridge/isa-irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-footbridge/personal.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-imx/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-imx/include/mach/io.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-imx/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-integrator/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-integrator/clock.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-integrator/core.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-integrator/impd1.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-integrator/include/mach/clkdev.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-iop13xx/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-ixp23xx/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-ixp4xx/common.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-kirkwood/common.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-kirkwood/common.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-kirkwood/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-kirkwood/include/mach/gpio.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-kirkwood/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ks8695/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ks8695/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ks8695/board-dsm320.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ks8695/board-micrel.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ks8695/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ks8695/gpio.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-l7200/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-lh7a40x/clocks.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-loki/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-msm/include/mach/io.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-msm/timer.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mv78xx0/common.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mv78xx0/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-mv78xx0/include/mach/gpio.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mv78xx0/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx1/Kconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx1/Makefile.boot 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx1/clock.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx1/crm_regs.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx1/devices.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx1/devices.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx1/mx1ads.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx2/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx2/devices.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx2/mx27ads.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx2/pcm038.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/devices.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/iomux.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/mx31moboard.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/mx31pdk.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-mx3/pcm037.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-netx/fb.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-netx/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-netx/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-netx/xc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-ns9xxx/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-ns9xxx/time-ns9360.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-fsample.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-h2-mmc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-h2.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-h3-mmc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-h3.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-osk.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-palmte.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-palmtt.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-palmz71.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-sx1-mmc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/board-sx1.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/clock.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/fpga.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/id.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/leds-osk.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/leds.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/pm.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/serial.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap1/timer32k.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/board-2430sdp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/board-apollon.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/board-generic.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/board-h4.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/board-ldp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/board-omap3pandora.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/board-overo.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/clock24xx.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/clock34xx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/clock34xx.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/id.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/mmc-twl4030.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/mmc-twl4030.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/timer-gp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-omap2/usb-tusb6010.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-orion5x/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-orion5x/common.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-orion5x/common.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-orion5x/gpio.c 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-orion5x/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-orion5x/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-orion5x/mpp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pnx4008/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/am200epd.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/clock.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/cm-x2xx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/cm-x300.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/corgi.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/cpufreq-pxa2xx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/devices.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/e330.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/e350.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/e400.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/e740.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/e750.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/e800.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/eseries.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/eseries.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/ezx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/generic.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/gpio.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/gumstix.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/h5000.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/imote2.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/include/mach/clkdev.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/include/mach/h5000.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/include/mach/io.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/include/mach/regs-ac97.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/include/mach/regs-uart.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/littleton.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/magician.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/mainstone.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/mfp-pxa2xx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/mioa701.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/poodle.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/pwm.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/pxa25x.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/pxa27x.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/pxa300.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/pxa320.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/pxa3xx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/saar.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/smemc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/spitz.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/ssp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/tavorevb.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/tosa.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/zylonite.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-pxa/zylonite_pxa320.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/clock.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/core.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/core.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/hotplug.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/include/mach/board-pba8.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/include/mach/clkdev.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-realview/localtimer.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/platsmp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-realview/realview_pba8.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-rpc/include/mach/io.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/include/mach/gpio-core.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/include/mach/tick.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/mach-bast.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/mach-h1940.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/mach-n30.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/mach-otom.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/mach-qt2410.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/mach-vr1000.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2410/s3c2410.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2412/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2412/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2412/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2412/mach-jive.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2412/mach-vstms.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2412/s3c2412.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2440/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2440/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2440/mach-anubis.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2440/mach-osiris.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2440/mach-rx3715.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2442/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2443/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2443/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2443/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c2443/s3c2443.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c24a0/include/mach/debug-macro.S 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c24a0/include/mach/irqs.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c24a0/include/mach/map.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c24a0/include/mach/regs-clock.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c24a0/include/mach/regs-irq.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c24a0/include/mach/tick.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/Kconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/Makefile 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/Makefile.boot 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/debug-macro.S 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/dma.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/entry-macro.S 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/gpio-core.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/gpio.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/hardware.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/irqs.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/map.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/pwm-clock.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/regs-fb.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/system.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/tick.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6400/include/mach/uncompress.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6410/Kconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6410/Makefile 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6410/cpu.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6410/mach-smdk6410.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-s3c6410/setup-sdhci.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/collie.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/collie_pm.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/cpu-sa1100.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/cpu-sa1110.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/pleb.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/shannon.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/sleep.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-sa1100/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-shark/core.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-versatile/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-versatile/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-versatile/clock.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-versatile/core.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-versatile/include/mach/clkdev.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-versatile/include/mach/dma.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mach-w90x900/Kconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/Makefile 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/Makefile.boot 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/cpu.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/entry-macro.S 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/irqs.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/map.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/regs-irq.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/regs-serial.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/regs-timer.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/system.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/timex.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/uncompress.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/include/mach/vmalloc.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/irq.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/mach-w90p910evb.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/time.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mach-w90x900/w90p910.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/alignment.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/cache-v3.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/cache-v4.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/cache-v4wt.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/cache-v7.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/copypage-feroceon.S 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mm/copypage-feroceon.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/copypage-v3.S 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mm/copypage-v3.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/copypage-v4mc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/copypage-v4wb.S 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mm/copypage-v4wb.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/copypage-v4wt.S 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/arm/mm/copypage-v4wt.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/copypage-v6.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/copypage-xscale.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/fault.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/init.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/mm.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/mmu.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/nommu.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/pgd.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/proc-syms.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/proc-v6.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/proc-v7.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/mm/proc-xsc3.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/oprofile/op_model_mpcore.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/dma-mx1-mx2.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/gpio.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/include/mach/board-mx31pdk.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/include/mach/io.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/include/mach/mtd-xip.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/include/mach/mx1.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/iomux-mx1-mx2.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-mxc/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/debug-devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/debug-leds.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/dmtimer.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/gpio.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/i2c.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-omap/sram.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-orion/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-orion/gpio.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-orion/include/plat/gpio.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-orion/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/clock.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/dev-fb.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/dev-hsmmc.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/dev-hsmmc1.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/dev-i2c0.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/dev-i2c1.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/gpio-config.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/gpio.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/mach/io.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/adc.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/cpu-freq.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/fb.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/gpio-cfg-helpers.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/gpio-cfg.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/gpio-core.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/iic-core.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/regs-fb.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/regs-irqtype.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/regs-sdhci.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/include/plat/sdhci.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c/init.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/adc.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/clock-dclk.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/clock.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/common-smdk.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/cpu.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/devs.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/dma.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/gpiolib.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/include/mach/pwm-clock.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/include/plat/map.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/include/plat/pll.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/pm.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/s3c244x.c
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/s3c244x.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/setup-i2c.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/spi-bus0-gpe11_12_13.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c24xx/spi-bus1-gpg5_6_7.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/Kconfig 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/Makefile 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/clock.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/cpu.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/dev-uart.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/gpiolib.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-a.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-b.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-c.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-d.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-e.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-f.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-g.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-h.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-i.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-j.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-n.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-o.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-p.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/gpio-bank-q.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/irqs.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/pll.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/regs-clock.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/regs-gpio.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/regs-sys.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/s3c6400.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/include/plat/s3c6410.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/irq-eint.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/irq.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/s3c6400-clock.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/s3c6400-init.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/setup-fb-24bpp.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/setup-i2c0.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/plat-s3c64xx/setup-i2c1.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/tools/mach-types
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/vfp/vfp.h
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/vfp/vfphw.S
浏览文件 @ 923a789b
此差异已折叠。
arch/arm/vfp/vfpmodule.c
浏览文件 @ 923a789b
此差异已折叠。
arch/avr32/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/avr32/kernel/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/blackfin/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/blackfin/kernel/time-ts.c
浏览文件 @ 923a789b
此差异已折叠。
arch/cris/arch-v32/kernel/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/cris/arch-v32/kernel/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/cris/include/asm/smp.h
浏览文件 @ 923a789b
此差异已折叠。
arch/cris/kernel/process.c
浏览文件 @ 923a789b
此差异已折叠。
arch/frv/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/h8300/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/hp/sim/hpsim_irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/include/asm/kvm.h
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/include/asm/kvm_host.h
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/include/asm/smp.h
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/include/asm/topology.h
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kernel/iosapic.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kernel/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kernel/msi_ia64.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kernel/smpboot.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kernel/topology.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/asm-offsets.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/kvm-ia64.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/kvm_minstate.h
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/misc.h
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/mmio.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/process.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/vcpu.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/vcpu.h
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/vmm.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/vmm_ivt.S
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/kvm/vtlb.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/sn/kernel/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/ia64/sn/kernel/msi_sn.c
浏览文件 @ 923a789b
此差异已折叠。
arch/m32r/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/m32r/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/m32r/kernel/smpboot.c
浏览文件 @ 923a789b
此差异已折叠。
arch/m68k/kernel/process.c
浏览文件 @ 923a789b
此差异已折叠。
arch/m68knommu/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/include/asm/irq.h
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/include/asm/smp.h
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/jazz/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/cevt-bcm1480.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/cevt-ds1287.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/cevt-gt641xx.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/cevt-r4k.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/cevt-sb1250.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/cevt-smtc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/cevt-txx9.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/i8253.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/irq-gic.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/smp-cmp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/smp-mt.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/kernel/smtc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/mti-malta/malta-smtc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/nxp/pnx8550/common/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/pmc-sierra/yosemite/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/sgi-ip27/ip27-smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/sgi-ip27/ip27-timer.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/sibyte/bcm1480/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/sibyte/bcm1480/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/sibyte/sb1250/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/sibyte/sb1250/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mips/sni/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/mn10300/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/parisc/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/parisc/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/parisc/kernel/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/parisc/kernel/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/include/asm/disassemble.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/include/asm/kvm_host.h
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/include/asm/kvm_ppc.h
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/include/asm/mmu-44x.h
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/include/asm/topology.h
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kernel/asm-offsets.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kernel/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kernel/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/44x.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/44x_emulate.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/44x_tlb.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/44x_tlb.h
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/booke.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/booke_interrupts.S
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/emulate.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/powerpc.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/timing.c 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/kvm/timing.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/sysdev/mpic.c
浏览文件 @ 923a789b
此差异已折叠。
arch/powerpc/sysdev/mpic.h
浏览文件 @ 923a789b
此差异已折叠。
arch/s390/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/s390/include/asm/kvm_virtio.h
浏览文件 @ 923a789b
此差异已折叠。
arch/s390/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/s390/kernel/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/s390/kernel/time.c
浏览文件 @ 923a789b
此差异已折叠。
arch/s390/kvm/kvm-s390.c
浏览文件 @ 923a789b
此差异已折叠。
arch/s390/mm/pgtable.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sh/include/asm/smp.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sh/include/asm/topology.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sh/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sh/kernel/smp.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sh/kernel/timers/timer-tmu.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/Kconfig
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/Kconfig.debug
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/boot/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/Kbuild
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/asm.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/atomic_64.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/bitops_64.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/hypervisor.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/irq_32.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/irq_64.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/module.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/module_32.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/include/asm/module_64.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/include/asm/oplib_32.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/pil.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/scatterlist_32.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/include/asm/scatterlist_64.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/include/asm/sections.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/sections_32.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/include/asm/sections_64.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/include/asm/smp_32.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/spitfire.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/system_32.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/system_64.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/tsb.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/ttable.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/unistd.h
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/include/asm/unistd_32.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/include/asm/unistd_64.h 已删除 100644 → 0
浏览文件 @ 103ceffb
此差异已折叠。
arch/sparc/kernel/.gitignore 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/Makefile
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/asm-offsets.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/cpu.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/devices.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/idprom.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/init_task.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/ioport.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/kernel.h 0 → 100644
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/module.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/muldiv.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/pcic.c
浏览文件 @ 923a789b
此差异已折叠。
arch/sparc/kernel/pmc.c
浏览文件 @ 923a789b
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或