Skip to content

cloud-kernel
cloud-kernel

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

通知 170
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 1b62f19c 编写于 作者: M Mauro Carvalho Chehab
浏览文件
操作

Merge tag 'v3.18-rc1' into v4l_for_linus 

Linux 3.18-rc1

* tag 'v3.18-rc1': (9167 commits)
  Linux 3.18-rc1
  MAINTAINERS: corrected bcm2835 search
  Net: DSA: Fix checking for get_phy_flags function
  sparc64: Do not define thread fpregs save area as zero-length array.
  sparc64: Fix corrupted thread fault code.
  MAINTAINERS: Become the docs maintainer
  x86,kvm,vmx: Preserve CR4 across VM entry
  ipv6: fix a potential use after free in sit.c
  ipv6: fix a potential use after free in ip6_offload.c
  ipv4: fix a potential use after free in gre_offload.c
  tcp: fix build error if IPv6 is not enabled
  futex: Ensure get_futex_key_refs() always implies a barrier
  bna: fix skb->truesize underestimation
  net: dsa: add includes for ethtool and phy_fixed definitions
  openvswitch: Set flow-key members.
  netrom: use linux/uaccess.h
  dsa: Fix conversion from host device to mii bus
  tipc: fix bug in bundled buffer reception
  ipv6: introduce tcp_v6_iif()
  sfc: add support for skb->xmit_more
  ...
上级 a66d05d5 f114040e
展开全部 隐藏空白更改
内联 并排
Showing with 30456 addition and 13363 deletion

要显示的变更太多。

