| /linux-4.1.27/drivers/irqchip/ |
| D | irq-gic-v3-its.c | 91 struct its_node *its; member
109 struct its_node *its = its_dev->its; in dev_event_to_col() local
111 return its->collections + its_dev->event_map.col_map[event]; in dev_event_to_col()
354 static u64 its_cmd_ptr_to_offset(struct its_node *its, in its_cmd_ptr_to_offset() argument
357 return (ptr - its->cmd_base) * sizeof(*ptr); in its_cmd_ptr_to_offset()
360 static int its_queue_full(struct its_node *its) in its_queue_full() argument
365 widx = its->cmd_write - its->cmd_base; in its_queue_full()
366 ridx = readl_relaxed(its->base + GITS_CREADR) / sizeof(struct its_cmd_block); in its_queue_full()
375 static struct its_cmd_block *its_allocate_entry(struct its_node *its) in its_allocate_entry() argument
380 while (its_queue_full(its)) { in its_allocate_entry()
[all …]
|
| /linux-4.1.27/arch/arm/mach-imx/ |
| D | Kconfig | 145 configurations for the board and its peripherals.
160 configurations for the board and its peripherals.
180 configurations for the board and its peripherals.
195 Include support for Visstrim_m10 platform and its different variants.
196 This includes specific configurations for the board and its
216 includes specific configurations for the module and its peripherals.
240 configurations for the board and its peripherals.
262 specific configurations for the board and its peripherals.
278 configurations for the board and its peripherals.
295 specific configurations for the board and its peripherals.
[all …]
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | gic-v3.txt | 58 - compatible : Should at least contain "arm,gic-v3-its".
83 gic-its@2c200000 {
84 compatible = "arm,gic-v3-its";
107 gic-its@2c200000 {
108 compatible = "arm,gic-v3-its";
113 gic-its@2c400000 {
114 compatible = "arm,gic-v3-its";
|
| D | arch_timer.txt | 7 The per-core architected timer is attached to a GIC to deliver its
9 to deliver its interrupts via SPIs.
|
| D | twd.txt | 7 The TWD is usually attached to a GIC to deliver its two per-processor
|
| D | vexpress-scc.txt | 8 In some cases its registers are also mapped in normal address space
|
| /linux-4.1.27/Documentation/devicetree/bindings/iommu/ |
| D | rockchip,iommu.txt | 5 its master device. Each slave device is bound to a single master device, and
6 shares its clocks, power domain and irq.
15 to associate with its master device. See:
|
| D | samsung,sysmmu.txt | 21 * MFC has one System MMU on its left and right bus.
42 - clock-names: Should be "sysmmu" if the System MMU is needed to gate its clock.
47 - clocks: Required if the System MMU is needed to gate its clock.
48 - power-domains: Required if the System MMU is needed to gate its power.
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-devices-online | 11 successful) its 'offline' field is updated accordingly. In
14 for the device and (if successful) its 'offline' field is
19 it is removed (i.e. device_del() is called for it), or its bus
|
| D | configfs-spear-pcie-gadget | 8 as device and then program its various registers to configure it
18 link ... used to enable ltssm and read its status.
|
| D | sysfs-bus-usb-devices-usbsevseg | 23 Description: Controls the way the device interprets its text buffer.
24 raw: each character controls its segment manually
|
| D | sysfs-driver-xen-blkfront | 10 and its default backend value.
|
| D | debugfs-ideapad | 17 status shows infos we can read and tells its meaning and value.
|
| D | sysfs-class-leds-gt683r | 7 of one LED will update the mode of its two sibling devices as
|
| D | sysfs-class-mic.txt | 73 An Intel MIC device runs a Linux OS during its operation. This
89 An Intel MIC device runs a Linux OS during its operation. Before
136 An Intel MIC device runs a Linux OS during its operation. For
150 An Intel MIC device runs a Linux OS during its operation. For
|
| D | sysfs-platform-dell-laptop | 33 To enable a trigger, write its name preceded by '+' to
34 this file. To disable a trigger, write its name preceded
|
| D | sysfs-wusb_cbaf | 28 6. The CM looks it up its database.
35 matching CDID in its database), the device is
|
| D | sysfs-class-mei | 23 The ME FW writes its status information into fw status
|
| D | sysfs-bus-iio-frequency-adf4350 | 21 down the PLL and its RFOut buffers during REFin changes.
|
| D | sysfs-bus-mdio | 19 appropriate mode for its data lines to the PHY hardware.
|
| D | sysfs-class-net-mesh | 75 Defines the isolation mark (and its bitmask) which
101 sends its protocol messages.
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
| D | par_io.txt | 11 - reg : offset to the register set and its length.
27 via its own gpio-controller node:
33 - reg : offset to the register set and its length.
|
| /linux-4.1.27/Documentation/power/ |
| D | runtime_pm.txt | 102 the helper functions described in Section 4 for the device until its status
107 mechanism allowing the device to request a change of its power state, such as
130 4 for the device, until its status is directly set to either 'active', or
142 idle callback with the device as its argument.
262 PM core as 'suspended', regardless of its real hardware status
314 then run pm_runtime_autosuspend(dev) and return its result
368 return its result
372 return its result
379 pm_request_idle(dev) and return its result
383 pm_request_autosuspend(dev) and return its result
[all …]
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | fault_injection.txt | 8 observe how the client reacts and if it manages to recover its state correctly.
42 its files.
46 Clearing this list will force the client to reclaim its locks (files are
52 force the client to reaquire its delegation before accessing the file
57 access a file. This test will notify the client that its delegation has
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | object.txt | 96 Within FS-Cache, each active object is managed by its own individual state
106 be created or accessed with respect to its parent object.
159 preparation states in which the object sets itself up and waits for its parent
160 object to transit to a state that allows access to its children:
205 There are some normal running states in which the object spends its time
243 The object comes here if it is dying due to an error, because its parent
248 can destroy themselves. This object waits for all its children to go away
253 The object comes to this state if it was waiting on its parent in
254 FSCACHE_OBJECT_INIT, but its parent died. The object will destroy itself
261 all its children, if it is dying because the netfs relinquished its
[all …]
|
| /linux-4.1.27/Documentation/ABI/removed/ |
| D | raw1394 | 6 access to FireWire buses. Its major drawbacks were its inability
7 to implement sensible device security policies, and its low level
|
| D | video1394 | 8 performance issues in its first generation. Any video1394 user had
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | lm95245 | 22 the temperature of a remote diode as well as its own temperature.
31 Each sensor has its own critical limit. Additionally, there is a relative
38 The lm95245 driver can change its update interval to a fixed set of values.
|
| D | lm95234 | 23 or four (LM95234) remote diodes as well as its own temperature.
33 Each sensor has its own maximum limit, but the hysteresis is common to all
38 The lm95234 driver can change its update interval to a fixed set of values.
|
| D | max1619 | 18 The MAX1619 is a digital temperature sensor. It senses its own temperature as
26 The max1619 driver will not update its values more frequently than every
|
| D | abx500 | 25 specific abx500 chip has its special configurations in its own file, e.g. some
|
| D | adm1031 | 31 Each temperature channel has its own high and low limits, plus a critical
35 two. Each fan channel has its own low speed limit.
|
| D | lm77 | 25 the limit and its hysteresis is always the same for all 3 limits.
28 * When setting a limit, its hysteresis will automatically follow, the
|
| D | lm83 | 21 The LM83 is a digital temperature sensor. It senses its own temperature as
79 Each sensor has its own high limit, but the critical limit is common to
83 The lm83 driver will not update its values more frequently than every
|
| D | emc1403 | 45 difference between the limit and its hysteresis is always the same for
49 * When setting a limit, its hysteresis will automatically follow, the
|
| D | sis5595 | 88 triggered when an external chip has crossed its limits. Usually, this is
89 connected to some LM75-like chip; if at least one crosses its limits, this
99 The SiS5595 only updates its values each 1.5 seconds; reading it more often
|
| D | max6642 | 17 The MAX6642 is a digital temperature sensor. It senses its own temperature as
|
| /linux-4.1.27/Documentation/usb/ |
| D | gadget_configfs.txt | 20 A gadget is seen by its host as a set of configurations, each of which contains
62 For each gadget to be created its corresponding directory must be created:
76 Each gadget needs to have its vendor id <VID> and product id <PID> specified:
81 A gadget also needs its serial number, manufacturer and product strings.
110 Each configuration also needs its strings, so a subdirectory must be created
126 The gadget will provide some functions, for each function its corresponding
140 Each function provides its specific set of attributes, with either read-only
348 a number of its default sub-groups created automatically.
355 1. A gadget has its config group, which has some attributes (idVendor,
375 4. Each USB function naturally has its own view of what it wants
|
| D | gadget-testing.txt | 34 The ACM function provides just one attribute in its function directory:
63 The ECM function provides these attributes in its function directory:
96 The ECM subset function provides these attributes in its function directory:
129 The EEM function provides these attributes in its function directory:
185 The HID function provides these attributes in its function directory:
231 The LOOPBACK function provides these attributes in its function directory:
251 The MASS STORAGE function provides these attributes in its directory:
304 The MIDI function provides these attributes in its function directory:
387 The NCM function provides these attributes in its function directory:
420 The OBEX function provides just one attribute in its function directory:
[all …]
|
| D | power-management.txt | 89 its usbfs file open, whether or not any I/O is going on.
91 If a USB device has no driver, its usbfs file isn't open, and it isn't
103 Of course, nothing the kernel does on its own initiative should
104 prevent the computer or its devices from working properly. If a
228 then each new USB device will have its autosuspend idle-delay
266 If a driver knows that its device has proper suspend/resume support,
297 methods in its usb_driver structure, and the reset_resume method is
313 since the device has probably lost most or all of its state
350 in its usb_driver structure. It is then responsible for informing the
351 USB core whenever one of its interfaces becomes busy or idle. The
[all …]
|
| /linux-4.1.27/drivers/char/xillybus/ |
| D | Kconfig | 12 its capabilities, and creates device files accordingly.
29 Set to M if you want Xillybus to find its resources from the
|
| /linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 109 - cooling-device: A phandle of a cooling device with its specifier,
133 for describing a thermal zone, including its cooling device bindings. The
134 thermal zone node must contain, apart from its own properties, one sub-node
205 * capable CPU. The CPU node describes its four OPPs.
297 used to monitor the zone 'cpu-thermal' using its sole sensor. A fan
300 the thermal zone 'cpu-thermal' using its cooling states
301 from its minimum to 4, when it reaches trip point 'cpu_alert0'
303 'cpu_alert1', but from 5 to its maximum state. The cpu@0 device is also
305 using all its cooling states at trip point 'cpu_alert1',
340 /* each zone within the SoC may have its own trips */
[all …]
|
| /linux-4.1.27/Documentation/i2c/ |
| D | summary | 19 use its protocols on many I2C systems. However, there are systems that don't
35 driver, or includes its own implementation.
38 code to access some type of device. Each detected device gets its own
|
| D | slave-interface | 39 Each backend should come with separate documentation to describe its specific
110 reset its state machine for I2C transfers to be able to receive new requests.
118 * use a standard i2c_driver and its matching mechanisms
135 on always to be able to detect its slave address. When unregistering, do the
|
| /linux-4.1.27/Documentation/ |
| D | kernel-per-CPU-kthreads.txt | 37 To reduce its OS jitter, do any of the following:
45 3. Rework the eHCA driver so that its per-CPU kthreads are
51 To reduce its OS jitter, do the following:
57 To reduce its OS jitter, do one of the following:
66 To reduce its OS jitter, each softirq vector must be handled
117 minimizing its chances of being selected to do the load balancing
147 2. Enable RCU to do its processing remotely via dyntick-idle by
162 To reduce its OS jitter, do any of the following:
175 to remove it, even if its addition was a mistake.
180 use of each CPU's workqueues to run its cache_reap()
[all …]
|
| D | remoteproc.txt | 12 is running its own instance of RTOS in an AMP configuration.
21 (for more information about the virtio-based rpmsg bus and its drivers,
32 - Boot a remote processor (i.e. load its firmware, power it on, ...).
104 only if there are no other references to rproc and its refcount now
127 After rproc_del() returns, @rproc is still valid, and its
186 When the firmware is parsed, its various segments are loaded to memory
234 * its @type. The content of the entry itself will immediately follow
246 the host should provide back its details (e.g. address of an allocated
259 * @RSC_VDEV: declare support for a virtio device, and serve as its
276 For more details regarding a specific resource type, please see its
[all …]
|
| D | rpmsg.txt | 17 its own instance of RTOS in an AMP configuration.
54 When a driver starts listening on a channel, its rx callback is bound with
66 and its length (in bytes). The message will be sent on the specified
67 channel, i.e. its source and destination address fields will be
82 its length (in bytes), and an explicit destination address.
100 its length (in bytes), and explicit source and destination addresses.
116 and its length (in bytes). The message will be sent on the specified
117 channel, i.e. its source and destination address fields will be
129 its length (in bytes), and an explicit destination address.
144 its length (in bytes), and explicit source and destination addresses.
[all …]
|
| D | init.txt | 32 you should make sure that the script specifies an interpreter in its shebang
33 header line (#!/...) that is fully working (including its library
35 non-script binary such as /bin/sh and confirm its successful execution.
|
| D | printk-formats.txt | 16 If <type> is dependent on a config option for its size (e.g., sector_t,
17 blkcnt_t) or is architecture-dependent for its size (e.g., tcflag_t), use a
18 format specifier of its largest possible type and explicitly cast to it.
78 For printing a phys_addr_t type (and its derivatives, such as
276 bitmap and its derivatives such as cpumask and nodemask:
281 For printing bitmap and its derivatives such as cpumask and nodemask,
|
| D | robust-futex-ABI.txt | 15 1) a one time call, per thread, to tell the kernel where its list of
43 its own thread private 'head'.
85 'lock entry' on this list, with its associated 'lock word' at the
109 By keeping its locks linked this way, on a list starting with a 'head'
131 When adding or removing a lock from its list of held locks, in order for
141 3) add the lock entry, with its thread id (TID) in the bottom 29 bits
|
| D | video-output.txt | 9 laptop, The ACPI video driver registered its output devices and read/write
|
| D | unshare.txt | 6 be used, its interface specification, design, implementation and
35 its simplicity but also from allowing application programmers to work
98 the benefits of this new feature can exceed its cost.
127 unshare allows a process to disassociate parts of its execution
135 The main use of unshare is to allow a process to control its
231 function. The first component was split into its own function.
|
| D | ldm.txt | 12 replacement for the MSDOS style partitions. It stores its information in a
78 As with all the partition code, if the driver doesn't see signs of its type of
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | freezer-subsystem.txt | 53 tasks beloning to the cgroup and all its descendant cgroups. Each
54 cgroup has its own state (self-state) and the state inherited from the
67 belonging to the cgroup and its descendants become frozen. Note that
69 to the cgroup or one of its descendant cgroups until the new task is
74 if not already freezing, enters FREEZING state along with all its
80 becomes THAWED, all its descendants which are freezing because of
|
| D | cpuacct.txt | 8 group accumulates the CPU usage of all of its child groups and the tasks
9 directly present in its group.
29 process (bash) into it. CPU time consumed by this bash and its children
|
| D | cpusets.txt | 54 include CPUs in its CPU affinity mask, and using the mbind(2) and
55 set_mempolicy(2) system calls to include Memory Nodes in its memory
58 schedule a task on a CPU that is not allowed in its cpus_allowed
142 - in fork and exit, to attach and detach a task from its cpuset.
187 command. The properties of a cpuset, such as its flags, allowed
207 - Its CPUs and Memory Nodes must be a subset of its parents.
208 - It can't be marked exclusive unless its parent is.
209 - If its cpu or memory is exclusive, they may not overlap any sibling.
238 isolating each job's user allocation in its own cpuset. To do this,
382 The algorithmic cost of load balancing and its impact on key shared
[all …]
|
| D | hugetlb.txt | 8 beyond its limit. This requires the application to know beforehand how much
9 HugeTLB pages it would require for its use.
|
| D | unified-hierarchy.txt | 47 controller on its own hierarchy. Only closely related ones, such as
111 is no longer referenced in its current hierarchy. Because per-cgroup
141 assume that resource control knobs of a child belong to its parent.
168 from the parent can be used in its children.
186 tasks belonging to the parent cgroup and its children cgroups. This
201 cgroup to host the tasks. The hidden leaf has its own copies of all
244 cgroup must create children and transfer all its tasks to the children
245 before enabling controllers in its "cgroup.subtree_control" file.
278 and its descendants; otherwise, 1. poll and [id]notify events are
334 implementation, despite its enormous size, does not even provide the
[all …]
|
| D | devices.txt | 16 never receive a device access which is denied by its parent.
55 access permissions than its parent. Every time an entry is written to
56 a cgroup's devices.deny file, all its children will have that entry removed
|
| D | cgroups.txt | 198 - in fork and exit, to attach and detach a task from its css_set.
249 command. The properties of a cgroup, such as its flags, are
271 a single cgroup on its cgrp_link_list field, and a list of
272 cg_cgroup_links for a single css_set on its cg_link_list.
302 flag is enabled (1) in a cgroup, a new cpuset cgroup will copy its
317 6) Attach that task to the new cgroup by writing its PID to the
448 mounted hierarchy, to remove a task from its current cgroup you must
461 rather than by its set of active subsystems. Each hierarchy is either
528 If a subsystem can be compiled as a module, it should also have in its
529 module initcall a call to cgroup_load_subsys(), and in its exitcall a
[all …]
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | automount-support.txt | 11 A filesystem can now mount another filesystem on one of its directories by the
37 vfsmount and its root dentry. The ref counts on these will need
78 If a vfsmount was already flagged for expiry, and if its usage count is 1
79 (it's only referenced by its parent vfsmount), then it will be deleted
108 umount() or its parent mountpoint, an EBUSY error will be returned and the
|
| D | ceph.txt | 26 utilize btrfs to store data objects, leveraging its advanced features
42 loaded into its cache with a single I/O operation. The contents of
54 a snapshot on any subdirectory (and its nested contents) in the
93 address its connection to the monitor originates from.
125 its cache. (This does not change correctness; the client uses
|
| D | ext3.txt | 33 identified through either its new major/minor numbers
44 system prior to its metadata being committed to the
48 into the main file system after its metadata has been
51 commit=nrsec (*) Ext3 can be told to sync all its data and metadata
167 a similar level of journaling as that of XFS, JFS, and ReiserFS in its default
181 written to the journal first, and then to its final location.
|
| D | path-lookup.txt | 9 path string. Then repeating the lookup from the child dentry and finding its
88 Parent and name members of a dentry, as well as its membership in the dcache
89 hash, and its inode are protected by the per-dentry d_lock spinlock. A
91 and this stabilises its d_inode pointer and actual inode. This gives a stable
106 However when a dentry is renamed, its hash value can change, requiring it to be
178 the dentry, stabilising it while comparing its name and parent and then
185 looks like (its name, parent, and inode). That snapshot is then used to start
268 | name: "a.c" | We now take its d_lock, verify d_seq of this
270 | children:NULL | its refcount because we're holding d_lock.
273 Taking a refcount on a dentry from rcu-walk mode, by taking its d_lock,
[all …]
|
| D | sysfs-tagging.txt | 29 will be differentiated from other sysfs mounts by having its
38 - call kobj_ns_type_register() with its kobj_ns_type_operations which has
|
| D | sharedsubtree.txt | 20 A process wants to clone its own namespace, but still wants to access the CD
152 A) A process wants to clone its own namespace, but still wants to
169 B) A process wants its mounts invisible to any other process, but
180 of its namespace as slave
200 requirements. Offcourse its needs support from PAM.
261 /mnt or /tmp reflect in all the other mounts of its peer
284 has its own peer group too. This vfsmount receives propagation
285 events from its master vfsmount, and also forwards propagation
286 events to its 'peer group' and to its slave vfsmounts.
288 Strictly speaking, the vfsmount is shared having its own
[all …]
|
| D | fiemap.txt | 41 flag is fatal to its operation. This scheme is intended to allow the
59 extended attribute lookup tree, instead of its data tree.
92 for an extents logical offset to start before the request or its logical
128 Delayed allocation - while there is data for this extent, its
162 Unwritten extent - the extent is allocated but its data has not been
179 defining its set of supported fiemap flags, and calling a helper function on
|
| D | ocfs2.txt | 59 system prior to its metadata being committed to the
62 into the main file system after its metadata has been
67 commit=nrsec (*) Ocfs2 can be told to sync all its data and metadata
|
| D | ncpfs.txt | 6 ftp.gwdg.de/pub/linux/misc/ncpfs, but sunsite and its many mirrors
|
| /linux-4.1.27/Documentation/devicetree/bindings/reset/ |
| D | sirf,rstc.txt | 31 For modules whose rest_bit is in SW_RST0, its RESET_INDEX is 0~31. For modules whose
32 rest_bit is in SW_RST1, its RESET_INDEX is 32~63.
|
| /linux-4.1.27/Documentation/RCU/ |
| D | UP.txt | 5 may immediately invoke its function. The basis of this misconception
23 Now, if call_rcu() were to directly invoke its arguments, then upon return
35 by having call_rcu() directly invoke its arguments only if it was called
45 its arguments would cause it to fail to make the fundamental guarantee
46 underlying RCU, namely that call_rcu() defers invoking its arguments until
84 Permitting call_rcu() to immediately invoke its arguments breaks RCU,
|
| /linux-4.1.27/Documentation/accounting/ |
| D | delay-accounting.txt | 21 important tasks could be a trigger for raising its corresponding priority.
23 The functionality, through its use of the taskstats interface, also provides
30 statistics of a task are available both during its lifetime as well as on its
|
| D | taskstats.txt | 10 - efficiently provide statistics during lifetime of a task and on its exit
36 one of the cpus in the cpumask, its per-pid statistics are sent to the
41 If the exiting task is the last thread exiting its thread group,
88 in cpus before closing the listening socket, the kernel cleans up its interest
143 to the version its using.
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | brcm,kona-ccu.txt | 68 its symbolic specifier (rather than its numeric index value) should
113 its symbolic specifier (rather than its numeric index value) should
|
| D | st,nomadik.txt | 16 board has its own circuitry for providing this oscillator
19 if the board has its own circuitry for providing this
|
| D | pxa-clock.txt | 8 ID in its "clocks" phandle cell (see include/.../pxa-clock.h).
|
| D | imx6sl-clock.txt | 9 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx6sl-clock.h
|
| D | efm32-clock.txt | 10 its "clocks" phandle cell. The header efm32-clk.h contains a list of available
|
| D | fujitsu,mb86s70-crg11.txt | 8 The consumer specifies the desired clock pointing to its phandle.
|
| D | clps711x-clock.txt | 10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/clps711x-clock.h
|
| D | imx6sx-clock.txt | 12 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx6sx-clock.h
|
| D | lsi,axm5516-clks.txt | 9 The consumer specifies the desired clock by having the clock ID in its "clocks"
|
| D | qoriq-clock.txt | 37 address space defined by its parent bus, and resource zero
63 It takes parent's clock-frequency as its clock.
65 It takes parent's clock-frequency as its clock.
|
| D | imx27-clock.txt | 10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx27-clock.h
|
| D | imx1-clock.txt | 9 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx1-clock.h
|
| D | imx21-clock.txt | 10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx21-clock.h
|
| D | imx5-clock.txt | 10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx5-clock.h
|
| D | arm-integrator.txt | 10 it obtains the base address for it's address range from its
|
| D | imx6q-clock.txt | 10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx6qdl-clock.h
|
| D | imx23-clock.txt | 9 ID in its "clocks" phandle cell. The following is a full list of i.MX23
|
| D | prima2-clock.txt | 10 ID in its "clocks" phandle cell. The following is a full list of prima2
|
| D | imx31-clock.txt | 10 ID in its "clocks" phandle cell. The following is a full list of i.MX31
|
| D | imx28-clock.txt | 9 ID in its "clocks" phandle cell. The following is a full list of i.MX28
|
| D | vf610-clock.txt | 22 ID in its "clocks" phandle cell. See include/dt-bindings/clock/vf610-clock.h
|
| /linux-4.1.27/Documentation/PCI/ |
| D | PCIEBUS-HOWTO.txt | 19 internal logical PCI buses. The Switch Port, which has its secondary
26 referred to in this document as services, depending on its port type.
39 may have its own software service driver. In this case several
85 register its service with the PCI Express Port Bus driver (see
181 switch interrupt mode on its device. The PCI Express Port Bus driver
194 are not permitted to switch interrupt mode on its device. The PCI
212 Each service driver runs its PCI config operations on its own
|
| D | pci-iov-howto.txt | 20 turned on, each VF's PCI configuration space can be accessed by its own
22 Memory Space, which is used to map its register set. VF device driver
33 If the hardware has SR-IOV capability, loading its PF driver would
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | cs4271.txt | 24 The CS4271 requires its LRCLK and MCLK to be stable before its RESET
|
| D | wm8962.txt | 22 Any other value is regarded as setting the GPIO register by its reset
|
| D | samsung,odroidx2-max98090.txt | 13 documented in its binding), and the jacks on the board
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | nested-vmx.txt | 18 its implementation and its performance characteristics, in the OSDI 2010 paper
30 L0, the guest hypervisor, which we call L1, and its nested guest, which we
73 this structure is *opaque* to its user, who is not supposed to know or care
74 about its internal structure. Rather, the structure is accessed through the
86 VMCS12_REVISION (from vmx.c) should be changed if struct vmcs12 or its inner
|
| /linux-4.1.27/Documentation/devicetree/bindings/staging/iio/adc/ |
| D | mxs-lradc.txt | 18 2 kHz and its default is 2 (= 1 ms)
20 1 ... 2047. It counts at 2 kHz and its default is
|
| /linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
| D | tmio_mmc.txt | 3 The tmio-mmc driver doesn't probe its devices actively, instead its binding to
|
| /linux-4.1.27/Documentation/prctl/ |
| D | no_new_privs.txt | 2 its parent did not have. The most obvious examples are setuid/setgid
18 new, generic mechanism to make it safe for a process to modify its
49 escalate its privileges by directly attacking setuid, setgid, and
|
| /linux-4.1.27/Documentation/security/ |
| D | credentials.txt | 85 A subject has an additional interpretation of its credentials. A subset
86 of its credentials forms the 'subjective context'. The subjective context
116 Sometimes the object will include sets of rules as part of its
137 of its credentials. When an action is requested, they take the
181 itself to its effective or permitted sets through capset(). This
279 Each task points to its credentials by a pointer called 'cred' in its
285 (1) its reference count may be changed;
305 A task may only alter its _own_ credentials; it is no longer permitted for a
325 has _const_ pointers to its credential sets, as does struct file. Furthermore,
334 A task being able to alter only its own credentials permits the current process
[all …]
|
| D | LSM.txt | 26 a new LSM is accepted into the kernel when its intent (a description of
29 This allows an LSM's code to be easily compared to its goals, and so
|
| D | Yama.txt | 38 between a debugging process and its inferior (crash handlers, etc),
40 other process (and its descendants) are allowed to call PTRACE_ATTACH
59 this relationship is that of only its descendants when the above
|
| D | IMA-templates.txt | 72 - "ima": its format is 'd|n';
73 - "ima-ng" (default): its format is 'd-ng|n-ng';
74 - "ima-sig": its format is 'd-ng|n-ng|sig'.
|
| /linux-4.1.27/Documentation/networking/ |
| D | batman-adv.txt | 46 To activate a given interface simply write "bat0" into its
54 By reading the "iface_status" file you can check its status:
59 To deactivate an interface you have to write "none" into its
90 sends its broadcast packets):
95 and also change its value:
112 sure it reaches its destination.
|
| D | ipvs-sysctl.txt | 131 packets when its destination server is not available. It may
138 connection immediately when a packet arrives and its
142 connections when its destination is not available.
151 quiescent by setting its weight to 0 and it is desired that
184 synchronized, every time the number of its incoming packets
|
| D | regulatory.txt | 66 as its integration is added.
81 registering on its struct wiphy a reg_notifier() callback. This notifier
84 (driver, user, country IE) and determine what to allow based on its
87 added to this document when its support is enabled.
|
| /linux-4.1.27/fs/kernfs/ |
| D | Kconfig | 2 # KERNFS should be selected by its users
|
| /linux-4.1.27/Documentation/fmc/ |
| D | fmc-fakedev.txt | 7 it manages, this module creates a single instance of its set of
33 After loading the device, you can use the write_ee method do modify its
|
| D | fmc-chardev.txt | 27 The example below shows raw access to a SPEC card programmed with its
55 SDB record from a SPEC device programmed with its golden image:
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/ |
| D | s5p-mfc.txt | 25 for DMA contiguous memory allocation and its size.
28 for DMA contiguous memory allocation and its size.
|
| /linux-4.1.27/Documentation/gpio/ |
| D | board.txt | 14 describe its hardware layout. Currently, mappings can be defined through device
123 A lookup table can then be defined as follows, with an empty entry defining its
141 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows:
152 Since the "power" GPIO is mapped as active-low, its actual signal will be 0
|
| D | driver.txt | 41 gpio_chip" (see linux/gpio/driver.h for its complete definition) with members
47 - flag saying whether calls to its methods may sleep
86 something like this sequence in its interrupt handler:
103 this in its interrupt handler:
120 need to embed the gpio_chip in its state container and obtain a pointer
176 Sometimes it is useful to allow a GPIO chip driver to request its own GPIO
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-bwc.txt | 13 group exceeds this limit (for that period), the tasks belonging to its
83 [ Where C is the parent's bandwidth, and c_i its children ]
87 a. it fully consumes its own quota within a period
88 b. a parent's quota is fully consumed within its period
|
| D | sched-domains.txt | 25 load of each of its member CPUs, and only when the load of a group becomes
36 our CPU is on, starting from its base domain and going up the ->parent chain.
37 While doing that, it checks to see if the current domain has exhausted its
58 might have just one domain covering its one NUMA level.
|
| D | sched-design-CFS.txt | 23 specifies when its next timeslice would start execution on the ideal
25 is its actual runtime normalized to the total number of running tasks.
99 Due to its design, the CFS scheduler is not prone to any of the "attacks" that
127 - SCHED_IDLE: This is even weaker than nice 19, but its not a true
188 This function is called when a task changes its scheduling class or changes
189 its task group.
|
| D | sched-deadline.txt | 56 that each task runs for at most its runtime every period, avoiding any
89 - When a SCHED_DEADLINE task executes for an amount of time t, its
99 and cannot be scheduled until its scheduling deadline. The "replenishment
140 The utilisation of a real-time task is defined as the ratio between its
141 WCET and its period (or minimum inter-arrival time), and represents
158 between the finishing time of a job and its absolute deadline).
198 this task, as it is not possible to respect its temporal constraints.
275 its own timing constraints needs, in general, a way of declaring:
398 application, given that you know its pid:
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | governors.txt | 146 to its default value of '95' it means that between the checking
151 set to '0' (its default), all processes are counted towards the
164 scheduling interval for reevaluating load when the CPU is at its top
166 of load evaluation and helping the CPU stay at its top speed when truly
207 CPU at a speed regardless of its load whilst '100' will, in theory, make
211 governor but for the opposite direction. For example when set to its
237 CPUFREQ_GOV_START: This governor shall start its duty for the CPU
239 CPUFREQ_GOV_STOP: This governor shall end its duty for the CPU
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio-poweroff.txt | 7 state. Otherwise its configured as an input.
28 property is not specified, the GPIO is initialized as an output in its
|
| D | gpio-restart.txt | 7 will be driven in the inactive state. Otherwise its not driven until
30 specified, the GPIO is initialized as an output in its inactive state.
|
| D | abilis,tb10x-gpio.txt | 16 its parent interrupt controller.
|
| /linux-4.1.27/drivers/net/wireless/hostap/ |
| D | Kconfig | 68 driver and its help text includes more information about the Host AP
81 driver and its help text includes more information about the Host AP
94 driver and its help text includes more information about the Host AP
|
| /linux-4.1.27/drivers/video/backlight/ |
| D | Kconfig | 102 for its LCD.
117 If you have an S6E63M0 LCD Panel, say Y to enable its
125 If you have an LD9040 Panel, say Y to enable its
133 If you have an AMS369FG06 AMOLED Panel, say Y to enable its
141 If you have an LMS501KF03 LCD Panel, say Y to enable its
148 If you have a HX-8357 LCD panel, say Y to enable its LCD control
290 If you have an Intel-based Apple say Y to enable a driver for its
298 for its backlight
359 enable its driver.
|
| /linux-4.1.27/drivers/fmc/ |
| D | Kconfig | 40 its binary and the function carrier->reprogram to actually do it.
49 acquainted with a mezzanine before writing its specific driver.
|
| /linux-4.1.27/fs/reiserfs/ |
| D | Kconfig | 35 possibly imagine of its internal consistency throughout its
39 out in checking for consistency when debugging without fear of its
|
| /linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
| D | regulator.txt | 62 Consumer nodes can reference one or more of its supplies/
68 example used to reference its own supply, in which case
69 its just seen as a special case of a regulator being a
|
| /linux-4.1.27/Documentation/connector/ |
| D | connector.txt | 98 netlink group to the user which is equal to its id.idx.
118 If we receive a message and its sequence number is not equal to one we
120 its sequence number is the same as one we are expecting, but its
128 selected ids will be turned on or off (registered or unregistered its
|
| /linux-4.1.27/arch/arc/include/asm/ |
| D | tlb-mmu1.h | 25 ; and its unpleasant LFSR pseudo-random sequence
|
| /linux-4.1.27/drivers/input/gameport/ |
| D | Kconfig | 47 Audigy card and want to use its gameport.
58 and others), and want to use its gameport.
|
| /linux-4.1.27/drivers/lguest/ |
| D | README | 19 taste of its scope. Suitable for the armchair coders and other such
27 - Whereby the Guest finds its voice and become useful, and our
|
| /linux-4.1.27/fs/exofs/ |
| D | Kconfig | 6 as its backing storage.
|
| /linux-4.1.27/Documentation/vm/ |
| D | zswap.txt | 26 device when the compressed pool reaches its size limit. This requirement had
35 evict pages from its own compressed pool on an LRU basis and write them back to
58 Zswap seeks to be simple in its policies. Sysfs attributes allow for one user
|
| D | zsmalloc.txt | 10 This was one of the major issues with its predecessor (xvmalloc).
19 since this satisfies the requirements of all its current users (in the
|
| D | ksm.txt | 5 added to the Linux kernel in 2.6.32. See mm/ksm.c for its implementation,
11 copied if a process later wants to update its content).
47 restricting its use to areas likely to benefit. KSM's scans may use a lot
|
| /linux-4.1.27/drivers/staging/media/davinci_vpfe/ |
| D | davinci-vpfe-mc.txt | 68 accepts a pointer to struct vpfe_isif_raw_config as its argument. Similarly
70 VIDIOC_VPFE_RSZ_S_CONFIG accepts a pointer to struct vpfe_rsz_config as its
93 as its argument.
|
| /linux-4.1.27/Documentation/infiniband/ |
| D | core_locking.txt | 71 handler directly from its post_send method. Instead, the low-level
110 soon as the add method of its struct ib_client is called for that
114 A consumer is permitted to sleep in its add and remove methods.
|
| /linux-4.1.27/Documentation/power/regulator/ |
| D | overview.txt | 38 Static: consumer does not change its supply voltage or
39 current limit. It only needs to enable or disable its
43 Dynamic: consumer needs to change its supply voltage or
47 o Power Domain - Electronic circuit that is supplied its input power by the
|
| D | consumer.txt | 11 A consumer driver can get access to its supply regulator by calling :-
15 The consumer passes in its struct device pointer and power supply ID. The core
37 A consumer can enable its power supply by calling:-
52 A consumer can disable its supply when no longer needed by calling :-
143 on all its consumers) and change operating mode (if necessary and permitted)
|
| /linux-4.1.27/Documentation/scsi/ |
| D | FlashPoint.txt | 12 operating system support to its BusLogic brand of FlashPoint Ultra SCSI
46 and system boards. Through its wide range of RAID controllers and its
72 Ever since its introduction last October, the BusLogic FlashPoint LT has
74 drivers have been available for this new Ultra SCSI product. Despite its
85 After this problem was identified, BusLogic contacted its major OEM
|
| D | osd.txt | 20 as its back-end data storage. Other clients are the other osd parts listed below.
75 its state throughout execution. Each request goes through these stages:
92 layer and wait for its completion. The request can be executed
166 For us, a scatter-gather-list, as its name implies and as used by the Networking
|
| D | lpfc.txt | 35 jitter, or a device temporarily loses connectivity (due to its cable
41 errored by the driver, the mid-layer would exhaust its retries, and the
|
| /linux-4.1.27/Documentation/acpi/ |
| D | namespace.txt | 28 Description Table) using its first entry, the data within the FADT
241 column), so its sysfs directory will not contain the 'path'
247 its namespace path will be present in its sysfs directory. For
286 (2) to do specific things to the device with the help of its ACPI
290 If an ACPI device object is linked to a "physical" device, its sysfs
305 The linking mechanism is generally bus-specific. The core of its
|
| /linux-4.1.27/drivers/usb/serial/ |
| D | Makefile-keyspan_pda_fw | 4 # and its lack of preprocessor support
|
| /linux-4.1.27/drivers/media/platform/blackfin/ |
| D | Kconfig | 8 Choose PPI or EPPI as its interface.
|
| /linux-4.1.27/drivers/staging/iio/Documentation/ |
| D | inkernel.txt | 31 The driver must provide datasheet_name values for its channels and
32 must pass the iio_map structures and a pointer to its own iio_dev structure
|
| /linux-4.1.27/Documentation/devicetree/bindings/crypto/ |
| D | mv_cesa.txt | 6 region, followed by base physical address of sram and its memory
|
| /linux-4.1.27/drivers/staging/dgnc/ |
| D | TODO | 3 * remove unecessary error messages. Example kzalloc() has its
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/firmware/ |
| D | tlm,trusted-foundations.txt | 4 Boards that use the Trusted Foundations secure monitor can signal its
|
| /linux-4.1.27/Documentation/frv/ |
| D | booting.txt | 82 The kernel command line <CMDLINE> tells the kernel where its console is and
83 how to find its root filesystem. This is made up of the following components,
149 kernel the IP address of the NFS server providing its root filesystem,
170 simply dumps it to its standard output.
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | ti-keystone-devctrl.txt | 4 the status of its peripherals. This node is intended to allow access to
|
| D | palmas.txt | 23 - interrupt-controller : palmas has its own internal IRQs
|
| /linux-4.1.27/tools/perf/util/ |
| D | python-ext-sources | 4 # Each source file must be placed on its own line so that it can be
|
| /linux-4.1.27/Documentation/devicetree/bindings/iio/light/ |
| D | gp2ap020a00f.txt | 4 for its built-in led. It is also defined by this binding.
|
| /linux-4.1.27/Documentation/arm/SA1100/ |
| D | Victor | 8 Of course Victor is using Linux as its main operating system.
|
| /linux-4.1.27/fs/logfs/ |
| D | Kconfig | 14 In its current state it is still very experimental and should
|
| /linux-4.1.27/Documentation/devicetree/bindings/hwmon/ |
| D | ibmpowernv.txt | 11 given sensor and its attribute data
|
| /linux-4.1.27/net/phonet/ |
| D | Kconfig | 9 communication protocol developed by Nokia for use with its modems.
|
| /linux-4.1.27/drivers/video/fbdev/exynos/ |
| D | Kconfig | 29 If you have an S6E8AX0 MIPI AMOLED LCD Panel, say Y to enable its
|
| /linux-4.1.27/Documentation/devicetree/bindings/phy/ |
| D | qcom-ipq806x-sata-phy.txt | 5 Each SATA PHY controller should have its own node.
|
| D | qcom-apq8064-sata-phy.txt | 5 Each SATA PHY controller should have its own node.
|
| D | samsung-phy.txt | 10 the PHY specifier identifies the PHY and its meaning is as follows:
47 The first phandle argument in the PHY specifier identifies the PHY, its
88 Each SATA PHY controller should have its own node.
|
| D | qcom-dwc3-usb-phy.txt | 5 controllers. Each DWC3 PHY controller should have its own node.
|
| /linux-4.1.27/Documentation/devicetree/bindings/power_supply/ |
| D | sbs_sbs-battery.txt | 13 a flag specifying its polarity.
|
| /linux-4.1.27/fs/omfs/ |
| D | Kconfig | 10 and wish to mount its disk.
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | DAI.txt | 10 multiplexes its data on its SDATA_OUT (playback) and SDATA_IN (capture) lines.
|
| /linux-4.1.27/net/netfilter/ipvs/ |
| D | Kconfig | 20 information and its administration program, please visit the
171 its server if the server is alive and under load. If the server is
172 overloaded (its active connection numbers is larger than its weight)
173 and there is a server in its half load, then allocate the weighted
237 that minimize its expected delay (The Shortest Expected Delay
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 7.AdvancedTopics | 17 as its tool of choice.
20 especially as the volume of those patches grows. Git also has its rough
22 still being civilized by its developers. This document will not attempt to
24 long document in its own right. Instead, the focus here will be on how git
39 rewriting of history (such as rebase) is also useful. Git comes with its
133 authorship information; the git "am" tool does its best in this regard, but
|
| /linux-4.1.27/include/net/netfilter/ |
| D | nf_conntrack_synproxy.h | 8 u32 its; member
|
| /linux-4.1.27/fs/cramfs/ |
| D | README | 27 a directory's entries before recursing down its subdirectories: the
97 for blksize, whereas Linux-2.3.39 uses its PAGE_CACHE_SIZE, which in
102 One option is to change mkcramfs to take its PAGE_CACHE_SIZE from
166 its current 12 bytes. Inodes other than the root inode are followed
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 72 for its configuration. Obviously, there will be a nice program that
107 and its attributes, allowing the subsystem to ignore all but the
230 that item means that a group can behave as an item in its own right.
249 config_item (or more likely, its container structure), initializes it,
274 down. It no longer has a reference on its parent and has no place in
279 item is removed from its parent group. Like drop_item(),
350 be in its parent's cg_children list for the same duration. This allows
371 in its own subsystem).
390 automatically created inside the parent at its creation. Thus,
428 probably shouldn't calling them of its own gumption. Rather it should
[all …]
|
| /linux-4.1.27/drivers/clk/versatile/ |
| D | Kconfig | 25 Express platforms hidden behind its configuration infrastructure,
|
| /linux-4.1.27/fs/efs/ |
| D | Kconfig | 11 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
|
| /linux-4.1.27/Documentation/devicetree/bindings/ata/ |
| D | fsl-sata.txt | 4 Each SATA port should have its own node.
|
| D | exynos-sata.txt | 4 Each SATA controller should have its own node.
|
| /linux-4.1.27/Documentation/devicetree/bindings/power/ |
| D | power-controller.txt | 7 standard property "system-power-controller" in its device node. This property
|
| /linux-4.1.27/drivers/hid/usbhid/ |
| D | Kconfig | 56 to use the keyboard in its limited Boot Protocol mode instead.
72 to use the mouse in its limited Boot Protocol mode instead.
|
| /linux-4.1.27/Documentation/block/ |
| D | cfq-iosched.txt | 154 whole is entitled to at its parent's level while the latter two
156 its direct children.
171 root never has a parent making its weight is meaningless. For backward
173 and AB have no child and thus its tasks have no children cgroup to
196 A has children and further distributes its 57% among the children and
273 and notice how a workload can lose its disk share and suffer due to
278 data comes in only after fsync has finished its IO (atleast for ext4
|
| /linux-4.1.27/drivers/power/avs/ |
| D | Kconfig | 6 its power consumption.
|
| /linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
| D | NAND.txt | 12 code, so the driver enforces its own OOB layout and ECC parameters
|
| /linux-4.1.27/scripts/coccinelle/misc/ |
| D | cstptr.cocci | 1 /// PTR_ERR should be applied before its argument is reassigned, typically
|
| /linux-4.1.27/Documentation/leds/ |
| D | ledtrig-transient.txt | 51 as its default trigger, trigger activation routine will get called. During
58 creates its properties and does its initialization. Transient trigger
109 default states it defines for the LED in its brightness_set()
|
| /linux-4.1.27/Documentation/serial/ |
| D | n_gsm.txt | 14 its serial port. Depending on the modem used, you can pass more or less
64 each modem has its configuration and some DLC have dedicated functions,
|
| /linux-4.1.27/block/partitions/ |
| D | Kconfig | 128 FreeBSD uses its own hard disk partition scheme on your PC. It
130 and manages it similarly to DOS extended partitions, putting in its
149 Like most systems, Solaris x86 uses its own hard disk partition
159 Like some systems, UnixWare uses its own slice table inside a
229 Like most systems, SunOS uses its own hard disk partition table
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | PSS-updates | 22 This parameter takes a port address as its parameter. Any available port
57 all emulations whenever its unloaded. This can be useful for those who are
82 # System using the PSS sound card just for its CDROM and joystick ports.
|
| /linux-4.1.27/Documentation/input/ |
| D | yealink.txt | 130 Reading /sys/../lineX will return the format string with its current value:
142 - Writing a space to an icon will always hide its content.
152 Reading will return all available icon names and its current settings:
|
| /linux-4.1.27/Documentation/pcmcia/ |
| D | driver.txt | 21 PCMCIA device listed in its (newly updated) pcmcia_device_id list.
|
| /linux-4.1.27/Documentation/dvb/ |
| D | contributors.txt | 4 for the initial saa7146 driver and its recent overhaul
18 (in case you are wondering where CyberLogin is, EON changed its login
|
| /linux-4.1.27/Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 8 CRYPTO Engines etc has its own instance of dma hardware. QMSS has also
38 its components.
|
| /linux-4.1.27/Documentation/ABI/obsolete/ |
| D | sysfs-class-rfkill | 11 because its not possible to express the 'soft and hard block'
|
| /linux-4.1.27/Documentation/devicetree/bindings/spi/ |
| D | efm32-spi.txt | 17 already configured in the hardware, so its either the
|
| /linux-4.1.27/scripts/coccinelle/api/ |
| D | memdup_user.cocci | 1 /// Use memdup_user rather than duplicating its implementation
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/i2c/ |
| D | ov2640.txt | 16 The device node must contain one 'port' child node for its digital output
|
| /linux-4.1.27/arch/x86/boot/ |
| D | pmjump.S | 58 # The 32-bit code sets up its own stack, but this way we do have
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | nbd.txt | 8 can use a remote server as one of its block devices. So every time
|
| /linux-4.1.27/fs/sysfs/ |
| D | Kconfig | 21 the kernel boot command line via its major and minor numbers. For
|
| /linux-4.1.27/drivers/staging/lustre/lnet/ |
| D | Kconfig | 11 can put into its transport.
|
| /linux-4.1.27/drivers/staging/android/ion/ |
| D | Kconfig | 10 If you're not using Android its probably safe to
|