To preserve performance only 1000 of 1000+ files are displayed.
文本差异 电子邮件补丁
Documentation/.gitignore 已删除 100644 → 0
浏览文件 @ a66d05d5
filesystems/dnotify_test
laptops/dslm
timers/hpet_example
vm/hugepage-mmap
vm/hugepage-shm
vm/map_hugetlb
Documentation/00-INDEX
浏览文件 @ 1b62f19c
......@@ -287,6 +287,8 @@ local_ops.txt
- semantics and behavior of local atomic operations.
lockdep-design.txt
- documentation on the runtime locking correctness validator.
locking/
- directory with info about kernel locking primitives
lockstat.txt
- info on collecting statistics on locks (and contention).
lockup-watchdogs.txt
......
Documentation/ABI/removed/net_dma 0 → 100644
浏览文件 @ 1b62f19c
What: tcp_dma_copybreak sysctl
Date: Removed in kernel v3.13
Contact: Dan Williams <dan.j.williams@intel.com>
Description:
Formerly the lower limit, in bytes, of the size of socket reads
that will be offloaded to a DMA copy engine. Removed due to
coherency issues of the cpu potentially touching the buffers
while dma is in flight.
Documentation/ABI/stable/sysfs-devices-node
浏览文件 @ 1b62f19c
......@@ -85,14 +85,6 @@ Description:
will be compacted. When it completes, memory will be freed
into blocks which have as many contiguous pages as possible
What: /sys/devices/system/node/nodeX/scan_unevictable_pages
Date: October 2008
Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>
Description:
When set, it triggers scanning the node's unevictable lists
and move any pages that have become evictable onto the respective
zone's inactive list. See mm/vmscan.c
What: /sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
Date: December 2009
Contact: Lee Schermerhorn <lee.schermerhorn@hp.com>
......
Documentation/ABI/testing/configfs-usb-gadget-uac1 0 → 100644
浏览文件 @ 1b62f19c
What: /config/usb-gadget/gadget/functions/uac1.name
Date: Sep 2014
KernelVersion: 3.18
Description:
The attributes:
audio_buf_size - audio buffer size
fn_cap - capture pcm device file name
fn_cntl - control device file name
fn_play - playback pcm device file name
req_buf_size - ISO OUT endpoint request buffer size
req_count - ISO OUT endpoint request count
Documentation/ABI/testing/configfs-usb-gadget-uac2 0 → 100644
浏览文件 @ 1b62f19c
What: /config/usb-gadget/gadget/functions/uac2.name
Date: Sep 2014
KernelVersion: 3.18
Description:
The attributes:
c_chmask - capture channel mask
c_srate - capture sampling rate
c_ssize - capture sample size (bytes)
p_chmask - playback channel mask
p_srate - playback sampling rate
p_ssize - playback sample size (bytes)
Documentation/ABI/testing/sysfs-block
浏览文件 @ 1b62f19c
......@@ -53,6 +53,14 @@ Description:
512 bytes of data.
What: /sys/block/<disk>/integrity/device_is_integrity_capable
Date: July 2014
Contact: Martin K. Petersen <martin.petersen@oracle.com>
Description:
Indicates whether a storage device is capable of storing
integrity metadata. Set if the device is T10 PI-capable.
What: /sys/block/<disk>/integrity/write_generate
Date: June 2008
Contact: Martin K. Petersen <martin.petersen@oracle.com>
......
Documentation/ABI/testing/sysfs-block-zram
浏览文件 @ 1b62f19c
......@@ -77,11 +77,14 @@ What: /sys/block/zram<id>/notify_free
Date: August 2010
Contact: Nitin Gupta <ngupta@vflare.org>
Description:
The notify_free file is read-only and specifies the number of
swap slot free notifications received by this device. These
notifications are sent to a swap block device when a swap slot
is freed. This statistic is applicable only when this disk is
being used as a swap disk.
The notify_free file is read-only. Depending on device usage
scenario it may account a) the number of pages freed because
of swap slot free notifications or b) the number of pages freed
because of REQ_DISCARD requests sent by bio. The former ones
are sent to a swap block device when a swap slot is freed, which
implies that this disk is being used as a swap disk. The latter
ones are sent by filesystem mounted with discard option,
whenever some data blocks are getting discarded.
What: /sys/block/zram<id>/zero_pages
Date: August 2010
......@@ -119,3 +122,22 @@ Description:
efficiency can be calculated using compr_data_size and this
statistic.
Unit: bytes
What: /sys/block/zram<id>/mem_used_max
Date: August 2014
Contact: Minchan Kim <minchan@kernel.org>
Description:
The mem_used_max file is read/write and specifies the amount
of maximum memory zram have consumed to store compressed data.
For resetting the value, you should write "0". Otherwise,
you could see -EINVAL.
Unit: bytes
What: /sys/block/zram<id>/mem_limit
Date: August 2014
Contact: Minchan Kim <minchan@kernel.org>
Description:
The mem_limit file is read/write and specifies the maximum
amount of memory ZRAM can use to store the compressed data. The
limit could be changed in run time and "0" means disable the
limit. No limit is the initial state. Unit: bytes
Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7
浏览文件 @ 1b62f19c
What: /sys/bus/event_source/devices/hv_24x7/interface/catalog
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
Provides access to the binary "24x7 catalog" provided by the
hypervisor on POWER7 and 8 systems. This catalog lists events
......@@ -10,14 +10,14 @@ Description:
What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_length
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
A number equal to the length in bytes of the catalog. This is
also extractable from the provided binary "catalog" sysfs entry.
What: /sys/bus/event_source/devices/hv_24x7/interface/catalog_version
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
Exposes the "version" field of the 24x7 catalog. This is also
extractable from the provided binary "catalog" sysfs entry.
Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci
浏览文件 @ 1b62f19c
What: /sys/bus/event_source/devices/hv_gpci/interface/collect_privileged
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
'0' if the hypervisor is configured to forbid access to event
counters being accumulated by other guests and to physical
......@@ -9,35 +9,35 @@ Description:
What: /sys/bus/event_source/devices/hv_gpci/interface/ga
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
0 or 1. Indicates whether we have access to "GA" events (listed
in arch/powerpc/perf/hv-gpci.h).
What: /sys/bus/event_source/devices/hv_gpci/interface/expanded
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
0 or 1. Indicates whether we have access to "EXPANDED" events (listed
in arch/powerpc/perf/hv-gpci.h).
What: /sys/bus/event_source/devices/hv_gpci/interface/lab
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
0 or 1. Indicates whether we have access to "LAB" events (listed
in arch/powerpc/perf/hv-gpci.h).
What: /sys/bus/event_source/devices/hv_gpci/interface/version
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
A number indicating the version of the gpci interface that the
hypervisor reports supporting.
What: /sys/bus/event_source/devices/hv_gpci/interface/kernel_version
Date: February 2014
Contact: Cody P Schafer <cody@linux.vnet.ibm.com>
Contact: Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
Description:
A number indicating the latest version of the gpci interface
that the kernel is aware of.
Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150 0 → 100644
浏览文件 @ 1b62f19c
What: /sys/bus/iio/devices/triggerX/name = "bmc150_accel-any-motion-devX"
KernelVersion: 3.17
Contact: linux-iio@vger.kernel.org
Description:
The BMC150 accelerometer kernel module provides an additional trigger,
which sets driver in a mode, where data is pushed to the buffer
only when there is any motion.
Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160 0 → 100644
浏览文件 @ 1b62f19c
What: /sys/bus/iio/devices/triggerX/name = "bmg160-any-motion-devX"
KernelVersion: 3.17
Contact: linux-iio@vger.kernel.org
Description:
The BMG160 gyro kernel module provides an additional trigger,
which sets driver in a mode, where data is pushed to the buffer
only when there is any motion.
Documentation/ABI/testing/sysfs-bus-pci
浏览文件 @ 1b62f19c
......@@ -65,6 +65,16 @@ Description:
force a rescan of all PCI buses in the system, and
re-discover previously removed devices.
What: /sys/bus/pci/devices/.../msi_bus
Date: September 2014
Contact: Linux PCI developers <linux-pci@vger.kernel.org>
Description:
Writing a zero value to this attribute disallows MSI and
MSI-X for any future drivers of the device. If the device
is a bridge, MSI and MSI-X will be disallowed for future
drivers of all child devices under the bridge. Drivers
must be reloaded for the new setting to take effect.
What: /sys/bus/pci/devices/.../msi_irqs/
Date: September, 2011
Contact: Neil Horman <nhorman@tuxdriver.com>
......
Documentation/ABI/testing/sysfs-class-cxl 0 → 100644
浏览文件 @ 1b62f19c
Slave contexts (eg. /sys/class/cxl/afu0.0s):
What: /sys/class/cxl/<afu>/irqs_max
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read/write
Decimal value of maximum number of interrupts that can be
requested by userspace. The default on probe is the maximum
that hardware can support (eg. 2037). Write values will limit
userspace applications to that many userspace interrupts. Must
be >= irqs_min.
What: /sys/class/cxl/<afu>/irqs_min
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Decimal value of the minimum number of interrupts that
userspace must request on a CXL_START_WORK ioctl. Userspace may
omit the num_interrupts field in the START_WORK IOCTL to get
this minimum automatically.
What: /sys/class/cxl/<afu>/mmio_size
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Decimal value of the size of the MMIO space that may be mmaped
by userspace.
What: /sys/class/cxl/<afu>/modes_supported
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
List of the modes this AFU supports. One per line.
Valid entries are: "dedicated_process" and "afu_directed"
What: /sys/class/cxl/<afu>/mode
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read/write
The current mode the AFU is using. Will be one of the modes
given in modes_supported. Writing will change the mode
provided that no user contexts are attached.
What: /sys/class/cxl/<afu>/prefault_mode
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read/write
Set the mode for prefaulting in segments into the segment table
when performing the START_WORK ioctl. Possible values:
none: No prefaulting (default)
work_element_descriptor: Treat the work element
descriptor as an effective address and
prefault what it points to.
all: all segments process calling START_WORK maps.
What: /sys/class/cxl/<afu>/reset
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: write only
Writing 1 here will reset the AFU provided there are not
contexts active on the AFU.
What: /sys/class/cxl/<afu>/api_version
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Decimal value of the current version of the kernel/user API.
What: /sys/class/cxl/<afu>/api_version_com
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Decimal value of the the lowest version of the userspace API
this this kernel supports.
Master contexts (eg. /sys/class/cxl/afu0.0m)
What: /sys/class/cxl/<afu>m/mmio_size
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Decimal value of the size of the MMIO space that may be mmaped
by userspace. This includes all slave contexts space also.
What: /sys/class/cxl/<afu>m/pp_mmio_len
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Decimal value of the Per Process MMIO space length.
What: /sys/class/cxl/<afu>m/pp_mmio_off
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Decimal value of the Per Process MMIO space offset.
Card info (eg. /sys/class/cxl/card0)
What: /sys/class/cxl/<card>/caia_version
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Identifies the CAIA Version the card implements.
What: /sys/class/cxl/<card>/psl_version
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Identifies the revision level of the PSL.
What: /sys/class/cxl/<card>/base_image
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Identifies the revision level of the base image for devices
that support loadable PSLs. For FPGAs this field identifies
the image contained in the on-adapter flash which is loaded
during the initial program load.
What: /sys/class/cxl/<card>/image_loaded
Date: September 2014
Contact: linuxppc-dev@lists.ozlabs.org
Description: read only
Will return "user" or "factory" depending on the image loaded
onto the card.
Documentation/ABI/testing/sysfs-class-net
浏览文件 @ 1b62f19c
......@@ -159,7 +159,7 @@ Description:
lower-level interface protocol used. Ethernet devices will show
a 'mtu' attribute value of 1500 unless changed.
What: /sys/calss/net/<iface>/netdev_group
What: /sys/class/net/<iface>/netdev_group
Date: January 2011
KernelVersion: 2.6.39
Contact: netdev@vger.kernel.org
......
Documentation/ABI/testing/sysfs-class-power
浏览文件 @ 1b62f19c
......@@ -18,3 +18,17 @@ Description:
This file is writeable and can be used to set the assumed
battery 'full level'. As batteries age, this value has to be
amended over time.
What: /sys/class/power_supply/max14577-charger/device/fast_charge_timer
Date: October 2014
KernelVersion: 3.18.0
Contact: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Description:
This entry shows and sets the maximum time the max14577
charger operates in fast-charge mode. When the timer expires
the device will terminate fast-charge mode (charging current
will drop to 0 A) and will trigger interrupt.
Valid values:
- 5, 6 or 7 (hours),
- 0: disabled.
Documentation/ABI/testing/sysfs-class-uwb_rc
浏览文件 @ 1b62f19c
......@@ -43,6 +43,19 @@ Description:
Reading returns the currently active channel, or -1 if
the radio controller is not beaconing.
What: /sys/class/uwb_rc/uwbN/ASIE
Date: August 2014
KernelVersion: 3.18
Contact: linux-usb@vger.kernel.org
Description:
The application-specific information element (ASIE)
included in this device's beacon, in space separated
hex octets.
Reading returns the current ASIE. Writing replaces
the current ASIE with the one written.
What: /sys/class/uwb_rc/uwbN/scan
Date: July 2008
KernelVersion: 2.6.27
......
Documentation/ABI/testing/sysfs-devices-memory
浏览文件 @ 1b62f19c
......@@ -61,6 +61,14 @@ Users: hotplug memory remove tools
http://www.ibm.com/developerworks/wikis/display/LinuxP/powerpc-utils
What: /sys/devices/system/memory/memoryX/valid_zones
Date: July 2014
Contact: Zhang Zhen <zhenzhang.zhang@huawei.com>
Description:
The file /sys/devices/system/memory/memoryX/valid_zones is
read-only and is designed to show which zone this memory
block can be onlined to.
What: /sys/devices/system/memoryX/nodeY
Date: October 2009
Contact: Linux Memory Management list <linux-mm@kvack.org>
......
Documentation/ABI/testing/sysfs-fs-f2fs
浏览文件 @ 1b62f19c
......@@ -44,6 +44,13 @@ Description:
Controls the FS utilization condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/min_fsync_blocks
Date: September 2014
Contact: "Jaegeuk Kim" <jaegeuk@kernel.org>
Description:
Controls the dirty page count condition for the in-place-update
policies.
What: /sys/fs/f2fs/<disk>/max_small_discards
Date: November 2013
Contact: "Jaegeuk Kim" <jaegeuk.kim@samsung.com>
......
Documentation/Changes
浏览文件 @ 1b62f19c
......@@ -167,18 +167,11 @@ later is recommended, due to some significant improvements).
PCMCIAutils
-----------
PCMCIAutils replaces pcmcia-cs (see below). It properly sets up
PCMCIAutils replaces pcmcia-cs. It properly sets up
PCMCIA sockets at system startup and loads the appropriate modules
for 16-bit PCMCIA devices if the kernel is modularized and the hotplug
subsystem is used.
Pcmcia-cs
---------
PCMCIA (PC Card) support is now partially implemented in the main
kernel source. The "pcmciautils" package (see above) replaces pcmcia-cs
for newest kernels.
Quota-tools
-----------
......@@ -341,17 +334,13 @@ Pcmciautils
-----------
o <ftp://ftp.kernel.org/pub/linux/utils/kernel/pcmcia/>
Pcmcia-cs
---------
o <http://pcmcia-cs.sourceforge.net/>
Quota-tools
----------
o <http://sourceforge.net/projects/linuxquota/>
DocBook Stylesheets
-------------------
o <http://nwalsh.com/docbook/dsssl/>
o <http://sourceforge.net/projects/docbook/files/docbook-dsssl/>
XMLTO XSLT Frontend
-------------------
......@@ -359,11 +348,11 @@ o <http://cyberelk.net/tim/xmlto/>
Intel P6 microcode
------------------
o <http://www.urbanmyth.org/microcode/>
o <https://downloadcenter.intel.com/>
udev
----
o <http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html>
o <http://www.freedesktop.org/software/systemd/man/udev.html>
FUSE
----
......@@ -371,7 +360,7 @@ o <http://sourceforge.net/projects/fuse>
mcelog
------
o <ftp://ftp.kernel.org/pub/linux/utils/cpu/mce/>
o <http://www.mcelog.org/>
Networking
**********
......
Documentation/CodingStyle
浏览文件 @ 1b62f19c
......@@ -675,7 +675,7 @@ the ones already enabled by DEBUG.
Many subsystems have Kconfig debug options to turn on -DDEBUG in the
corresponding Makefile; in other cases specific files #define DEBUG. And
when a debug message should be unconditionally printed, such as if it is
already inside a debug-related #ifdef secton, printk(KERN_DEBUG ...) can be
already inside a debug-related #ifdef section, printk(KERN_DEBUG ...) can be
used.
......
Documentation/DMA-API-HOWTO.txt
浏览文件 @ 1b62f19c
......@@ -531,7 +531,7 @@ To map a single region, you do:
size_t size = buffer->len;
dma_handle = dma_map_single(dev, addr, size, direction);
if (dma_mapping_error(dma_handle)) {
if (dma_mapping_error(dev, dma_handle)) {
/*
* reduce current DMA mapping usage,
* delay and try again later or
......@@ -588,7 +588,7 @@ Specifically:
size_t size = buffer->len;
dma_handle = dma_map_page(dev, page, offset, size, direction);
if (dma_mapping_error(dma_handle)) {
if (dma_mapping_error(dev, dma_handle)) {
/*
* reduce current DMA mapping usage,
* delay and try again later or
......@@ -689,7 +689,7 @@ to use the dma_sync_*() interfaces.
dma_addr_t mapping;
mapping = dma_map_single(cp->dev, buffer, len, DMA_FROM_DEVICE);
if (dma_mapping_error(dma_handle)) {
if (dma_mapping_error(cp->dev, dma_handle)) {
/*
* reduce current DMA mapping usage,
* delay and try again later or
......
Documentation/DocBook/drm.tmpl
浏览文件 @ 1b62f19c
......@@ -291,10 +291,9 @@ char *date;</synopsis>
<title>Device Registration</title>
<para>
A number of functions are provided to help with device registration.
The functions deal with PCI, USB and platform devices, respectively.
The functions deal with PCI and platform devices, respectively.
</para>
!Edrivers/gpu/drm/drm_pci.c
!Edrivers/gpu/drm/drm_usb.c
!Edrivers/gpu/drm/drm_platform.c
<para>
New drivers that no longer rely on the services provided by the
......@@ -3386,6 +3385,13 @@ void (*disable_vblank) (struct drm_device *dev, int crtc);</synopsis>
by scheduling a timer. The delay is accessible through the vblankoffdelay
module parameter or the <varname>drm_vblank_offdelay</varname> global
variable and expressed in milliseconds. Its default value is 5000 ms.
Zero means never disable, and a negative value means disable immediately.
Drivers may override the behaviour by setting the
<structname>drm_device</structname>
<structfield>vblank_disable_immediate</structfield> flag, which when set
causes vblank interrupts to be disabled immediately regardless of the
drm_vblank_offdelay value. The flag should only be set if there's a
properly working hardware vblank counter present.
</para>
<para>
When a vertical blanking interrupt occurs drivers only need to call the
......@@ -3400,6 +3406,7 @@ void (*disable_vblank) (struct drm_device *dev, int crtc);</synopsis>
<sect2>
<title>Vertical Blanking and Interrupt Handling Functions Reference</title>
!Edrivers/gpu/drm/drm_irq.c
!Finclude/drm/drmP.h drm_crtc_vblank_waitqueue
</sect2>
</sect1>
......@@ -3918,6 +3925,11 @@ int num_ioctls;</synopsis>
!Pdrivers/gpu/drm/i915/i915_cmd_parser.c batch buffer command parser
!Idrivers/gpu/drm/i915/i915_cmd_parser.c
</sect2>
<sect2>
<title>Logical Rings, Logical Ring Contexts and Execlists</title>
!Pdrivers/gpu/drm/i915/intel_lrc.c Logical Rings, Logical Ring Contexts and Execlists
!Idrivers/gpu/drm/i915/intel_lrc.c
</sect2>
</sect1>
</chapter>
</part>
......
Documentation/DocBook/kernel-locking.tmpl
浏览文件 @ 1b62f19c
......@@ -1972,7 +1972,7 @@ machines due to caching.
<itemizedlist>
<listitem>
<para>
<filename>Documentation/spinlocks.txt</filename>:
<filename>Documentation/locking/spinlocks.txt</filename>:
Linus Torvalds' spinlocking tutorial in the kernel sources.
</para>
</listitem>
......
Documentation/DocBook/media/v4l/common.xml
浏览文件 @ 1b62f19c
......@@ -110,7 +110,7 @@ makes no provisions to find these related devices. Some really
complex devices use the Media Controller (see <xref linkend="media_controller" />)
which can be used for this purpose. But most drivers do not use it,
and while some code exists that uses sysfs to discover related devices
(see libmedia_dev in the <ulink url="http://git.linuxtv.org/v4l-utils/">v4l-utils</ulink>
(see libmedia_dev in the <ulink url="http://git.linuxtv.org/cgit.cgi/v4l-utils.git/">v4l-utils</ulink>
git repository), there is no library yet that can provide a single API towards
both Media Controller-based devices and devices that do not use the Media Controller.
If you want to work on this please write to the linux-media mailing list: &v4l-ml;.</para>
......
Documentation/DocBook/usb.tmpl
浏览文件 @ 1b62f19c
......@@ -593,7 +593,7 @@ for (;;) {
Each device has one control endpoint (endpoint zero)
which supports a limited RPC style RPC access.
Devices are configured
by khubd (in the kernel) setting a device-wide
by hub_wq (in the kernel) setting a device-wide
<emphasis>configuration</emphasis> that affects things
like power consumption and basic functionality.
The endpoints are part of USB <emphasis>interfaces</emphasis>,
......
Documentation/DocBook/writing-an-alsa-driver.tmpl
浏览文件 @ 1b62f19c
......@@ -2742,7 +2742,9 @@ struct _snd_pcm_runtime {
<para>
Another note is that this callback is non-atomic
(schedulable). This is important, because the
(schedulable) as default, i.e. when no
<structfield>nonatomic</structfield> flag set.
This is important, because the
<structfield>trigger</structfield> callback
is atomic (non-schedulable). That is, mutexes or any
schedule-related functions are not available in
......@@ -2900,8 +2902,9 @@ struct _snd_pcm_runtime {
</para>
<para>
As mentioned, this callback is atomic. You cannot call
functions which may sleep.
As mentioned, this callback is atomic as default unless
<structfield>nonatomic</structfield> flag set, and
you cannot call functions which may sleep.
The trigger callback should be as minimal as possible,
just really triggering the DMA. The other stuff should be
initialized hw_params and prepare callbacks properly
......@@ -2936,7 +2939,7 @@ struct _snd_pcm_runtime {
</para>
<para>
This callback is also atomic.
This callback is also atomic as default.
</para>
</section>
......@@ -2972,7 +2975,7 @@ struct _snd_pcm_runtime {
is useful only for such a purpose.
</para>
<para>
This callback is atomic.
This callback is atomic as default.
</para>
</section>
......@@ -3175,6 +3178,21 @@ struct _snd_pcm_runtime {
called with local interrupts disabled.
</para>
<para>
The recent changes in PCM core code, however, allow all PCM
operations to be non-atomic. This assumes that the all caller
sides are in non-atomic contexts. For example, the function
<function>snd_pcm_period_elapsed()</function> is called
typically from the interrupt handler. But, if you set up the
driver to use a threaded interrupt handler, this call can be in
non-atomic context, too. In such a case, you can set
<structfield>nonatomic</structfield> filed of
<structname>snd_pcm</structname> object after creating it.
When this flag is set, mutex and rwsem are used internally in
the PCM core instead of spin and rwlocks, so that you can call
all PCM functions safely in a non-atomic context.
</para>
</section>
<section id="pcm-interface-constraints">
<title>Constraints</title>
......
Documentation/Makefile
浏览文件 @ 1b62f19c
obj-m := DocBook/ accounting/ auxdisplay/ connector/ \
filesystems/ filesystems/configfs/ ia64/ laptops/ networking/ \
pcmcia/ spi/ timers/ watchdog/src/ misc-devices/mei/
subdir-y := accounting arm auxdisplay blackfin connector \
filesystems filesystems ia64 laptops mic misc-devices \
networking pcmcia prctl ptp spi timers vDSO video4linux \
watchdog
Documentation/RCU/stallwarn.txt
浏览文件 @ 1b62f19c
......@@ -56,8 +56,20 @@ RCU_STALL_RAT_DELAY
two jiffies. (This is a cpp macro, not a kernel configuration
parameter.)
When a CPU detects that it is stalling, it will print a message similar
to the following:
rcupdate.rcu_task_stall_timeout
This boot/sysfs parameter controls the RCU-tasks stall warning
interval. A value of zero or less suppresses RCU-tasks stall
warnings. A positive value sets the stall-warning interval
in jiffies. An RCU-tasks stall warning starts wtih the line:
INFO: rcu_tasks detected stalls on tasks:
And continues with the output of sched_show_task() for each
task stalling the current RCU-tasks grace period.
For non-RCU-tasks flavors of RCU, when a CPU detects that it is stalling,
it will print a message similar to the following:
INFO: rcu_sched_state detected stall on CPU 5 (t=2500 jiffies)
......@@ -174,8 +186,12 @@ o A CPU looping with preemption disabled. This condition can
o A CPU looping with bottom halves disabled. This condition can
result in RCU-sched and RCU-bh stalls.
o For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the kernel
without invoking schedule().
o For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the
kernel without invoking schedule(). Note that cond_resched()
does not necessarily prevent RCU CPU stall warnings. Therefore,
if the looping in the kernel is really expected and desirable
behavior, you might need to replace some of the cond_resched()
calls with calls to cond_resched_rcu_qs().
o A CPU-bound real-time task in a CONFIG_PREEMPT kernel, which might
happen to preempt a low-priority task in the middle of an RCU
......@@ -208,11 +224,10 @@ o A hardware failure. This is quite unlikely, but has occurred
This resulted in a series of RCU CPU stall warnings, eventually
leading the realization that the CPU had failed.
The RCU, RCU-sched, and RCU-bh implementations have CPU stall warning.
SRCU does not have its own CPU stall warnings, but its calls to
synchronize_sched() will result in RCU-sched detecting RCU-sched-related
CPU stalls. Please note that RCU only detects CPU stalls when there is
a grace period in progress. No grace period, no CPU stall warnings.
The RCU, RCU-sched, RCU-bh, and RCU-tasks implementations have CPU stall
warning. Note that SRCU does -not- have CPU stall warnings. Please note
that RCU only detects CPU stalls when there is a grace period in progress.
No grace period, no CPU stall warnings.
To diagnose the cause of the stall, inspect the stack traces.
The offending function will usually be near the top of the stack.
......
Documentation/accounting/Makefile
浏览文件 @ 1b62f19c
# kbuild trick to avoid linker error. Can be omitted if a module is built.
obj- := dummy.o
# List of programs to build
hostprogs-y := getdelays
......
Documentation/acpi/enumeration.txt
浏览文件 @ 1b62f19c
......@@ -312,3 +312,30 @@ a code like this:
There are also devm_* versions of these functions which release the
descriptors once the device is released.
MFD devices
~~~~~~~~~~~
The MFD devices register their children as platform devices. For the child
devices there needs to be an ACPI handle that they can use to reference
parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
we provide two ways:
o The children share the parent ACPI handle.
o The MFD cell can specify the ACPI id of the device.
For the first case, the MFD drivers do not need to do anything. The
resulting child platform device will have its ACPI_COMPANION() set to point
to the parent device.
If the ACPI namespace has a device that we can match using an ACPI id,
the id should be set like:
static struct mfd_cell my_subdevice_cell = {
.name = "my_subdevice",
/* set the resources relative to the parent */
.acpi_pnpid = "XYZ0001",
};
The ACPI id "XYZ0001" is then used to lookup an ACPI device directly under
the MFD device and if found, that ACPI companion device is bound to the
resulting child platform device.
Documentation/applying-patches.txt
浏览文件 @ 1b62f19c
......@@ -94,7 +94,7 @@ Common errors when patching
---
When patch applies a patch file it attempts to verify the sanity of the
file in different ways.
Checking that the file looks like a valid patch file & checking the code
Checking that the file looks like a valid patch file and checking the code
around the bits being modified matches the context provided in the patch are
just two of the basic sanity checks patch does.
......
Documentation/arm/Makefile 0 → 100644
浏览文件 @ 1b62f19c
subdir-y := SH-Mobile
Documentation/arm/Marvell/README
浏览文件 @ 1b62f19c
......@@ -103,6 +103,10 @@ EBU Armada family
NOTE: not to be confused with the non-SMP 78xx0 SoCs
Product Brief: http://www.marvell.com/embedded-processors/armada-xp/assets/Marvell-ArmadaXP-SoC-product%20brief.pdf
Functional Spec: http://www.marvell.com/embedded-processors/armada-xp/assets/ARMADA-XP-Functional-SpecDatasheet.pdf
Hardware Specs:
http://www.marvell.com/embedded-processors/armada-xp/assets/HW_MV78230_OS.PDF
http://www.marvell.com/embedded-processors/armada-xp/assets/HW_MV78260_OS.PDF
http://www.marvell.com/embedded-processors/armada-xp/assets/HW_MV78460_OS.PDF
Core: Sheeva ARMv7 compatible
......
Documentation/arm/SH-Mobile/Makefile
浏览文件 @ 1b62f19c
BIN := vrl4
# List of programs to build
hostprogs-y := vrl4
.PHONY: all
all: $(BIN)
# Tell kbuild to always build the programs
always := $(hostprogs-y)
.PHONY: clean
clean:
rm -f *.o $(BIN)
HOSTCFLAGS_vrl4.o += -I$(objtree)/usr/include -I$(srctree)/tools/include
Documentation/arm/SH-Mobile/vrl4.c
浏览文件 @ 1b62f19c
......@@ -34,6 +34,7 @@
#include <stdint.h>
#include <stdio.h>
#include <errno.h>
#include <tools/endian.h>
struct hdr {
uint32_t magic1;
......@@ -77,7 +78,7 @@ struct hdr {
#define ROUND_UP(x) ((x + ALIGN - 1) & ~(ALIGN - 1))
ssize_t do_read(int fd, void *buf, size_t count)
static ssize_t do_read(int fd, void *buf, size_t count)
{
size_t offset = 0;
ssize_t l;
......@@ -98,7 +99,7 @@ ssize_t do_read(int fd, void *buf, size_t count)
return offset;
}
ssize_t do_write(int fd, const void *buf, size_t count)
static ssize_t do_write(int fd, const void *buf, size_t count)
{
size_t offset = 0;
ssize_t l;
......@@ -117,7 +118,7 @@ ssize_t do_write(int fd, const void *buf, size_t count)
return offset;
}
ssize_t write_zero(int fd, size_t len)
static ssize_t write_zero(int fd, size_t len)
{
size_t i = len;
......
Documentation/auxdisplay/Makefile
浏览文件 @ 1b62f19c
# kbuild trick to avoid linker error. Can be omitted if a module is built.
obj- := dummy.o
# List of programs to build
hostprogs-y := cfag12864b-example
......
Documentation/binfmt_misc.txt
浏览文件 @ 1b62f19c
......@@ -15,39 +15,50 @@ First you must mount binfmt_misc:
mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
To actually register a new binary type, you have to set up a string looking like
:name:type:offset:magic:mask:interpreter:flags (where you can choose the ':' upon
your needs) and echo it to /proc/sys/fs/binfmt_misc/register.
:name:type:offset:magic:mask:interpreter:flags (where you can choose the ':'
upon your needs) and echo it to /proc/sys/fs/binfmt_misc/register.
Here is what the fields mean:
- 'name' is an identifier string. A new /proc file will be created with this
name below /proc/sys/fs/binfmt_misc
name below /proc/sys/fs/binfmt_misc; cannot contain slashes '/' for obvious
reasons.
- 'type' is the type of recognition. Give 'M' for magic and 'E' for extension.
- 'offset' is the offset of the magic/mask in the file, counted in bytes. This
defaults to 0 if you omit it (i.e. you write ':name:type::magic...')
defaults to 0 if you omit it (i.e. you write ':name:type::magic...'). Ignored
when using filename extension matching.
- 'magic' is the byte sequence binfmt_misc is matching for. The magic string
may contain hex-encoded characters like \x0a or \xA4. In a shell environment
you will have to write \\x0a to prevent the shell from eating your \.
may contain hex-encoded characters like \x0a or \xA4. Note that you must
escape any NUL bytes; parsing halts at the first one. In a shell environment
you might have to write \\x0a to prevent the shell from eating your \.
If you chose filename extension matching, this is the extension to be
recognised (without the '.', the \x0a specials are not allowed). Extension
matching is case sensitive!
matching is case sensitive, and slashes '/' are not allowed!
- 'mask' is an (optional, defaults to all 0xff) mask. You can mask out some
bits from matching by supplying a string like magic and as long as magic.
The mask is anded with the byte sequence of the file.
The mask is anded with the byte sequence of the file. Note that you must
escape any NUL bytes; parsing halts at the first one. Ignored when using
filename extension matching.
- 'interpreter' is the program that should be invoked with the binary as first
argument (specify the full path)
- 'flags' is an optional field that controls several aspects of the invocation
of the interpreter. It is a string of capital letters, each controls a certain
aspect. The following flags are supported -
'P' - preserve-argv[0]. Legacy behavior of binfmt_misc is to overwrite the
original argv[0] with the full path to the binary. When this flag is
included, binfmt_misc will add an argument to the argument vector for
this purpose, thus preserving the original argv[0].
of the interpreter. It is a string of capital letters, each controls a
certain aspect. The following flags are supported -
'P' - preserve-argv[0]. Legacy behavior of binfmt_misc is to overwrite
the original argv[0] with the full path to the binary. When this
flag is included, binfmt_misc will add an argument to the argument
vector for this purpose, thus preserving the original argv[0].
e.g. If your interp is set to /bin/foo and you run `blah` (which is
in /usr/local/bin), then the kernel will execute /bin/foo with
argv[] set to ["/bin/foo", "/usr/local/bin/blah", "blah"]. The
interp has to be aware of this so it can execute /usr/local/bin/blah
with argv[] set to ["blah"].
'O' - open-binary. Legacy behavior of binfmt_misc is to pass the full path
of the binary to the interpreter as an argument. When this flag is
included, binfmt_misc will open the file for reading and pass its
descriptor as an argument, instead of the full path, thus allowing
the interpreter to execute non-readable binaries. This feature should
be used with care - the interpreter has to be trusted not to emit
the contents of the non-readable binary.
the interpreter to execute non-readable binaries. This feature
should be used with care - the interpreter has to be trusted not to
emit the contents of the non-readable binary.
'C' - credentials. Currently, the behavior of binfmt_misc is to calculate
the credentials and security token of the new process according to
the interpreter. When this flag is included, these attributes are
......@@ -58,7 +69,7 @@ Here is what the fields mean:
There are some restrictions:
- the whole register string may not exceed 255 characters
- the whole register string may not exceed 1920 characters
- the magic must reside in the first 128 bytes of the file, i.e.
offset+size(magic) has to be less than 128
- the interpreter string may not exceed 127 characters
......@@ -110,7 +121,4 @@ passes it the full filename (or the file descriptor) to use. Using $PATH can
cause unexpected behaviour and can be a security hazard.
There is a web page about binfmt_misc at
http://www.tat.physik.uni-tuebingen.de
Richard Günther <rguenth@tat.physik.uni-tuebingen.de>
Documentation/blackfin/Makefile
浏览文件 @ 1b62f19c
ifneq ($(CONFIG_BLACKFIN),)
obj-m := gptimers-example.o
all: modules
modules clean:
$(MAKE) -C ../.. SUBDIRS=$(PWD) $@
endif
Documentation/block/data-integrity.txt
浏览文件 @ 1b62f19c
......@@ -129,11 +129,11 @@ interface for this is being worked on.
4.1 BIO
The data integrity patches add a new field to struct bio when
CONFIG_BLK_DEV_INTEGRITY is enabled. bio->bi_integrity is a pointer
to a struct bip which contains the bio integrity payload. Essentially
a bip is a trimmed down struct bio which holds a bio_vec containing
the integrity metadata and the required housekeeping information (bvec
pool, vector count, etc.)
CONFIG_BLK_DEV_INTEGRITY is enabled. bio_integrity(bio) returns a
pointer to a struct bip which contains the bio integrity payload.
Essentially a bip is a trimmed down struct bio which holds a bio_vec
containing the integrity metadata and the required housekeeping
information (bvec pool, vector count, etc.)
A kernel subsystem can enable data integrity protection on a bio by
calling bio_integrity_alloc(bio). This will allocate and attach the
......@@ -192,16 +192,6 @@ will require extra work due to the application tag.
supported by the block device.
int bdev_integrity_enabled(block_device, int rw);
bdev_integrity_enabled() will return 1 if the block device
supports integrity metadata transfer for the data direction
specified in 'rw'.
bdev_integrity_enabled() honors the write_generate and
read_verify flags in sysfs and will respond accordingly.
int bio_integrity_prep(bio);
To generate IMD for WRITE and to set up buffers for READ, the
......@@ -216,36 +206,6 @@ will require extra work due to the application tag.
bio_integrity_enabled() returned 1.
int bio_integrity_tag_size(bio);
If the filesystem wants to use the application tag space it will
first have to find out how much storage space is available.
Because tag space is generally limited (usually 2 bytes per
sector regardless of sector size), the integrity framework
supports interleaving the information between the sectors in an
I/O.
Filesystems can call bio_integrity_tag_size(bio) to find out how
many bytes of storage are available for that particular bio.
Another option is bdev_get_tag_size(block_device) which will
return the number of available bytes per hardware sector.
int bio_integrity_set_tag(bio, void *tag_buf, len);
After a successful return from bio_integrity_prep(),
bio_integrity_set_tag() can be used to attach an opaque tag
buffer to a bio. Obviously this only makes sense if the I/O is
a WRITE.
int bio_integrity_get_tag(bio, void *tag_buf, len);
Similarly, at READ I/O completion time the filesystem can
retrieve the tag buffer using bio_integrity_get_tag().
5.3 PASSING EXISTING INTEGRITY METADATA
Filesystems that either generate their own integrity metadata or
......@@ -298,8 +258,6 @@ will require extra work due to the application tag.
.name = "STANDARDSBODY-TYPE-VARIANT-CSUM",
.generate_fn = my_generate_fn,
.verify_fn = my_verify_fn,
.get_tag_fn = my_get_tag_fn,
.set_tag_fn = my_set_tag_fn,
.tuple_size = sizeof(struct my_tuple_size),
.tag_size = <tag bytes per hw sector>,
};
......@@ -321,7 +279,5 @@ will require extra work due to the application tag.
are available per hardware sector. For DIF this is either 2 or
0 depending on the value of the Control Mode Page ATO bit.
See 6.2 for a description of get_tag_fn and set_tag_fn.
----------------------------------------------------------------------
2007-12-24 Martin K. Petersen <martin.petersen@oracle.com>
Documentation/block/null_blk.txt
浏览文件 @ 1b62f19c
......@@ -42,7 +42,7 @@ nr_devices=[Number of devices]: Default: 2
Number of block devices instantiated. They are instantiated as /dev/nullb0,
etc.
irq_mode=[0-2]: Default: 1-Soft-irq
irqmode=[0-2]: Default: 1-Soft-irq
The completion mode used for completing IOs to the block-layer.
0: None.
......@@ -53,7 +53,7 @@ irq_mode=[0-2]: Default: 1-Soft-irq
completion.
completion_nsec=[ns]: Default: 10.000ns
Combined with irq_mode=2 (timer). The time each completion event must wait.
Combined with irqmode=2 (timer). The time each completion event must wait.
submit_queues=[0..nr_cpus]:
The number of submission queues attached to the device driver. If unset, it
......
Documentation/block/queue-sysfs.txt
浏览文件 @ 1b62f19c
......@@ -11,7 +11,7 @@ read-write.
add_random (RW)
----------------
This file allows to trun off the disk entropy contribution. Default
This file allows to turn off the disk entropy contribution. Default
value of this file is '1'(on).
discard_granularity (RO)
......@@ -72,7 +72,7 @@ Maximum segment size of the device.
minimum_io_size (RO)
--------------------
This is the smallest preferred io size reported by the device.
This is the smallest preferred IO size reported by the device.
nomerges (RW)
-------------
......@@ -98,7 +98,7 @@ regulated by nr_requests.
optimal_io_size (RO)
--------------------
This is the optimal io size reported by the device.
This is the optimal IO size reported by the device.
physical_block_size (RO)
------------------------
......
Documentation/blockdev/zram.txt
浏览文件 @ 1b62f19c
......@@ -74,14 +74,30 @@ There is little point creating a zram of greater than twice the size of memory
since we expect a 2:1 compression ratio. Note that zram uses about 0.1% of the
size of the disk when not in use so a huge zram is wasteful.
5) Activate:
5) Set memory limit: Optional
Set memory limit by writing the value to sysfs node 'mem_limit'.
The value can be either in bytes or you can use mem suffixes.
In addition, you could change the value in runtime.
Examples:
# limit /dev/zram0 with 50MB memory
echo $((50*1024*1024)) > /sys/block/zram0/mem_limit
# Using mem suffixes
echo 256K > /sys/block/zram0/mem_limit
echo 512M > /sys/block/zram0/mem_limit
echo 1G > /sys/block/zram0/mem_limit
# To disable memory limit
echo 0 > /sys/block/zram0/mem_limit
6) Activate:
mkswap /dev/zram0
swapon /dev/zram0
mkfs.ext4 /dev/zram1
mount /dev/zram1 /tmp
6) Stats:
7) Stats:
Per-device statistics are exported as various nodes under
/sys/block/zram<id>/
disksize
......@@ -95,12 +111,13 @@ size of the disk when not in use so a huge zram is wasteful.
orig_data_size
compr_data_size
mem_used_total
mem_used_max
7) Deactivate:
8) Deactivate:
swapoff /dev/zram0
umount /dev/zram1
8) Reset:
9) Reset:
Write any positive value to 'reset' sysfs node
echo 1 > /sys/block/zram0/reset
echo 1 > /sys/block/zram1/reset
......
Documentation/devicetree/bindings/arm/altera/socfpga-sdram-edac.txt 0 → 100644
浏览文件 @ 1b62f19c
Altera SOCFPGA SDRAM Error Detection & Correction [EDAC]
The EDAC accesses a range of registers in the SDRAM controller.
Required properties:
- compatible : should contain "altr,sdram-edac";
- altr,sdr-syscon : phandle of the sdr module
- interrupts : Should contain the SDRAM ECC IRQ in the
appropriate format for the IRQ controller.
Example:
sdramedac {
compatible = "altr,sdram-edac";
altr,sdr-syscon = <&sdr>;
interrupts = <0 39 4>;
};
Documentation/devicetree/bindings/arm/amlogic.txt 0 → 100644
浏览文件 @ 1b62f19c
Amlogic MesonX device tree bindings
-------------------------------------------
Boards with the Amlogic Meson6 SoC shall have the following properties:
Required root node property:
compatible = "amlogic,meson6";
Documentation/devicetree/bindings/arm/atmel-at91.txt
浏览文件 @ 1b62f19c
Atmel AT91 device tree bindings.
================================
Boards with a SoC of the Atmel AT91 or SMART family shall have the following
properties:
Required root node properties:
compatible: must be one of:
* "atmel,at91rm9200"
* "atmel,at91sam9" for SoCs using an ARM926EJ-S core, shall be extended with
the specific SoC family or compatible:
o "atmel,at91sam9260"
o "atmel,at91sam9261"
o "atmel,at91sam9263"
o "atmel,at91sam9x5" for the 5 series, shall be extended with the specific
SoC compatible:
- "atmel,at91sam9g15"
- "atmel,at91sam9g25"
- "atmel,at91sam9g35"
- "atmel,at91sam9x25"
- "atmel,at91sam9x35"
o "atmel,at91sam9g20"
o "atmel,at91sam9g45"
o "atmel,at91sam9n12"
o "atmel,at91sam9rl"
* "atmel,sama5" for SoCs using a Cortex-A5, shall be extended with the specific
SoC family:
o "atmel,sama5d3" shall be extended with the specific SoC compatible:
- "atmel,sama5d31"
- "atmel,sama5d33"
- "atmel,sama5d34"
- "atmel,sama5d35"
- "atmel,sama5d36"
o "atmel,sama5d4" shall be extended with the specific SoC compatible:
- "atmel,sama5d41"
- "atmel,sama5d42"
- "atmel,sama5d43"
- "atmel,sama5d44"
PIT Timer required properties:
- compatible: Should be "atmel,at91sam9260-pit"
- reg: Should contain registers location and length
......@@ -61,8 +98,8 @@ RAMC SDRAM/DDR Controller required properties:
- compatible: Should be "atmel,at91rm9200-sdramc",
"atmel,at91sam9260-sdramc",
"atmel,at91sam9g45-ddramc",
"atmel,sama5d3-ddramc",
- reg: Should contain registers location and length
For at91sam9263 and at91sam9g45 you must specify 2 entries.
Examples:
......@@ -71,12 +108,6 @@ Examples:
reg = <0xffffe800 0x200>;
};
ramc0: ramc@ffffe400 {
compatible = "atmel,at91sam9g45-ddramc";
reg = <0xffffe400 0x200
0xffffe600 0x200>;
};
SHDWC Shutdown Controller
required properties:
......
Documentation/devicetree/bindings/arm/bcm/bcm63138.txt 0 → 100644
浏览文件 @ 1b62f19c
Broadcom BCM63138 DSL System-on-a-Chip device tree bindings
-----------------------------------------------------------
Boards compatible with the BCM63138 DSL System-on-a-Chip should have the
following properties:
Required root node property:
compatible: should be "brcm,bcm63138"
Documentation/devicetree/bindings/arm/cavium-thunder.txt 0 → 100644
浏览文件 @ 1b62f19c
Cavium Thunder platform device tree bindings
--------------------------------------------
Boards with Cavium's Thunder SoC shall have following properties.
Root Node
---------
Required root node properties:
- compatible = "cavium,thunder-88xx";
Documentation/devicetree/bindings/arm/cpus.txt
浏览文件 @ 1b62f19c
......@@ -166,6 +166,7 @@ nodes to be present and contain the properties described below.
"arm,cortex-r5"
"arm,cortex-r7"
"brcm,brahma-b15"
"cavium,thunder"
"faraday,fa526"
"intel,sa110"
"intel,sa1100"
......@@ -219,6 +220,12 @@ nodes to be present and contain the properties described below.
Value type: <phandle>
Definition: Specifies the ACC[2] node associated with this CPU.
- cpu-idle-states
Usage: Optional
Value type: <prop-encoded-array>
Definition:
# List of phandles to idle state nodes supported
by this cpu [3].
Example 1 (dual-cluster big.LITTLE system 32-bit):
......@@ -415,3 +422,5 @@ cpus {
--
[1] arm/msm/qcom,saw2.txt
[2] arm/msm/qcom,kpss-acc.txt
[3] ARM Linux kernel documentation - idle states bindings
Documentation/devicetree/bindings/arm/idle-states.txt
Documentation/devicetree/bindings/arm/exynos/power_domain.txt
浏览文件 @ 1b62f19c
......@@ -8,6 +8,8 @@ Required Properties:
* samsung,exynos4210-pd - for exynos4210 type power domain.
- reg: physical base address of the controller and length of memory mapped
region.
- #power-domain-cells: number of cells in power domain specifier;
must be 0.
Optional Properties:
- clocks: List of clock handles. The parent clocks of the input clocks to the
......@@ -29,6 +31,7 @@ Example:
lcd0: power-domain-lcd0 {
compatible = "samsung,exynos4210-pd";
reg = <0x10023C00 0x10>;
#power-domain-cells = <0>;
};
mfc_pd: power-domain@10044060 {
......@@ -37,12 +40,8 @@ Example:
clocks = <&clock CLK_FIN_PLL>, <&clock CLK_MOUT_SW_ACLK333>,
<&clock CLK_MOUT_USER_ACLK333>;
clock-names = "oscclk", "pclk0", "clk0";
#power-domain-cells = <0>;
};
Example of the node using power domain:
node {
/* ... */
samsung,power-domain = <&lcd0>;
/* ... */
};
See Documentation/devicetree/bindings/power/power_domain.txt for description
of consumer-side bindings.
Documentation/devicetree/bindings/arm/geniatech.txt 0 → 100644
浏览文件 @ 1b62f19c
Geniatech platforms device tree bindings
-------------------------------------------
Geniatech ATV1200
- compatible = "geniatech,atv1200"
Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt
浏览文件 @ 1b62f19c
......@@ -5,6 +5,11 @@ Hi4511 Board
Required root node properties:
- compatible = "hisilicon,hi3620-hi4511";
HiP04 D01 Board
Required root node properties:
- compatible = "hisilicon,hip04-d01";
Hisilicon system controller
Required properties:
......@@ -55,3 +60,21 @@ Example:
compatible = "hisilicon,pctrl";
reg = <0xfca09000 0x1000>;
};
-----------------------------------------------------------------------
Fabric:
Required Properties:
- compatible: "hisilicon,hip04-fabric";
- reg: Address and size of Fabric
-----------------------------------------------------------------------
Bootwrapper boot method (software protocol on SMP):
Required Properties:
- compatible: "hisilicon,hip04-bootwrapper";
- boot-method: Address and size of boot method.
[0]: bootwrapper physical address
[1]: bootwrapper size
[2]: relocation physical address
[3]: relocation size
Documentation/devicetree/bindings/arm/idle-states.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/arm/l2cc.txt
浏览文件 @ 1b62f19c
......@@ -2,6 +2,10 @@
ARM cores often have a separate level 2 cache controller. There are various
implementations of the L2 cache controller with compatible programming models.
Some of the properties that are just prefixed "cache-*" are taken from section
3.7.3 of the ePAPR v1.1 specification which can be found at:
https://www.power.org/wp-content/uploads/2012/06/Power_ePAPR_APPROVED_v1.1.pdf
The ARM L2 cache representation in the device tree should be done as follows:
Required properties:
......@@ -44,6 +48,12 @@ Optional properties:
I/O coherent mode. Valid only when the arm,pl310-cache compatible
string is used.
- interrupts : 1 combined interrupt.
- cache-size : specifies the size in bytes of the cache
- cache-sets : specifies the number of associativity sets of the cache
- cache-block-size : specifies the size in bytes of a cache block
- cache-line-size : specifies the size in bytes of a line in the cache,
if this is not specified, the line size is assumed to be equal to the
cache block size
- cache-id-part: cache id part number to be used if it is not present
on hardware
- wt-override: If present then L2 is forced to Write through mode
......
Documentation/devicetree/bindings/arm/mediatek.txt
浏览文件 @ 1b62f19c
......@@ -6,3 +6,9 @@ Required root node property:
compatible: must contain "mediatek,mt6589"
Supported boards:
- bq Aquaris5 smart phone:
Required root node properties:
- compatible = "mundoreader,bq-aquaris5", "mediatek,mt6589";
Documentation/devicetree/bindings/arm/omap/mpu.txt
浏览文件 @ 1b62f19c
......@@ -10,6 +10,9 @@ Required properties:
Should be "ti,omap5-mpu" for OMAP5
- ti,hwmods: "mpu"
Optional properties:
- sram: Phandle to the ocmcram node
Examples:
- For an OMAP5 SMP system:
......
Documentation/devicetree/bindings/arm/omap/omap.txt
浏览文件 @ 1b62f19c
......@@ -85,6 +85,18 @@ SoCs:
- DRA722
compatible = "ti,dra722", "ti,dra72", "ti,dra7"
- AM5728
compatible = "ti,am5728", "ti,dra742", "ti,dra74", "ti,dra7"
- AM5726
compatible = "ti,am5726", "ti,dra742", "ti,dra74", "ti,dra7"
- AM5718
compatible = "ti,am5718", "ti,dra722", "ti,dra72", "ti,dra7"
- AM5716
compatible = "ti,am5716", "ti,dra722", "ti,dra72", "ti,dra7"
- AM4372
compatible = "ti,am4372", "ti,am43"
......
Documentation/devicetree/bindings/arm/psci.txt
浏览文件 @ 1b62f19c
......@@ -50,6 +50,16 @@ Main node optional properties:
- migrate : Function ID for MIGRATE operation
Device tree nodes that require usage of PSCI CPU_SUSPEND function (ie idle
state nodes, as per bindings in [1]) must specify the following properties:
- arm,psci-suspend-param
Usage: Required for state nodes[1] if the corresponding
idle-states node entry-method property is set
to "psci".
Value type: <u32>
Definition: power_state parameter to pass to the PSCI
suspend call.
Example:
......@@ -64,7 +74,6 @@ Case 1: PSCI v0.1 only.
migrate = <0x95c10003>;
};
Case 2: PSCI v0.2 only
psci {
......@@ -88,3 +97,6 @@ Case 3: PSCI v0.2 and PSCI v0.1.
...
};
[1] Kernel documentation - ARM idle states bindings
Documentation/devicetree/bindings/arm/idle-states.txt
Documentation/devicetree/bindings/arm/samsung/exynos-adc.txt
浏览文件 @ 1b62f19c
......@@ -11,13 +11,25 @@ New driver handles the following
Required properties:
- compatible: Must be "samsung,exynos-adc-v1"
for exynos4412/5250 controllers.
for exynos4412/5250 and s5pv210 controllers.
Must be "samsung,exynos-adc-v2" for
future controllers.
Must be "samsung,exynos3250-adc" for
controllers compatible with ADC of Exynos3250.
- reg: Contains ADC register address range (base address and
length) and the address of the phy enable register.
Must be "samsung,s3c2410-adc" for
the ADC in s3c2410 and compatibles
Must be "samsung,s3c2416-adc" for
the ADC in s3c2416 and compatibles
Must be "samsung,s3c2440-adc" for
the ADC in s3c2440 and compatibles
Must be "samsung,s3c2443-adc" for
the ADC in s3c2443 and compatibles
Must be "samsung,s3c6410-adc" for
the ADC in s3c6410 and compatibles
- reg: List of ADC register address range
- The base address and range of ADC register
- The base address and range of ADC_PHY register (every
SoC except for s3c24xx/s3c64xx ADC)
- interrupts: Contains the interrupt information for the timer. The
format is being dependent on which interrupt controller
the Samsung device uses.
......
Documentation/devicetree/bindings/arm/shmobile.txt 0 → 100644
浏览文件 @ 1b62f19c
Renesas SH-Mobile, R-Mobile, and R-Car Platform Device Tree Bindings
--------------------------------------------------------------------
SoCs:
- Emma Mobile EV2
compatible = "renesas,emev2"
- RZ/A1H (R7S72100)
compatible = "renesas,r7s72100"
- SH-Mobile AP4 (R8A73720/SH7372)
compatible = "renesas,sh7372"
- SH-Mobile AG5 (R8A73A00/SH73A0)
compatible = "renesas,sh73a0"
- R-Mobile APE6 (R8A73A40)
compatible = "renesas,r8a73a4"
- R-Mobile A1 (R8A77400)
compatible = "renesas,r8a7740"
- R-Car M1A (R8A77781)
compatible = "renesas,r8a7778"
- R-Car H1 (R8A77790)
compatible = "renesas,r8a7779"
- R-Car H2 (R8A77900)
compatible = "renesas,r8a7790"
- R-Car M2-W (R8A77910)
compatible = "renesas,r8a7791"
- R-Car V2H (R8A77920)
compatible = "renesas,r8a7792"
- R-Car M2-N (R8A77930)
compatible = "renesas,r8a7793"
- R-Car E2 (R8A77940)
compatible = "renesas,r8a7794"
Boards:
- Alt
compatible = "renesas,alt", "renesas,r8a7794"
- APE6-EVM
compatible = "renesas,ape6evm", "renesas,r8a73a4"
- APE6-EVM - Reference Device Tree Implementation
compatible = "renesas,ape6evm-reference", "renesas,r8a73a4"
- Atmark Techno Armadillo-800 EVA
compatible = "renesas,armadillo800eva"
- BOCK-W
compatible = "renesas,bockw", "renesas,r8a7778"
- BOCK-W - Reference Device Tree Implementation
compatible = "renesas,bockw-reference", "renesas,r8a7778"
- Genmai (RTK772100BC00000BR)
compatible = "renesas,genmai", "renesas,r7s72100"
- Gose
compatible = "renesas,gose", "renesas,r8a7793"
- Henninger
compatible = "renesas,henninger", "renesas,r8a7791"
- Koelsch (RTP0RC7791SEB00010S)
compatible = "renesas,koelsch", "renesas,r8a7791"
- Kyoto Microcomputer Co. KZM-A9-Dual
compatible = "renesas,kzm9d", "renesas,emev2"
- Kyoto Microcomputer Co. KZM-A9-GT
compatible = "renesas,kzm9g", "renesas,sh73a0"
- Kyoto Microcomputer Co. KZM-A9-GT - Reference Device Tree Implementation
compatible = "renesas,kzm9g-reference", "renesas,sh73a0"
- Lager (RTP0RC7790SEB00010S)
compatible = "renesas,lager", "renesas,r8a7790"
- Mackerel (R0P7372LC0016RL, AP4 EVM 2nd)
compatible = "renesas,mackerel"
- Marzen
compatible = "renesas,marzen", "renesas,r8a7779"
Note: Reference Device Tree Implementations are temporary implementations
to ease the migration from platform devices to Device Tree, and are
intended to be removed in the future.
Documentation/devicetree/bindings/arm/tegra/nvidia,tegra20-flowctrl.txt 0 → 100644
浏览文件 @ 1b62f19c
NVIDIA Tegra Flow Controller
Required properties:
- compatible: Should be "nvidia,tegra<chip>-flowctrl"
- reg: Should contain one register range (address and length)
Example:
flow-controller@60007000 {
compatible = "nvidia,tegra20-flowctrl";
reg = <0x60007000 0x1000>;
};
Documentation/devicetree/bindings/ata/qcom-sata.txt 0 → 100644
浏览文件 @ 1b62f19c
* Qualcomm AHCI SATA Controller
SATA nodes are defined to describe on-chip Serial ATA controllers.
Each SATA controller should have its own node.
Required properties:
- compatible : compatible list, must contain "generic-ahci"
- interrupts : <interrupt mapping for SATA IRQ>
- reg : <registers mapping>
- phys : Must contain exactly one entry as specified
in phy-bindings.txt
- phy-names : Must be "sata-phy"
Required properties for "qcom,ipq806x-ahci" compatible:
- clocks : Must contain an entry for each entry in clock-names.
- clock-names : Shall be:
"slave_iface" - Fabric port AHB clock for SATA
"iface" - AHB clock
"core" - core clock
"rxoob" - RX out-of-band clock
"pmalive" - Power Module Alive clock
- assigned-clocks : Shall be:
SATA_RXOOB_CLK
SATA_PMALIVE_CLK
- assigned-clock-rates : Shall be:
100Mhz (100000000) for SATA_RXOOB_CLK
100Mhz (100000000) for SATA_PMALIVE_CLK
Example:
sata@29000000 {
compatible = "qcom,ipq806x-ahci", "generic-ahci";
reg = <0x29000000 0x180>;
interrupts = <0 209 0x0>;
clocks = <&gcc SFAB_SATA_S_H_CLK>,
<&gcc SATA_H_CLK>,
<&gcc SATA_A_CLK>,
<&gcc SATA_RXOOB_CLK>,
<&gcc SATA_PMALIVE_CLK>;
clock-names = "slave_iface", "iface", "core",
"rxoob", "pmalive";
assigned-clocks = <&gcc SATA_RXOOB_CLK>, <&gcc SATA_PMALIVE_CLK>;
assigned-clock-rates = <100000000>, <100000000>;
phys = <&sata_phy>;
phy-names = "sata-phy";
};
Documentation/devicetree/bindings/bus/bcma.txt 0 → 100644
浏览文件 @ 1b62f19c
Driver for ARM AXI Bus with Broadcom Plugins (bcma)
Required properties:
- compatible : brcm,bus-axi
- reg : iomem address range of chipcommon core
The cores on the AXI bus are automatically detected by bcma with the
memory ranges they are using and they get registered afterwards.
The top-level axi bus may contain children representing attached cores
(devices). This is needed since some hardware details can't be auto
detected (e.g. IRQ numbers). Also some of the cores may be responsible
for extra things, e.g. ChipCommon providing access to the GPIO chip.
Example:
axi@18000000 {
compatible = "brcm,bus-axi";
reg = <0x18000000 0x1000>;
ranges = <0x00000000 0x18000000 0x00100000>;
#address-cells = <1>;
#size-cells = <1>;
chipcommon {
reg = <0x00000000 0x1000>;
gpio-controller;
#gpio-cells = <2>;
};
};
Documentation/devicetree/bindings/clock/arm-integrator.txt
浏览文件 @ 1b62f19c
Clock bindings for ARM Integrator and Versatile Core Module clocks
Auxilary Oscillator Clock
Auxiliary Oscillator Clock
This is a configurable clock fed from a 24 MHz chrystal,
used for generating e.g. video clocks. It is located on the
......
Documentation/devicetree/bindings/clock/at91-clock.txt
浏览文件 @ 1b62f19c
......@@ -74,6 +74,9 @@ Required properties:
"atmel,at91sam9x5-clk-utmi":
at91 utmi clock
"atmel,sama5d4-clk-h32mx":
at91 h32mx clock
Required properties for SCKC node:
- reg : defines the IO memory reserved for the SCKC.
- #size-cells : shall be 0 (reg is used to encode clk id).
......@@ -447,3 +450,14 @@ For example:
#clock-cells = <0>;
clocks = <&main>;
};
Required properties for 32 bits bus Matrix clock (h32mx clock):
- #clock-cells : from common clock binding; shall be set to 0.
- clocks : shall be the master clock source phandle.
For example:
h32ck: h32mxck {
#clock-cells = <0>;
compatible = "atmel,sama5d4-clk-h32mx";
clocks = <&mck>;
};
Documentation/devicetree/bindings/clock/exynos3250-clock.txt
浏览文件 @ 1b62f19c
......@@ -7,6 +7,8 @@ Required Properties:
- compatible: should be one of the following.
- "samsung,exynos3250-cmu" - controller compatible with Exynos3250 SoC.
- "samsung,exynos3250-cmu-dmc" - controller compatible with
Exynos3250 SoC for Dynamic Memory Controller domain.
- reg: physical base address of the controller and length of memory mapped
region.
......@@ -20,7 +22,7 @@ All available clocks are defined as preprocessor macros in
dt-bindings/clock/exynos3250.h header and can be used in device
tree sources.
Example 1: An example of a clock controller node is listed below.
Example 1: Examples of clock controller nodes are listed below.
cmu: clock-controller@10030000 {
compatible = "samsung,exynos3250-cmu";
......@@ -28,6 +30,12 @@ Example 1: An example of a clock controller node is listed below.
#clock-cells = <1>;
};
cmu_dmc: clock-controller@105C0000 {
compatible = "samsung,exynos3250-cmu-dmc";
reg = <0x105C0000 0x2000>;
#clock-cells = <1>;
};
Example 2: UART controller node that consumes the clock generated by the clock
controller. Refer to the standard clock bindings for information
about 'clocks' and 'clock-names' property.
......
Documentation/devicetree/bindings/clock/gpio-gate-clock.txt 0 → 100644
浏览文件 @ 1b62f19c
Binding for simple gpio gated clock.
This binding uses the common clock binding[1].
[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
Required properties:
- compatible : shall be "gpio-gate-clock".
- #clock-cells : from common clock binding; shall be set to 0.
- enable-gpios : GPIO reference for enabling and disabling the clock.
Optional properties:
- clocks: Maximum of one parent clock is supported.
Example:
clock {
compatible = "gpio-gate-clock";
clocks = <&parentclk>;
#clock-cells = <0>;
enable-gpios = <&gpio 1 GPIO_ACTIVE_HIGH>;
};
Documentation/devicetree/bindings/clock/maxim,max77686.txt
浏览文件 @ 1b62f19c
......@@ -9,13 +9,21 @@ The MAX77686 contains three 32.768khz clock outputs that can be controlled
Following properties should be presend in main device node of the MFD chip.
Required properties:
- #clock-cells: simple one-cell clock specifier format is used, where the
only cell is used as an index of the clock inside the provider. Following
indices are allowed:
- #clock-cells: from common clock binding; shall be set to 1.
Optional properties:
- clock-output-names: From common clock binding.
Each clock is assigned an identifier and client nodes can use this identifier
to specify the clock which they consume. Following indices are allowed:
- 0: 32khz_ap clock,
- 1: 32khz_cp clock,
- 2: 32khz_pmic clock.
Clocks are defined as preprocessor macros in dt-bindings/clock/maxim,max77686.h
header and can be used in device tree sources.
Example: Node of the MFD chip
max77686: max77686@09 {
......@@ -34,5 +42,5 @@ Example: Clock consumer node
compatible = "bar,foo";
/* ... */
clock-names = "my-clock";
clocks = <&max77686 2>;
clocks = <&max77686 MAX77686_CLK_PMIC>;
};
Documentation/devicetree/bindings/clock/maxim,max77802.txt 0 → 100644
浏览文件 @ 1b62f19c
Binding for Maxim MAX77802 32k clock generator block
This is a part of device tree bindings of MAX77802 multi-function device.
More information can be found in bindings/mfd/max77802.txt file.
The MAX77802 contains two 32.768khz clock outputs that can be controlled
(gated/ungated) over I2C.
Following properties should be present in main device node of the MFD chip.
Required properties:
- #clock-cells: From common clock binding; shall be set to 1.
Optional properties:
- clock-output-names: From common clock binding.
Each clock is assigned an identifier and client nodes can use this identifier
to specify the clock which they consume. Following indices are allowed:
- 0: 32khz_ap clock,
- 1: 32khz_cp clock.
Clocks are defined as preprocessor macros in dt-bindings/clock/maxim,max77802.h
header and can be used in device tree sources.
Example: Node of the MFD chip
max77802: max77802@09 {
compatible = "maxim,max77802";
interrupt-parent = <&wakeup_eint>;
interrupts = <26 0>;
reg = <0x09>;
#clock-cells = <1>;
/* ... */
};
Example: Clock consumer node
foo@0 {
compatible = "bar,foo";
/* ... */
clock-names = "my-clock";
clocks = <&max77802 MAX77802_CLK_32K_AP>;
};
Documentation/devicetree/bindings/clock/pxa-clock.txt 0 → 100644
浏览文件 @ 1b62f19c
* Clock bindings for Marvell PXA chips
Required properties:
- compatible: Should be "marvell,pxa-clocks"
- #clock-cells: Should be <1>
The clock consumer should specify the desired clock by having the clock
ID in its "clocks" phandle cell (see include/.../pxa-clock.h).
Examples:
pxa2xx_clks: pxa2xx_clks@41300004 {
compatible = "marvell,pxa-clocks";
#clock-cells = <1>;
status = "okay";
};
Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
浏览文件 @ 1b62f19c
......@@ -11,9 +11,12 @@ Required Properties:
- compatible: Must be one of the following
- "renesas,r7s72100-mstp-clocks" for R7S72100 (RZ) MSTP gate clocks
- "renesas,r8a7740-mstp-clocks" for R8A7740 (R-Mobile A1) MSTP gate clocks
- "renesas,r8a7779-mstp-clocks" for R8A7779 (R-Car H1) MSTP gate clocks
- "renesas,r8a7790-mstp-clocks" for R8A7790 (R-Car H2) MSTP gate clocks
- "renesas,r8a7791-mstp-clocks" for R8A7791 (R-Car M2) MSTP gate clocks
- "renesas,r8a7794-mstp-clocks" for R8A7794 (R-Car E2) MSTP gate clocks
- "renesas,sh73a0-mstp-clocks" for SH73A0 (SH-MobileAG5) MSTP gate clocks
- "renesas,cpg-mstp-clock" for generic MSTP gate clocks
- reg: Base address and length of the I/O mapped registers used by the MSTP
clocks. The first register is the clock control register and is mandatory.
......
Documentation/devicetree/bindings/clock/renesas,rcar-gen2-cpg-clocks.txt
浏览文件 @ 1b62f19c
......@@ -8,6 +8,7 @@ Required Properties:
- compatible: Must be one of
- "renesas,r8a7790-cpg-clocks" for the r8a7790 CPG
- "renesas,r8a7791-cpg-clocks" for the r8a7791 CPG
- "renesas,r8a7794-cpg-clocks" for the r8a7794 CPG
- "renesas,rcar-gen2-cpg-clocks" for the generic R-Car Gen2 CPG
- reg: Base address and length of the memory resource used by the CPG
......
Documentation/devicetree/bindings/clock/sunxi.txt
浏览文件 @ 1b62f19c
......@@ -46,7 +46,11 @@ Required properties:
"allwinner,sun6i-a31-apb2-div-clk" - for the APB2 gates on A31
"allwinner,sun6i-a31-apb2-gates-clk" - for the APB2 gates on A31
"allwinner,sun8i-a23-apb2-gates-clk" - for the APB2 gates on A23
"allwinner,sun5i-a13-mbus-clk" - for the MBUS clock on A13
"allwinner,sun4i-a10-mmc-output-clk" - for the MMC output clock on A10
"allwinner,sun4i-a10-mmc-sample-clk" - for the MMC sample clock on A10
"allwinner,sun4i-a10-mod0-clk" - for the module 0 family of clocks
"allwinner,sun8i-a23-mbus-clk" - for the MBUS clock on A23
"allwinner,sun7i-a20-out-clk" - for the external output clocks
"allwinner,sun7i-a20-gmac-clk" - for the GMAC clock module on A20/A31
"allwinner,sun4i-a10-usb-clk" - for usb gates + resets on A10 / A20
......
Documentation/devicetree/bindings/cpufreq/cpufreq-cpu0.txt 已删除 100644 → 0
浏览文件 @ a66d05d5
Generic CPU0 cpufreq driver
It is a generic cpufreq driver for CPU0 frequency management. It
supports both uniprocessor (UP) and symmetric multiprocessor (SMP)
systems which share clock and voltage across all CPUs.
Both required and optional properties listed below must be defined
under node /cpus/cpu@0.
Required properties:
- None
Optional properties:
- operating-points: Refer to Documentation/devicetree/bindings/power/opp.txt for
details. OPPs *must* be supplied either via DT, i.e. this property, or
populated at runtime.
- clock-latency: Specify the possible maximum transition latency for clock,
in unit of nanoseconds.
- voltage-tolerance: Specify the CPU voltage tolerance in percentage.
- #cooling-cells:
- cooling-min-level:
- cooling-max-level:
Please refer to Documentation/devicetree/bindings/thermal/thermal.txt.
Examples:
cpus {
#address-cells = <1>;
#size-cells = <0>;
cpu@0 {
compatible = "arm,cortex-a9";
reg = <0>;
next-level-cache = <&L2>;
operating-points = <
/* kHz uV */
792000 1100000
396000 950000
198000 850000
>;
clock-latency = <61036>; /* two CLK32 periods */
#cooling-cells = <2>;
cooling-min-level = <0>;
cooling-max-level = <2>;
};
cpu@1 {
compatible = "arm,cortex-a9";
reg = <1>;
next-level-cache = <&L2>;
};
cpu@2 {
compatible = "arm,cortex-a9";
reg = <2>;
next-level-cache = <&L2>;
};
cpu@3 {
compatible = "arm,cortex-a9";
reg = <3>;
next-level-cache = <&L2>;
};
};
Documentation/devicetree/bindings/cpufreq/cpufreq-dt.txt 0 → 100644
浏览文件 @ 1b62f19c
Generic cpufreq driver
It is a generic DT based cpufreq driver for frequency management. It supports
both uniprocessor (UP) and symmetric multiprocessor (SMP) systems which share
clock and voltage across all CPUs.
Both required and optional properties listed below must be defined
under node /cpus/cpu@0.
Required properties:
- None
Optional properties:
- operating-points: Refer to Documentation/devicetree/bindings/power/opp.txt for
details. OPPs *must* be supplied either via DT, i.e. this property, or
populated at runtime.
- clock-latency: Specify the possible maximum transition latency for clock,
in unit of nanoseconds.
- voltage-tolerance: Specify the CPU voltage tolerance in percentage.
- #cooling-cells:
- cooling-min-level:
- cooling-max-level:
Please refer to Documentation/devicetree/bindings/thermal/thermal.txt.
Examples:
cpus {
#address-cells = <1>;
#size-cells = <0>;
cpu@0 {
compatible = "arm,cortex-a9";
reg = <0>;
next-level-cache = <&L2>;
operating-points = <
/* kHz uV */
792000 1100000
396000 950000
198000 850000
>;
clock-latency = <61036>; /* two CLK32 periods */
#cooling-cells = <2>;
cooling-min-level = <0>;
cooling-max-level = <2>;
};
cpu@1 {
compatible = "arm,cortex-a9";
reg = <1>;
next-level-cache = <&L2>;
};
cpu@2 {
compatible = "arm,cortex-a9";
reg = <2>;
next-level-cache = <&L2>;
};
cpu@3 {
compatible = "arm,cortex-a9";
reg = <3>;
next-level-cache = <&L2>;
};
};
Documentation/devicetree/bindings/crypto/fsl-sec6.txt
浏览文件 @ 1b62f19c
SEC 6 is as Freescale's Cryptographic Accelerator and Assurance Module (CAAM).
Currently Freescale powerpc chip C29X is embeded with SEC 6.
Currently Freescale powerpc chip C29X is embedded with SEC 6.
SEC 6 device tree binding include:
-SEC 6 Node
-Job Ring Node
......
Documentation/devicetree/bindings/dma/qcom_adm.txt 0 → 100644
浏览文件 @ 1b62f19c
QCOM ADM DMA Controller
Required properties:
- compatible: must contain "qcom,adm" for IPQ/APQ8064 and MSM8960
- reg: Address range for DMA registers
- interrupts: Should contain one interrupt shared by all channels
- #dma-cells: must be <2>. First cell denotes the channel number. Second cell
denotes CRCI (client rate control interface) flow control assignment.
- clocks: Should contain the core clock and interface clock.
- clock-names: Must contain "core" for the core clock and "iface" for the
interface clock.
- resets: Must contain an entry for each entry in reset names.
- reset-names: Must include the following entries:
- clk
- c0
- c1
- c2
- qcom,ee: indicates the security domain identifier used in the secure world.
Example:
adm_dma: dma@18300000 {
compatible = "qcom,adm";
reg = <0x18300000 0x100000>;
interrupts = <0 170 0>;
#dma-cells = <2>;
clocks = <&gcc ADM0_CLK>, <&gcc ADM0_PBUS_CLK>;
clock-names = "core", "iface";
resets = <&gcc ADM0_RESET>,
<&gcc ADM0_C0_RESET>,
<&gcc ADM0_C1_RESET>,
<&gcc ADM0_C2_RESET>;
reset-names = "clk", "c0", "c1", "c2";
qcom,ee = <0>;
};
DMA clients must use the format descripted in the dma.txt file, using a three
cell specifier for each channel.
Each dmas request consists of 3 cells:
1. phandle pointing to the DMA controller
2. channel number
3. CRCI assignment, if applicable. If no CRCI flow control is required, use 0.
The CRCI is used for flow control. It identifies the peripheral device that
is the source/destination for the transferred data.
Example:
spi4: spi@1a280000 {
status = "ok";
spi-max-frequency = <50000000>;
pinctrl-0 = <&spi_pins>;
pinctrl-names = "default";
cs-gpios = <&qcom_pinmux 20 0>;
dmas = <&adm_dma 6 9>,
<&adm_dma 5 10>;
dma-names = "rx", "tx";
};
Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt 0 → 100644
浏览文件 @ 1b62f19c
Xilinx AXI DMA engine, it does transfers between memory and AXI4 stream
target devices. It can be configured to have one channel or two channels.
If configured as two channels, one is to transmit to the device and another
is to receive from the device.
Required properties:
- compatible: Should be "xlnx,axi-dma-1.00.a"
- #dma-cells: Should be <1>, see "dmas" property below
- reg: Should contain DMA registers location and length.
- dma-channel child node: Should have atleast one channel and can have upto
two channels per device. This node specifies the properties of each
DMA channel (see child node properties below).
Optional properties:
- xlnx,include-sg: Tells whether configured for Scatter-mode in
the hardware.
Required child node properties:
- compatible: It should be either "xlnx,axi-dma-mm2s-channel" or
"xlnx,axi-dma-s2mm-channel".
- interrupts: Should contain per channel DMA interrupts.
- xlnx,datawidth: Should contain the stream data width, take values
{32,64...1024}.
Option child node properties:
- xlnx,include-dre: Tells whether hardware is configured for Data
Realignment Engine.
Example:
++++++++
axi_dma_0: axidma@40400000 {
compatible = "xlnx,axi-dma-1.00.a";
#dma_cells = <1>;
reg = < 0x40400000 0x10000 >;
dma-channel@40400000 {
compatible = "xlnx,axi-dma-mm2s-channel";
interrupts = < 0 59 4 >;
xlnx,datawidth = <0x40>;
} ;
dma-channel@40400030 {
compatible = "xlnx,axi-dma-s2mm-channel";
interrupts = < 0 58 4 >;
xlnx,datawidth = <0x40>;
} ;
} ;
* DMA client
Required properties:
- dmas: a list of <[DMA device phandle] [Channel ID]> pairs,
where Channel ID is '0' for write/tx and '1' for read/rx
channel.
- dma-names: a list of DMA channel names, one per "dmas" entry
Example:
++++++++
dmatest_0: dmatest@0 {
compatible ="xlnx,axi-dma-test-1.00.a";
dmas = <&axi_dma_0 0
&axi_dma_0 1>;
dma-names = "dma0", "dma1";
} ;
Documentation/devicetree/bindings/drm/tilcdc/panel.txt
浏览文件 @ 1b62f19c
......@@ -18,6 +18,10 @@ Required properties:
Documentation/devicetree/bindings/video/display-timing.txt for display
timing binding details.
Optional properties:
- backlight: phandle of the backlight device attached to the panel
- enable-gpios: GPIO pin to enable or disable the panel
Recommended properties:
- pinctrl-names, pinctrl-0: the pincontrol settings to configure
muxing properly for pins that connect to TFP410 device
......@@ -29,6 +33,9 @@ Example:
compatible = "ti,tilcdc,panel";
pinctrl-names = "default";
pinctrl-0 = <&bone_lcd3_cape_lcd_pins>;
backlight = <&backlight>;
enable-gpios = <&gpio3 19 0>;
panel-info {
ac-bias = <255>;
ac-bias-intrpt = <0>;
......
Documentation/devicetree/bindings/extcon/extcon-rt8973a.txt 0 → 100644
浏览文件 @ 1b62f19c
* Richtek RT8973A - Micro USB Switch device
The Richtek RT8973A is Micro USB Switch with OVP and I2C interface. The RT8973A
is a USB port accessory detector and switch that is optimized to protect low
voltage system from abnormal high input voltage (up to 28V) and supports high
speed USB operation. Also, RT8973A support 'auto-configuration' mode.
If auto-configuration mode is enabled, RT8973A would control internal h/w patch
for USB D-/D+ switching.
Required properties:
- compatible: Should be "richtek,rt8973a-muic"
- reg: Specifies the I2C slave address of the MUIC block. It should be 0x14
- interrupt-parent: Specifies the phandle of the interrupt controller to which
the interrupts from rt8973a are delivered to.
- interrupts: Interrupt specifiers for detection interrupt sources.
Example:
rt8973a@14 {
compatible = "richtek,rt8973a-muic";
interrupt-parent = <&gpx1>;
interrupts = <5 0>;
reg = <0x14>;
};
Documentation/devicetree/bindings/gpio/gpio-dsp-keystone.txt 0 → 100644
浏览文件 @ 1b62f19c
Keystone 2 DSP GPIO controller bindings
HOST OS userland running on ARM can send interrupts to DSP cores using
the DSP GPIO controller IP. It provides 28 IRQ signals per each DSP core.
This is one of the component used by the IPC mechanism used on Keystone SOCs.
For example TCI6638K2K SoC has 8 DSP GPIO controllers:
- 8 for C66x CorePacx CPUs 0-7
Keystone 2 DSP GPIO controller has specific features:
- each GPIO can be configured only as output pin;
- setting GPIO value to 1 causes IRQ generation on target DSP core;
- reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
pending.
Required Properties:
- compatible: should be "ti,keystone-dsp-gpio"
- ti,syscon-dev: phandle/offset pair. The phandle to syscon used to
access device state control registers and the offset of device's specific
registers within device state control registers range.
- gpio-controller: Marks the device node as a gpio controller.
- #gpio-cells: Should be 2.
Please refer to gpio.txt in this directory for details of the common GPIO
bindings used by client devices.
Example:
dspgpio0: keystone_dsp_gpio@02620240 {
compatible = "ti,keystone-dsp-gpio";
ti,syscon-dev = <&devctrl 0x240>;
gpio-controller;
#gpio-cells = <2>;
};
dsp0: dsp0 {
compatible = "linux,rproc-user";
...
kick-gpio = <&dspgpio0 27>;
};
Documentation/devicetree/bindings/gpio/gpio-pca953x.txt 0 → 100644
浏览文件 @ 1b62f19c
* NXP PCA953x I2C GPIO multiplexer
Required properties:
- compatible: Has to contain one of the following:
nxp,pca9505
nxp,pca9534
nxp,pca9535
nxp,pca9536
nxp,pca9537
nxp,pca9538
nxp,pca9539
nxp,pca9554
nxp,pca9555
nxp,pca9556
nxp,pca9557
nxp,pca9574
nxp,pca9575
nxp,pca9698
maxim,max7310
maxim,max7312
maxim,max7313
maxim,max7315
ti,pca6107
ti,tca6408
ti,tca6416
ti,tca6424
exar,xra1202
Example:
gpio@20 {
compatible = "nxp,pca9505";
reg = <0x20>;
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_pca9505>;
interrupt-parent = <&gpio3>;
interrupts = <23 IRQ_TYPE_LEVEL_LOW>;
};
Documentation/devicetree/bindings/gpio/gpio-restart.txt 0 → 100644
浏览文件 @ 1b62f19c
Drive a GPIO line that can be used to restart the system from a restart
handler.
This binding supports level and edge triggered reset. At driver load
time, the driver will request the given gpio line and install a restart
handler. If the optional properties 'open-source' is not found, the GPIO line
will be driven in the inactive state. Otherwise its not driven until
the restart is initiated.
When the system is restarted, the restart handler will be invoked in
priority order. The gpio is configured as an output, and driven active,
triggering a level triggered reset condition. This will also cause an
inactive->active edge condition, triggering positive edge triggered
reset. After a delay specified by active-delay, the GPIO is set to
inactive, thus causing an active->inactive edge, triggering negative edge
triggered reset. After a delay specified by inactive-delay, the GPIO
is driven active again. After a delay specified by wait-delay, the
restart handler completes allowing other restart handlers to be attempted.
Required properties:
- compatible : should be "gpio-restart".
- gpios : The GPIO to set high/low, see "gpios property" in
Documentation/devicetree/bindings/gpio/gpio.txt. If the pin should be
low to reset the board set it to "Active Low", otherwise set
gpio to "Active High".
Optional properties:
- open-source : Treat the GPIO as being open source and defer driving
it to when the restart is initiated. If this optional property is not
specified, the GPIO is initialized as an output in its inactive state.
- priority : A priority ranging from 0 to 255 (default 128) according to
the following guidelines:
0: Restart handler of last resort, with limited restart
capabilities
128: Default restart handler; use if no other restart handler is
expected to be available, and/or if restart functionality is
sufficient to restart the entire system
255: Highest priority restart handler, will preempt all other
restart handlers
- active-delay: Delay (default 100) to wait after driving gpio active [ms]
- inactive-delay: Delay (default 100) to wait after driving gpio inactive [ms]
- wait-delay: Delay (default 3000) to wait after completing restart
sequence [ms]
Examples:
gpio-restart {
compatible = "gpio-restart";
gpios = <&gpio 4 0>;
priority = <128>;
active-delay = <100>;
inactive-delay = <100>;
wait-delay = <3000>;
};
Documentation/devicetree/bindings/gpio/gpio-xgene.txt 0 → 100644
浏览文件 @ 1b62f19c
APM X-Gene SoC GPIO controller bindings
This is a gpio controller that is part of the flash controller.
This gpio controller controls a total of 48 gpios.
Required properties:
- compatible: "apm,xgene-gpio" for X-Gene GPIO controller
- reg: Physical base address and size of the controller's registers
- #gpio-cells: Should be two.
- first cell is the pin number
- second cell is used to specify the gpio polarity:
0 = active high
1 = active low
- gpio-controller: Marks the device node as a GPIO controller.
Example:
gpio0: gpio0@1701c000 {
compatible = "apm,xgene-gpio";
reg = <0x0 0x1701c000 0x0 0x40>;
gpio-controller;
#gpio-cells = <2>;
};
Documentation/devicetree/bindings/gpio/mrvl-gpio.txt
浏览文件 @ 1b62f19c
......@@ -19,7 +19,7 @@ Required properties:
- gpio-controller : Marks the device node as a gpio controller.
- #gpio-cells : Should be one. It is the pin number.
Example:
Example for a MMP platform:
gpio: gpio@d4019000 {
compatible = "marvell,mmp-gpio";
......@@ -32,6 +32,19 @@ Example:
#interrupt-cells = <1>;
};
Example for a PXA3xx platform:
gpio: gpio@40e00000 {
compatible = "intel,pxa3xx-gpio";
reg = <0x40e00000 0x10000>;
interrupt-names = "gpio0", "gpio1", "gpio_mux";
interrupts = <8 9 10>;
gpio-controller;
#gpio-cells = <0x2>;
interrupt-controller;
#interrupt-cells = <0x2>;
};
* Marvell Orion GPIO Controller
Required properties:
......
Documentation/devicetree/bindings/hwmon/ntc_thermistor.txt
浏览文件 @ 1b62f19c
......@@ -25,6 +25,9 @@ Requires node properties:
- "io-channels" Channel node of ADC to be used for
conversion.
Optional node properties:
- "#thermal-sensor-cells" Used to expose itself to thermal fw.
Read more about iio bindings at
Documentation/devicetree/bindings/iio/iio-bindings.txt
......
Documentation/devicetree/bindings/i2c/i2c-axxia.txt 0 → 100644
浏览文件 @ 1b62f19c
LSI Axxia I2C
Required properties :
- compatible : Must be "lsi,api2c"
- reg : Offset and length of the register set for the device
- interrupts : the interrupt specifier
- #address-cells : Must be <1>;
- #size-cells : Must be <0>;
- clock-names : Must contain "i2c".
- clocks: Must contain an entry for each name in clock-names. See the common
clock bindings.
Optional properties :
- clock-frequency : Desired I2C bus clock frequency in Hz. If not specified,
the default 100 kHz frequency will be used. As only Normal and Fast modes
are supported, possible values are 100000 and 400000.
Example :
i2c@02010084000 {
compatible = "lsi,api2c";
device_type = "i2c";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x20 0x10084000 0x00 0x1000>;
interrupts = <0 19 4>;
clocks = <&clk_per>;
clock-names = "i2c";
clock-frequency = <400000>;
};
Documentation/devicetree/bindings/i2c/i2c-exynos5.txt
浏览文件 @ 1b62f19c
......@@ -12,6 +12,8 @@ Required properties:
on Exynos5250 and Exynos5420 SoCs.
-> "samsung,exynos5260-hsi2c", for i2c compatible with HSI2C available
on Exynos5260 SoCs.
-> "samsung,exynos7-hsi2c", for i2c compatible with HSI2C available
on Exynos7 SoCs.
- reg: physical base address of the controller and length of memory mapped
region.
......
Documentation/devicetree/bindings/i2c/i2c-hix5hd2.txt 0 → 100644
浏览文件 @ 1b62f19c
I2C for Hisilicon hix5hd2 chipset platform
Required properties:
- compatible: Must be "hisilicon,hix5hd2-i2c"
- reg: physical base address of the controller and length of memory mapped
region.
- interrupts: interrupt number to the cpu.
- #address-cells = <1>;
- #size-cells = <0>;
- clocks: phandles to input clocks.
Optional properties:
- clock-frequency: Desired I2C bus frequency in Hz, otherwise defaults to 100000
- Child nodes conforming to i2c bus binding
Examples:
I2C0@f8b10000 {
compatible = "hisilicon,hix5hd2-i2c";
reg = <0xf8b10000 0x1000>;
interrupts = <0 38 4>;
clocks = <&clock HIX5HD2_I2C0_RST>;
#address-cells = <1>;
#size-cells = <0>;
}
Documentation/devicetree/bindings/i2c/ti,bq32k.txt 0 → 100644
浏览文件 @ 1b62f19c
* TI BQ32000 I2C Serial Real-Time Clock
Required properties:
- compatible: Should contain "ti,bq32000".
- reg: I2C address for chip
Optional properties:
- trickle-resistor-ohms : Selected resistor for trickle charger
Values usable are 1120 and 20180
Should be given if trickle charger should be enabled
- trickle-diode-disable : Do not use internal trickle charger diode
Should be given if internal trickle charger diode should be disabled
Example:
bq32000: rtc@68 {
compatible = "ti,bq32000";
trickle-resistor-ohms = <1120>;
reg = <0x68>;
};
Documentation/devicetree/bindings/i2c/trivial-devices.txt
浏览文件 @ 1b62f19c
......@@ -35,7 +35,6 @@ catalyst,24c32 i2c serial eeprom
cirrus,cs42l51 Cirrus Logic CS42L51 audio codec
dallas,ds1307 64 x 8, Serial, I2C Real-Time Clock
dallas,ds1338 I2C RTC with 56-Byte NV RAM
dallas,ds1339 I2C Serial Real-Time Clock
dallas,ds1340 I2C RTC with Trickle Charger
dallas,ds1374 I2C, 32-Bit Binary Counter Watchdog RTC with Trickle Charger and Reset Input/Output
dallas,ds1631 High-Precision Digital Thermometer
......@@ -44,7 +43,7 @@ dallas,ds1775 Tiny Digital Thermometer and Thermostat
dallas,ds3232 Extremely Accurate I²C RTC with Integrated Crystal and SRAM
dallas,ds4510 CPU Supervisor with Nonvolatile Memory and Programmable I/O
dallas,ds75 Digital Thermometer and Thermostat
dialog,da9053 DA9053: flexible system level PMIC with multicore support
dlg,da9053 DA9053: flexible system level PMIC with multicore support
epson,rx8025 High-Stability. I2C-Bus INTERFACE REAL TIME CLOCK MODULE
epson,rx8581 I2C-BUS INTERFACE REAL TIME CLOCK MODULE
fsl,mag3110 MAG3110: Xtrinsic High Accuracy, 3D Magnetometer
......
Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt 0 → 100644
浏览文件 @ 1b62f19c
Rockchip Successive Approximation Register (SAR) A/D Converter bindings
Required properties:
- compatible: Should be "rockchip,saradc"
- reg: physical base address of the controller and length of memory mapped
region.
- interrupts: The interrupt number to the cpu. The interrupt specifier format
depends on the interrupt controller.
- clocks: Must contain an entry for each entry in clock-names.
- clock-names: Shall be "saradc" for the converter-clock, and "apb_pclk" for
the peripheral clock.
- vref-supply: The regulator supply ADC reference voltage.
- #io-channel-cells: Should be 1, see ../iio-bindings.txt
Example:
saradc: saradc@2006c000 {
compatible = "rockchip,saradc";
reg = <0x2006c000 0x100>;
interrupts = <GIC_SPI 26 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&cru SCLK_SARADC>, <&cru PCLK_SARADC>;
clock-names = "saradc", "apb_pclk";
#io-channel-cells = <1>;
vref-supply = <&vcc18>;
};
Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
浏览文件 @ 1b62f19c
......@@ -9,7 +9,7 @@ Required properties:
- interrupts: Should contain the interrupt for the device
- clocks: The clock is needed by the ADC controller, ADC clock source is ipg clock.
- clock-names: Must contain "adc", matching entry in the clocks property.
- vref-supply: The regulator supply ADC refrence voltage.
- vref-supply: The regulator supply ADC reference voltage.
Example:
adc0: adc@4003b000 {
......
Documentation/devicetree/bindings/iio/dac/max5821.txt 0 → 100644
浏览文件 @ 1b62f19c
Maxim max5821 DAC device driver
Required properties:
- compatible: Must be "maxim,max5821"
- reg: Should contain the DAC I2C address
- vref-supply: Phandle to the vref power supply
Example:
max5821@38 {
compatible = "maxim,max5821";
reg = <0x38>;
vref-supply = <&reg_max5821>;
};
Documentation/devicetree/bindings/input/ti,drv260x.txt 0 → 100644
浏览文件 @ 1b62f19c
* Texas Instruments - drv260x Haptics driver family
Required properties:
- compatible - One of:
"ti,drv2604" - DRV2604
"ti,drv2605" - DRV2605
"ti,drv2605l" - DRV2605L
- reg - I2C slave address
- vbat-supply - Required supply regulator
- mode - Power up mode of the chip (defined in include/dt-bindings/input/ti-drv260x.h)
DRV260X_LRA_MODE - Linear Resonance Actuator mode (Piezoelectric)
DRV260X_LRA_NO_CAL_MODE - This is a LRA Mode but there is no calibration
sequence during init. And the device is configured for real
time playback mode (RTP mode).
DRV260X_ERM_MODE - Eccentric Rotating Mass mode (Rotary vibrator)
- library-sel - These are ROM based waveforms pre-programmed into the IC.
This should be set to set the library to use at power up.
(defined in include/dt-bindings/input/ti-drv260x.h)
DRV260X_LIB_EMPTY - Do not use a pre-programmed library
DRV260X_ERM_LIB_A - Pre-programmed Library
DRV260X_ERM_LIB_B - Pre-programmed Library
DRV260X_ERM_LIB_C - Pre-programmed Library
DRV260X_ERM_LIB_D - Pre-programmed Library
DRV260X_ERM_LIB_E - Pre-programmed Library
DRV260X_ERM_LIB_F - Pre-programmed Library
DRV260X_LIB_LRA - Pre-programmed LRA Library
Optional properties:
- enable-gpio - gpio pin to enable/disable the device.
- vib-rated-mv - The rated voltage of the actuator in millivolts.
If this is not set then the value will be defaulted to
3.2 v.
- vib-overdrive-mv - The overdrive voltage of the actuator in millivolts.
If this is not set then the value will be defaulted to
3.2 v.
Example:
haptics: haptics@5a {
compatible = "ti,drv2605l";
reg = <0x5a>;
vbat-supply = <&vbat>;
enable-gpio = <&gpio1 28 GPIO_ACTIVE_HIGH>;
mode = <DRV260X_LRA_MODE>;
library-sel = <DRV260X_LIB_LRA>;
vib-rated-mv = <3200>;
vib-overdriver-mv = <3200>;
}
For more product information please see the link below:
http://www.ti.com/product/drv2605
Documentation/devicetree/bindings/input/ti,drv2667.txt 0 → 100644
浏览文件 @ 1b62f19c
* Texas Instruments - drv2667 Haptics driver
Required properties:
- compatible - "ti,drv2667" - DRV2667
- reg - I2C slave address
- vbat-supply - Required supply regulator
Example:
haptics: haptics@59 {
compatible = "ti,drv2667";
reg = <0x59>;
vbat-supply = <&vbat>;
};
For more product information please see the link below:
http://www.ti.com/product/drv2667
Documentation/devicetree/bindings/input/ti,palmas-pwrbutton.txt 0 → 100644
浏览文件 @ 1b62f19c
Texas Instruments Palmas family power button module
This module is part of the Palmas family of PMICs. For more details
about the whole chip see:
Documentation/devicetree/bindings/mfd/palmas.txt.
This module provides a simple power button event via an Interrupt.
Required properties:
- compatible: should be one of the following
- "ti,palmas-pwrbutton": For Palmas compatible power on button
- interrupt-parent: Parent interrupt device, must be handle of palmas node.
- interrupts: Interrupt number of power button submodule on device.
Optional Properties:
- ti,palmas-long-press-seconds: Duration in seconds which the power
button should be kept pressed for Palmas to power off automatically.
NOTE: This depends on OTP support and POWERHOLD signal configuration
on platform. Valid values are 6, 8, 10 and 12.
- ti,palmas-pwron-debounce-milli-seconds: Duration in milliseconds
which the power button should be kept pressed for Palmas to register
a press for debouncing purposes. NOTE: This depends on specific
Palmas variation capability. Valid values are 15, 100, 500 and 1000.
Example:
&palmas {
palmas_pwr_button: pwrbutton {
compatible = "ti,palmas-pwrbutton";
interrupt-parent = <&tps659038>;
interrupts = <1 IRQ_TYPE_EDGE_FALLING>;
ti,palmas-long-press-seconds = <12>;
ti,palmas-pwron-debounce-milli-seconds = <15>;
};
};
Documentation/devicetree/bindings/interrupt-controller/atmel,aic.txt
浏览文件 @ 1b62f19c
......@@ -2,7 +2,7 @@
Required properties:
- compatible: Should be "atmel,<chip>-aic"
<chip> can be "at91rm9200" or "sama5d3"
<chip> can be "at91rm9200", "sama5d3" or "sama5d4"
- interrupt-controller: Identifies the node as an interrupt controller.
- interrupt-parent: For single AIC system, it is an empty property.
- #interrupt-cells: The number of cells to define the interrupts. It should be 3.
......
Documentation/devicetree/bindings/mfd/atmel-gpbr.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/mfd/hi6421.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/mfd/max14577.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/mfd/qcom-pm8xxx.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/mfd/rk808.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/mfd/rn5t618.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/net/broadcom-sf2.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/net/can/m_can.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/net/can/rcar_can.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/net/emac_rockchip.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/net/meson-dwmac.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/pci/fsl,pci.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/pci/pci-keystone.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/pci/xgene-pci.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/pci/xilinx-pcie.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/regmap/regmap.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/regulator/da9211.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/regulator/isl9305.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/rng/apm,rng.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/rtc/dallas,ds1339.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/rtc/sun6i-rtc.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/serial/mtk-uart.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/sound/adi,ssm2602.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/sound/cs35l32.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/sound/es8328.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/sound/rt5677.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/sound/ssm4567.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/usb/dwc3-st.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/usb/ehci-st.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/usb/ohci-st.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/usb/qcom,dwc3.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/usb/renesas_usbhs.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/usb/udc-xilinx.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/video/adi,adv7123.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/bindings/video/renesas,du.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/devicetree/dynamic-resolution-notes.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/dmaengine.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/filesystems/.gitignore 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/filesystems/Locking
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/filesystems/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/filesystems/autofs4.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/filesystems/f2fs.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/filesystems/ntfs.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/filesystems/vfs.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/gpio/driver.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/hid/uhid.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/hwmon/k10temp
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/hwmon/menf21bmc 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/i2c/busses/i2c-i801
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/ia64/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/kbuild/makefiles.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/kernel-parameters.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/kmemleak.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/kprobes.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/laptops/.gitignore 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/laptops/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/locking/lockstat.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/locking/locktorture.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/locking/mutex-design.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/locking/spinlocks.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/lockstat.txt 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
Documentation/lockup-watchdogs.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/lzo.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/memory-barriers.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/memory-hotplug.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/mic/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/mic/mpssd/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/mic/mpssd/mpssd.c
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/misc-devices/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/mutex-design.txt 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
Documentation/networking/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/networking/dctcp.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/networking/filter.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/networking/pktgen.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/networking/timestamping/txtimestamp.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/pcmcia/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/pinctrl.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/power/suspend-and-interrupts.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/powerpc/00-INDEX
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/powerpc/cxl.txt 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/prctl/.gitignore 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/prctl/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/printk-formats.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/ptp/.gitignore 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/ptp/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/ptp/testptp.c
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/ptp/testptp.mk 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
Documentation/security/keys.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/serial/driver
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/serial/tty.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/spi/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/spi/spi-summary
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/spinlocks.txt 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
Documentation/sysctl/kernel.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/sysctl/net.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/sysfs-rules.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/this_cpu_ops.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/timers/.gitignore 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/timers/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/usb/hotplug.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/vDSO/.gitignore 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/vDSO/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/video4linux/.gitignore 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
Documentation/video4linux/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/virtual/kvm/api.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/virtual/kvm/mmu.txt
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/watchdog/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/watchdog/src/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
Documentation/x86/x86_64/mm.txt
浏览文件 @ 1b62f19c
此差异已折叠。
MAINTAINERS
浏览文件 @ 1b62f19c
此差异已折叠。
Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/alpha/include/asm/Kbuild
浏览文件 @ 1b62f19c
此差异已折叠。
arch/alpha/include/asm/atomic.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/alpha/include/asm/sections.h 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/alpha/include/asm/syscall.h 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/alpha/kernel/osf_sys.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/alpha/kernel/perf_event.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/alpha/kernel/ptrace.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/alpha/kernel/time.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arc/include/asm/Kbuild
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arc/include/asm/atomic.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/Kconfig.debug
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/bootp/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/compressed/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/am335x-bone.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/am33xx.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/am4372.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/armada-370-db.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/armada-370-rd.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/armada-370.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/armada-375.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91-sama5d4ek.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91sam9263.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91sam9g20.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91sam9g45.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91sam9n12.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91sam9n12ek.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91sam9rl.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/at91sam9x5.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/bcm2835-rpi-b.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/bcm2835.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/bcm63138.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/bcm963138dvt.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/berlin2q.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/cros-adc-thermistors.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/da850-evm.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/da850.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/dra7-evm.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/dra7.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/dra72-evm.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/dra72x.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/dra74x.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/exynos3250.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/exynos5250-cros-common.dtsi 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/boot/dts/exynos5250.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/exynos5420.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/hip04-d01.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/hip04.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx1-ads.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx1-apf9328.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx1-pinfunc.h 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx1.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx23-evk.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx25-pinfunc.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx25.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx28-evk.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx28-m28cu3.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx28-m28evk.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx28-tx28.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx28.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx35.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx50.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx51.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx53-smd.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx53.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6dl-gw552x.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6q-gw552x.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6q-hummingboard.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6qdl-gw552x.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6qdl-hummingboard.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6qdl.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6sl-evk.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6sl.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6sx-sdb.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/imx6sx.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/k2e.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/k2hk.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/k2l.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/keystone.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6281-a.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6281-a0.dts 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6281-a1.dts 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/boot/dts/kirkwood-rd88f6281-z0.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/kirkwood.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/meson.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/meson6-atv1200.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/meson6.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/mt6589.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap2.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap2420-n810.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap2420.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap2430.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-gta04.dts 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/boot/dts/omap3-gta04.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-gta04a3.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-gta04a4.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-gta04a5.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-ha-common.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-ha-lcd.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-ha.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-ldp.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-n900.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-tao3530.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3-thunder.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap3.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap4-panda.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap4.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap5-cm-t54.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap5-sbc-t54.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/omap5.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/pxa27x.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/pxa2xx.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064-cm-qs600.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-apq8064.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-apq8084-ifc6540.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-apq8084.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-ipq8064-ap148.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-ipq8064-v1.0.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-ipq8064.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-msm8660.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-msm8960.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/qcom-msm8974.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r7s72100.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a73a4.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7740.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7778.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7779.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7790-lager.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7790.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7791.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7794-alt.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/r8a7794.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/rk3066a.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/rk3188.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/rk3288-evb.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/rk3288.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/rk3xxx.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sama5d3.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sama5d3_can.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sama5d3xcm.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sama5d3xmb.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sama5d4.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sh7372.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sh73a0.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/socfpga.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/socfpga_vt.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/spear1310.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/spear1340.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun4i-a10.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun5i-a10s.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun5i-a13-hsg-h702.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun5i-a13.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun6i-a31.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-hummingbird.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun7i-a20-olinuxino-lime.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun7i-a20.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/sun8i-a23.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/tegra114.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/tegra124-nyan-big.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/tegra124.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/tegra20.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/tegra30.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/vexpress-v2m.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/vf610-colibri-eval-v3.dts 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/vf610-colibri.dts 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/boot/dts/vf610-colibri.dtsi 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/vf610-twr.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/vf610.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/zynq-7000.dtsi
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/zynq-zc702.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/zynq-zc706.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/boot/dts/zynq-zed.dts
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/common/scoop.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/ape6evm_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/at91_dt_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/bcm2835_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/bcm_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/bockw_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/clps711x_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/ep93xx_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/exynos_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/ezx_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/hi3xxx_defconfig 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/configs/hisi_defconfig 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/imote2_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/koelsch_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/kzm9g_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/lager_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/lpc32xx_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/marzen_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/multi_v7_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/mvebu_v7_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/pxa3xx_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/qcom_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/sama5_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/shmobile_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/sunxi_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/configs/tegra_defconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/crypto/sha1-armv7-neon.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/arch_timer.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/atomic.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/dma-mapping.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/ftrace.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/io.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/irq_work.h 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/kvm_emulate.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/kvm_host.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/kvm_mmu.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/mcpm.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/pgtable.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/smp.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/syscall.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/asm/tlb.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/debug/bcm63xx.S 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/debug/meson.S 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/include/uapi/asm/kvm.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/atags_parse.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/entry-armv.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/entry-common.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/entry-header.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/fiq.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/hibernate.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/hw_breakpoint.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/irq.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/perf_event_cpu.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/process.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/ptrace.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/return_address.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/setup.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/smp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/smp_twd.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/topology.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/traps.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/unwind.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kernel/vmlinux.lds.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kvm/arm.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kvm/coproc.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kvm/guest.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kvm/interrupts_head.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/kvm/mmu.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/Kconfig.non_dt
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/at91_rstc.h 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-at91/at91_shdwc.h 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-at91/at91sam9260.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/at91sam9261.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/at91sam9263.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/at91sam926x_time.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-at91/at91sam9_alt_reset.S 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-at91/at91sam9g45.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/at91sam9g45_reset.S 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-at91/at91sam9rl.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/board-cam60.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/board-cpu9krea.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/board-dt-sam9.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/board-dt-sama5.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/board-foxg20.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-at91/board-gsia18s.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/board-rsi-ews.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-at91/board-sam9rlek.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/clock.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/generic.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/include/mach/sama5d4.h 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/irq.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/pm.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/sama5d4.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/setup.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-at91/soc.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-bcm/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-bcm/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-bcm/bcm63xx.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-clps711x/common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-clps711x/common.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-clps711x/devices.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-cns3xxx/cns3420vb.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-cns3xxx/core.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-cns3xxx/core.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-cns3xxx/pcie.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-davinci/da8xx-dt.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-ebsa110/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-ep93xx/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-exynos/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-exynos/exynos.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-exynos/include/mach/memory.h 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-exynos/platsmp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-exynos/pm_domains.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-footbridge/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-hisi/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-hisi/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-hisi/hisilicon.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-hisi/platmcpm.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/anatop.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/avic.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/board-pcm038.h 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-imx/clk-gate-exclusive.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/clk-imx6q.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/clk-imx6sl.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/clk-imx6sx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/clk-pllv3.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/clk-vf610.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/clk.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/common.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/cpuidle-imx6q.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/eukrea_mbimx27-baseboard.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-imx/imx1-dt.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/imx27-dt.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/iomux-imx31.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/iomux-v1.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/iomux-v3.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/mach-cpuimx27.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-imx/mach-imx51.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/mach-imx6sx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/mach-mx1ads.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-imx/mach-mx31_3ds.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/mach-mx31lite.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/mach-mxt_td60.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-imx/mach-pcm037.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/mach-pcm038.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-imx/mxc.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/pcm970-baseboard.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-imx/platsmp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/time.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-imx/tzic.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-integrator/impd1.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-integrator/pci_v3.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-iop13xx/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-iop32x/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-iop33x/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-ks8695/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-lpc32xx/common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-meson/Kconfig 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-meson/Makefile 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-meson/meson.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-msm/board-mahimahi.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-msm/board-msm7x30.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-msm/board-trout.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-msm/io.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-mvebu/pmsu.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/board-3430sdp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/board-cm-t35.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/board-generic.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/board-ldp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/board-n8x0.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/board-overo.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/board-rx51.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/common.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/display.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/gpmc.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/hdq1w.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/i2c.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/io.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/irq.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-omap2/msdi.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/mux.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/omap-secure.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/omap4-common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/omap_hwmod.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/omap_hwmod.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/pdata-quirks.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/pm.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/pm.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/pm34xx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/pm44xx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/powerdomain.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/powerdomain.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/prm3xxx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/prm44xx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/prm_common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/prminst44xx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/prminst44xx.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/sr_device.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/sram.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/sram.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/timer.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/vc.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/voltage.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-omap2/wd_timer.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-orion5x/ts209-setup.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-orion5x/ts409-setup.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-pxa/devices.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-pxa/devices.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-pxa/lpd270.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-pxa/pxa3xx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-qcom/board.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-rockchip/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-rpc/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/common.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-anubis.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-bast.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-gta02.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-h1940.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-jive.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-n30.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-osiris.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-otom.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-qt2410.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-rx1950.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-rx3715.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-vr1000.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/mach-vstms.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/s3c2410.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/s3c2412.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/s3c2416.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/s3c2443.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c24xx/s3c244x.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c64xx/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c64xx/common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c64xx/common.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c64xx/mach-hmt.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c64xx/mach-ncp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s3c64xx/pm.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s5pv210/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s5pv210/pm.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s5pv210/regs-clock.h 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-s5pv210/s5pv210.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-sa1100/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-sa1100/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-sa1100/h3xxx.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/board-genmai.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-shmobile/clock-r7s72100.c 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-shmobile/common.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/cpufreq.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/intc.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/irqs.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/pm-r8a7740.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/pm-r8a7779.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/pm-rcar.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/pm-rmobile.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/pm-rmobile.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/r7s72100.h 已删除 100644 → 0
浏览文件 @ a66d05d5
此差异已折叠。
arch/arm/mach-shmobile/r8a73a4.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/r8a7740.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/r8a7779.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/r8a7790.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/r8a7791.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/setup-r8a7794.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-shmobile/timer.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-spear/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-sunxi/sunxi.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-tegra/flowctrl.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-tegra/flowctrl.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-tegra/tegra.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-u300/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-vt8500/vt8500.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-zynq/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-zynq/common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-zynq/common.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-zynq/hotplug.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-zynq/platsmp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-zynq/pm.c 0 → 100644
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mach-zynq/slcr.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/cache-l2x0.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/dma-mapping.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/flush.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/idmap.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/init.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/mmu.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/proc-macros.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/mm/proc-v7.S
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/net/bpf_jit_32.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/net/bpf_jit_32.h
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-iop/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-omap/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-omap/dma.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-orion/common.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-pxa/ssp.c
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-samsung/Kconfig
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-samsung/Makefile
浏览文件 @ 1b62f19c
此差异已折叠。
arch/arm/plat-samsung/pm-debug.c
浏览文件 @ 1b62f19c
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或