Home
last modified time | relevance | path

Searched refs:its (Results 1 – 200 of 1338) sorted by relevance

1234567

/linux-4.4.14/arch/um/os-Linux/
Dtime.c62 struct itimerspec its; in os_timer_set_interval() local
74 its.it_value.tv_sec = its_in->it_value.tv_sec; in os_timer_set_interval()
75 its.it_value.tv_nsec = its_in->it_value.tv_nsec; in os_timer_set_interval()
77 its.it_value.tv_sec = 0; in os_timer_set_interval()
78 its.it_value.tv_nsec = nsec; in os_timer_set_interval()
81 its.it_interval.tv_sec = 0; in os_timer_set_interval()
82 its.it_interval.tv_nsec = nsec; in os_timer_set_interval()
84 if(timer_settime(*t, 0, &its, NULL) == -1) { in os_timer_set_interval()
102 struct itimerspec its; in os_timer_remain() local
109 if(timer_gettime(t, &its) == -1) { in os_timer_remain()
[all …]
/linux-4.4.14/drivers/irqchip/
Dirq-gic-v3-its.c91 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 …]
DMakefile26 obj-$(CONFIG_ARM_GIC_V3_ITS) += irq-gic-v3-its.o irq-gic-v3-its-pci-msi.o irq-gic-v3-its-platform-…
/linux-4.4.14/include/linux/
Dtime64.h60 static inline struct itimerspec64 itimerspec_to_itimerspec64(struct itimerspec *its) in itimerspec_to_itimerspec64() argument
62 return *its; in itimerspec_to_itimerspec64()
106 static inline struct itimerspec64 itimerspec_to_itimerspec64(struct itimerspec *its) in itimerspec_to_itimerspec64() argument
110 ret.it_interval = timespec_to_timespec64(its->it_interval); in itimerspec_to_itimerspec64()
111 ret.it_value = timespec_to_timespec64(its->it_value); in itimerspec_to_itimerspec64()
/linux-4.4.14/arch/arm/mach-imx/
DKconfig145 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.4.14/Documentation/devicetree/bindings/interrupt-controller/
Darm,gic-v3.txt58 - compatible : Should at least contain "arm,gic-v3-its".
85 gic-its@2c200000 {
86 compatible = "arm,gic-v3-its";
110 gic-its@2c200000 {
111 compatible = "arm,gic-v3-its";
117 gic-its@2c400000 {
118 compatible = "arm,gic-v3-its";
/linux-4.4.14/Documentation/devicetree/bindings/iommu/
Drockchip,iommu.txt5 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:
Dsamsung,sysmmu.txt21 * 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.4.14/Documentation/ABI/testing/
Dsysfs-devices-online11 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
Dconfigfs-spear-pcie-gadget8 as device and then program its various registers to configure it
18 link ... used to enable ltssm and read its status.
Dsysfs-bus-usb-devices-usbsevseg23 Description: Controls the way the device interprets its text buffer.
24 raw: each character controls its segment manually
Dconfigfs-stp-policy13 This group is the root of a policy; its name is a concatenation
24 <device> component of its parent directory.
Dsysfs-driver-xen-blkfront10 and its default backend value.
Dsysfs-class-leds-gt683r7 of one LED will update the mode of its two sibling devices as
Ddebugfs-ideapad17 status shows infos we can read and tells its meaning and value.
Dsysfs-class-stm_source6 stm_source device linkage to stm device, where its tracing data
Dsysfs-driver-st11 appear in sysfs as its presence is conditional upon debug
Dsysfs-platform-dell-laptop33 To enable a trigger, write its name preceded by '+' to
34 this file. To disable a trigger, write its name preceded
Dsysfs-class-mic.txt68 An Intel MIC device runs a Linux OS during its operation. This
84 An Intel MIC device runs a Linux OS during its operation. Before
131 An Intel MIC device runs a Linux OS during its operation. For
145 An Intel MIC device runs a Linux OS during its operation. For
Dsysfs-class-zram15 device and return its device id back to user (so one can
Dsysfs-wusb_cbaf28 6. The CM looks it up its database.
35 matching CDID in its database), the device is
Dsysfs-class-mei23 The ME FW writes its status information into fw status
Dsysfs-bus-iio-frequency-adf435021 down the PLL and its RFOut buffers during REFin changes.
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
Dpar_io.txt11 - 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.4.14/Documentation/filesystems/nfs/
Dfault_injection.txt8 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.4.14/Documentation/power/
Druntime_pm.txt102 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.4.14/Documentation/filesystems/caching/
Dobject.txt96 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.4.14/Documentation/ABI/removed/
Draw13946 access to FireWire buses. Its major drawbacks were its inability
7 to implement sensible device security policies, and its low level
Dvideo13948 performance issues in its first generation. Any video1394 user had
/linux-4.4.14/Documentation/hwmon/
Dlm9524522 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.
Dlm9523423 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.
Dmax161918 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
Dabx50025 specific abx500 chip has its special configurations in its own file, e.g. some
Dadm103131 Each temperature channel has its own high and low limits, plus a critical
35 two. Each fan channel has its own low speed limit.
Dlm7725 the limit and its hysteresis is always the same for all 3 limits.
28 * When setting a limit, its hysteresis will automatically follow, the
Dlm8321 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
Demc140345 difference between the limit and its hysteresis is always the same for
49 * When setting a limit, its hysteresis will automatically follow, the
Dsis559588 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
Dmax664217 The MAX6642 is a digital temperature sensor. It senses its own temperature as
/linux-4.4.14/Documentation/usb/
Dgadget_configfs.txt20 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
Dgadget-testing.txt34 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 …]
Dpower-management.txt89 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.4.14/drivers/char/xillybus/
DKconfig12 its capabilities, and creates device files accordingly.
29 Set to M if you want Xillybus to find its resources from the
/linux-4.4.14/Documentation/devicetree/bindings/thermal/
Dthermal.txt110 - cooling-device: A phandle of a cooling device with its specifier,
134 for describing a thermal zone, including its cooling device bindings. The
135 thermal zone node must contain, apart from its own properties, one sub-node
213 * capable CPU. The CPU node describes its four OPPs.
305 used to monitor the zone 'cpu-thermal' using its sole sensor. A fan
308 the thermal zone 'cpu-thermal' using its cooling states
309 from its minimum to 4, when it reaches trip point 'cpu_alert0'
311 'cpu_alert1', but from 5 to its maximum state. The cpu@0 device is also
313 using all its cooling states at trip point 'cpu_alert1',
348 /* each zone within the SoC may have its own trips */
[all …]
/linux-4.4.14/Documentation/filesystems/
Dsysfs-tagging.txt21 void *ns member of its kernfs_node. If a directory entry is tagged,
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
Dceph.txt26 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
Dpath-lookup.txt9 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 …]
Dsharedsubtree.txt20 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 …]
Dautomount-support.txt53 If a vfsmount was already flagged for expiry, and if its usage count is 1
54 (it's only referenced by its parent vfsmount), then it will be deleted
83 umount() or its parent mountpoint, an EBUSY error will be returned and the
Dfiemap.txt41 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
Docfs2.txt59 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
Dncpfs.txt6 ftp.gwdg.de/pub/linux/misc/ncpfs, but sunsite and its many mirrors
/linux-4.4.14/Documentation/i2c/
Dsummary19 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
Dslave-interface42 Each backend should come with separate documentation to describe its specific
118 reset its state machine for I2C transfers to be able to receive new requests.
126 * use a standard i2c_driver and its matching mechanisms
143 on always to be able to detect its slave address. When unregistering, do the
/linux-4.4.14/Documentation/
Dkernel-per-CPU-kthreads.txt37 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 …]
Dremoteproc.txt12 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, ...).
110 only if there are no other references to rproc and its refcount now
133 After rproc_del() returns, @rproc is still valid, and its
192 When the firmware is parsed, its various segments are loaded to memory
240 * its @type. The content of the entry itself will immediately follow
252 the host should provide back its details (e.g. address of an allocated
265 * @RSC_VDEV: declare support for a virtio device, and serve as its
282 For more details regarding a specific resource type, please see its
[all …]
Drpmsg.txt17 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 …]
Dinit.txt32 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.
Dprintk-formats.txt16 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.
82 For printing a phys_addr_t type (and its derivatives, such as
284 bitmap and its derivatives such as cpumask and nodemask:
289 For printing bitmap and its derivatives such as cpumask and nodemask,
Drobust-futex-ABI.txt15 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
Dvideo-output.txt9 laptop, The ACPI video driver registered its output devices and read/write
/linux-4.4.14/Documentation/cgroups/
Dfreezer-subsystem.txt53 tasks belonging 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
Dcpuacct.txt8 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
Dcpusets.txt54 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 …]
Dhugetlb.txt8 beyond its limit. This requires the application to know beforehand how much
9 HugeTLB pages it would require for its use.
Dunified-hierarchy.txt53 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.
253 access of the directory and its "cgroup.procs" file to the user. Note
295 "cgroup.procs" file of a cgroup and its uid agrees with the target, it
[all …]
Ddevices.txt16 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
Dcgroups.txt198 - 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.4.14/Documentation/devicetree/bindings/clock/
Dcsr,atlas7-car.txt10 ID in its "clocks" phandle cell.
14 ID in its "reset" phandle cell.
Dbrcm,kona-ccu.txt68 its symbolic specifier (rather than its numeric index value) should
113 its symbolic specifier (rather than its numeric index value) should
Dst,nomadik.txt16 board has its own circuitry for providing this oscillator
19 if the board has its own circuitry for providing this
Dpxa-clock.txt8 ID in its "clocks" phandle cell (see include/.../pxa-clock.h).
Dimx6sl-clock.txt9 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx6sl-clock.h
Dfujitsu,mb86s70-crg11.txt8 The consumer specifies the desired clock pointing to its phandle.
Defm32-clock.txt10 its "clocks" phandle cell. The header efm32-clk.h contains a list of available
Dclps711x-clock.txt10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/clps711x-clock.h
Dimx7d-clock.txt12 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx7d-clock.h
Dimx6ul-clock.txt12 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx6ul-clock.h
Dlsi,axm5516-clks.txt9 The consumer specifies the desired clock by having the clock ID in its "clocks"
Dimx6sx-clock.txt12 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx6sx-clock.h
Dimx1-clock.txt9 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx1-clock.h
Dimx27-clock.txt10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx27-clock.h
Dimx21-clock.txt10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx21-clock.h
Dimx5-clock.txt10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx5-clock.h
Dimx6q-clock.txt10 ID in its "clocks" phandle cell. See include/dt-bindings/clock/imx6qdl-clock.h
Darm-integrator.txt10 it obtains the base address for it's address range from its
Dimx23-clock.txt9 ID in its "clocks" phandle cell. The following is a full list of i.MX23
Dzx296702-clk.txt19 ID in its "clocks" phandle cell. See include/dt-bindings/clock/zx296702-clock.h
Dprima2-clock.txt10 ID in its "clocks" phandle cell. The following is a full list of prima2
Dqoriq-clock.txt39 address space defined by its parent bus, and resource zero
102 It takes parent's clock-frequency as its clock.
104 It takes parent's clock-frequency as its clock.
/linux-4.4.14/Documentation/devicetree/bindings/reset/
Dsirf,rstc.txt31 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.4.14/Documentation/RCU/
DUP.txt5 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.4.14/Documentation/accounting/
Ddelay-accounting.txt21 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
Dtaskstats.txt10 - 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.4.14/Documentation/PCI/
DPCIEBUS-HOWTO.txt19 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
Dpci-iov-howto.txt20 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.4.14/Documentation/devicetree/bindings/sound/
Dcs4271.txt24 The CS4271 requires its LRCLK and MCLK to be stable before its RESET
Dwm8962.txt22 Any other value is regarded as setting the GPIO register by its reset
/linux-4.4.14/Documentation/virtual/kvm/
Dnested-vmx.txt18 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.4.14/Documentation/devicetree/bindings/mmc/
Dtmio_mmc.txt3 The tmio-mmc driver doesn't probe its devices actively, instead its binding to
/linux-4.4.14/Documentation/devicetree/bindings/staging/iio/adc/
Dmxs-lradc.txt18 2 kHz and its default is 2 (= 1 ms)
20 1 ... 2047. It counts at 2 kHz and its default is
/linux-4.4.14/Documentation/prctl/
Dno_new_privs.txt2 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.4.14/Documentation/security/
Dcredentials.txt85 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 …]
DLSM.txt26 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
DYama.txt36 between a debugging process and its inferior (crash handlers, etc),
38 other process (and its descendants) are allowed to call PTRACE_ATTACH
57 this relationship is that of only its descendants when the above
DIMA-templates.txt72 - "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.4.14/Documentation/networking/
Dbatman-adv.txt46 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.
Dipvs-sysctl.txt131 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
194 synchronized, every time the number of its incoming packets
Dregulatory.txt66 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.4.14/fs/kernfs/
DKconfig2 # KERNFS should be selected by its users
/linux-4.4.14/Documentation/vm/
Dzswap.txt26 device when the compressed pool reaches its size limit. This requirement had
49 evict pages from its own compressed pool on an LRU basis and write them back to
84 Zswap seeks to be simple in its policies. Sysfs attributes allow for one user
97 request is made for a page in an old zpool, it is uncompressed using its
99 and its compressor are freed.
Dzsmalloc.txt10 This was one of the major issues with its predecessor (xvmalloc).
19 since this satisfies the requirements of all its current users (in the
Dksm.txt5 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.4.14/Documentation/devicetree/bindings/media/
Ds5p-mfc.txt25 for DMA contiguous memory allocation and its size.
28 for DMA contiguous memory allocation and its size.
/linux-4.4.14/Documentation/fmc/
Dfmc-fakedev.txt7 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
Dfmc-chardev.txt27 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.4.14/Documentation/scheduler/
Dsched-bwc.txt13 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
Dsched-domains.txt25 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.
Dsched-design-CFS.txt23 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.
Dsched-deadline.txt60 that each task runs for at most its runtime every period, avoiding any
93 - When a SCHED_DEADLINE task executes for an amount of time t, its
103 and cannot be scheduled until its scheduling deadline. The "replenishment
150 The utilization of a real-time task is defined as the ratio between its
151 WCET and its period (or minimum inter-arrival time), and represents
168 between the finishing time of a job and its absolute deadline).
196 to respect its deadline; Task_2 is scheduled immediately after Task_1, hence
197 its response time cannot be larger than 50ms + 10ms = 60ms) even if
235 time t + e + P, after its absolute deadline. The total utilization of the
272 represented by its absolute deadlines d_j = r_j + D described above, while
[all …]
/linux-4.4.14/Documentation/cpu-freq/
Dgovernors.txt146 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.4.14/certs/
DKconfig10 the URI should identify, both the certificate and its corresponding
13 If this option is unchanged from its default "certs/signing_key.pem",
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-poweroff.txt7 state. Otherwise its configured as an input.
28 property is not specified, the GPIO is initialized as an output in its
Dgpio-restart.txt7 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.
/linux-4.4.14/drivers/net/wireless/hostap/
DKconfig68 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.4.14/drivers/video/backlight/
DKconfig104 for its LCD.
119 If you have an S6E63M0 LCD Panel, say Y to enable its
127 If you have an LD9040 Panel, say Y to enable its
135 If you have an AMS369FG06 AMOLED Panel, say Y to enable its
143 If you have an LMS501KF03 LCD Panel, say Y to enable its
150 If you have a HX-8357 LCD panel, say Y to enable its LCD control
292 If you have an Intel-based Apple say Y to enable a driver for its
300 for its backlight
368 enable its driver.
/linux-4.4.14/drivers/media/platform/sti/bdisp/
Dbdisp-hw.c99 u32 its; in bdisp_hw_get_and_clear_irq() local
101 its = readl(bdisp->regs + BLT_ITS); in bdisp_hw_get_and_clear_irq()
104 if (!(its & BLT_ITS_AQ1_LNA)) { in bdisp_hw_get_and_clear_irq()
105 dev_dbg(bdisp->dev, "Unexpected IT status: 0x%08X\n", its); in bdisp_hw_get_and_clear_irq()
106 writel(its, bdisp->regs + BLT_ITS); in bdisp_hw_get_and_clear_irq()
111 writel(its, bdisp->regs + BLT_ITS); in bdisp_hw_get_and_clear_irq()
/linux-4.4.14/drivers/fmc/
DKconfig40 its binary and the function carrier->reprogram to actually do it.
49 acquainted with a mezzanine before writing its specific driver.
/linux-4.4.14/arch/arm64/boot/dts/freescale/
Dfsl-ls2080a.dtsi149 its: gic-its@6020000 { label
150 compatible = "arm,gic-v3-its";
404 msi-parent = <&its>;
427 msi-parent = <&its>;
450 msi-parent = <&its>;
473 msi-parent = <&its>;
/linux-4.4.14/fs/reiserfs/
DKconfig35 possibly imagine of its internal consistency throughout its
39 out in checking for consistency when debugging without fear of its
/linux-4.4.14/Documentation/connector/
Dconnector.txt98 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.4.14/Documentation/gpio/
Ddriver.txt41 gpio_chip" (see linux/gpio/driver.h for its complete definition) with members
47 - flag saying whether calls to its methods may sleep
66 (like PM runtime) in its gpio_chip implementation (.get/.set and direction
82 (like PM runtime) as part of its irq_chip implementation on -RT.
98 something like this sequence in its interrupt handler:
130 its interrupt handler:
147 this in its interrupt handler:
164 need to embed the gpio_chip in its state container and obtain a pointer
252 Sometimes it is useful to allow a GPIO chip driver to request its own GPIO
Dboard.txt14 describe its hardware layout. Currently, mappings can be defined through device
136 A lookup table can then be defined as follows, with an empty entry defining its
154 The driver controlling "foo.0" will then be able to obtain its GPIOs as follows:
166 as active-low, its actual signal will be 0 after this code. Contrary to the legacy
/linux-4.4.14/drivers/staging/rdma/ipath/
DTODO1 The ipath driver has been moved to staging in preparation for its removal in a
/linux-4.4.14/arch/arc/include/asm/
Dtlb-mmu1.h25 ; and its unpleasant LFSR pseudo-random sequence
/linux-4.4.14/drivers/input/gameport/
DKconfig47 Audigy card and want to use its gameport.
58 and others), and want to use its gameport.
/linux-4.4.14/drivers/lguest/
DREADME19 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.4.14/fs/exofs/
DKconfig6 as its backing storage.
/linux-4.4.14/Documentation/infiniband/
Dcore_locking.txt71 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.4.14/drivers/staging/media/davinci_vpfe/
Ddavinci-vpfe-mc.txt68 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.4.14/Documentation/trace/
Dintel_th.txt35 via its "masters" attribute group. More detailed GTH interface
43 buffer, which can later on be read from its device nodes via read() or
55 For each Intel TH device in the system a bus of its own is
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dregulator.txt69 Consumer nodes can reference one or more of its supplies/
75 example used to reference its own supply, in which case
76 its just seen as a special case of a regulator being a
/linux-4.4.14/Documentation/power/regulator/
Doverview.txt38 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
Dconsumer.txt11 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.4.14/Documentation/scsi/
DFlashPoint.txt12 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
Dosd.txt20 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
Dlpfc.txt35 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.4.14/Documentation/acpi/
Dnamespace.txt28 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
Denumeration.txt60 configuring GPIOs it can get its ACPI handle and extract this information
138 specific FixedDMA resource by its index.
204 Then the at25 SPI driver can get this configuration by calling _DSM on its
347 resulting child platform device will have its ACPI_COMPANION() set to point
386 6.0). For non-enumerable bus types that object must be _HID and its value must
396 or its value is not valid, the device will not be enumerated by the ACPI
398 (except when an I2C or SPI link from the device to its parent is present, in
/linux-4.4.14/drivers/usb/serial/
DMakefile-keyspan_pda_fw4 # and its lack of preprocessor support
/linux-4.4.14/drivers/media/platform/blackfin/
DKconfig8 Choose PPI or EPPI as its interface.
/linux-4.4.14/drivers/staging/iio/Documentation/
Dinkernel.txt31 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.4.14/Documentation/devicetree/bindings/arm/firmware/
Dtlm,trusted-foundations.txt4 Boards that use the Trusted Foundations secure monitor can signal its
/linux-4.4.14/drivers/staging/dgnc/
DTODO3 * remove unnecessary error messages. Example kzalloc() has its
/linux-4.4.14/Documentation/frv/
Dbooting.txt82 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.4.14/Documentation/devicetree/bindings/mfd/
Dti-keystone-devctrl.txt4 the status of its peripherals. This node is intended to allow access to
/linux-4.4.14/Documentation/devicetree/bindings/iio/light/
Dgp2ap020a00f.txt4 for its built-in led. It is also defined by this binding.
/linux-4.4.14/fs/logfs/
DKconfig14 In its current state it is still very experimental and should
/linux-4.4.14/Documentation/devicetree/bindings/pwm/
Dbrcm,bcm7038-pwm.txt10 its internal variable clock frequency generator
/linux-4.4.14/Documentation/devicetree/bindings/hwmon/
Dibmpowernv.txt11 given sensor and its attribute data
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt72 for its configuration. Obviously, there will be a nice program that
107 and its attributes, allowing the subsystem to ignore all but the
224 that item means that a group can behave as an item in its own right.
243 config_item (or more likely, its container structure), initializes it,
268 down. It no longer has a reference on its parent and has no place in
273 item is removed from its parent group. Like drop_item(),
334 be in its parent's cg_children list for the same duration. This allows
355 in its own subsystem).
374 automatically created inside the parent at its creation. Thus,
412 probably shouldn't calling them of its own gumption. Rather it should
[all …]
/linux-4.4.14/tools/perf/util/
Dpython-ext-sources4 # Each source file must be placed on its own line so that it can be
/linux-4.4.14/drivers/video/fbdev/exynos/
DKconfig29 If you have an S6E8AX0 MIPI AMOLED LCD Panel, say Y to enable its
/linux-4.4.14/net/phonet/
DKconfig9 communication protocol developed by Nokia for use with its modems.
/linux-4.4.14/Documentation/device-mapper/
Dsnapshot.txt30 its visible content unchanged, at least until the <COW device> fills up.
45 to allow userspace to advertise its support for seeing "Overflow" in the
109 merging snapshot after it completes. The "snapshot" that hands over its
113 A snapshot will merge into its origin with the following command:
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Dqcom-ipq806x-sata-phy.txt5 Each SATA PHY controller should have its own node.
Dqcom-apq8064-sata-phy.txt5 Each SATA PHY controller should have its own node.
Dsamsung-phy.txt10 the PHY specifier identifies the PHY and its meaning is as follows:
50 The first phandle argument in the PHY specifier identifies the PHY, its
91 Each SATA PHY controller should have its own node.
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Dsbs_sbs-battery.txt13 a flag specifying its polarity.
/linux-4.4.14/fs/omfs/
DKconfig10 and wish to mount its disk.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Darch_timer.txt7 The per-core architected timer is attached to a GIC to deliver its
9 to deliver its interrupts via SPIs.
/linux-4.4.14/Documentation/sound/alsa/soc/
DDAI.txt10 multiplexes its data on its SDATA_OUT (playback) and SDATA_IN (capture) lines.
/linux-4.4.14/Documentation/development-process/
D7.AdvancedTopics17 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.4.14/include/net/netfilter/
Dnf_conntrack_synproxy.h8 u32 its; member
/linux-4.4.14/Documentation/devicetree/bindings/ata/
Dbrcm,sata-brcmstb.txt4 Each SATA controller should have its own node.
Dfsl-sata.txt4 Each SATA port should have its own node.
Dexynos-sata.txt4 Each SATA controller should have its own node.
/linux-4.4.14/fs/cramfs/
DREADME27 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.4.14/Documentation/devicetree/bindings/power/
Dpower-controller.txt7 standard property "system-power-controller" in its device node. This property
/linux-4.4.14/drivers/clk/versatile/
DKconfig25 Express platforms hidden behind its configuration infrastructure,
/linux-4.4.14/fs/efs/
DKconfig11 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
/linux-4.4.14/tools/perf/Documentation/
Dcallchain-overhead-calculation.txt17 'self' overhead of its child functions. But with this enabled, users
105 is sorted by its values. The 'children' overhead is disabled by
/linux-4.4.14/drivers/hid/usbhid/
DKconfig56 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.4.14/Documentation/block/
Dcfq-iosched.txt154 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.4.14/Documentation/arm/Samsung-S3C24XX/
DNAND.txt12 code, so the driver enforces its own OOB layout and ECC parameters
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dmarvell,pxa2xx-lcdc.txt15 This node must have its properties bus-width and remote-endpoint set.
/linux-4.4.14/scripts/coccinelle/misc/
Dcstptr.cocci1 /// PTR_ERR should be applied before its argument is reassigned, typically
/linux-4.4.14/arch/h8300/boot/compressed/
Dhead.S46 .long 0 ; its size in bytes
/linux-4.4.14/drivers/power/avs/
DKconfig6 its power consumption.
/linux-4.4.14/Documentation/leds/
Dledtrig-transient.txt51 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.4.14/net/netfilter/ipvs/
DKconfig20 information and its administration program, please visit the
182 its server if the server is alive and under load. If the server is
183 overloaded (its active connection numbers is larger than its weight)
184 and there is a server in its half load, then allocate the weighted
248 that minimize its expected delay (The Shortest Expected Delay
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt21 device, and reserves a portion of the underlying storage for its metadata. At
34 Each arena follows the same layout for its metadata, and all references in an
166 the map for that external LBA to point to its new postmap ABA. At this point the
175 RTT for its presence. If the postmap free block is in the RTT, it waits till the
263 with the BTT. It will have to provide the rw_bytes interface in its
268 It may register with the BTT after it adds its own gendisk, using btt_init:
/linux-4.4.14/Documentation/serial/
Dn_gsm.txt14 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.4.14/block/partitions/
DKconfig128 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.4.14/Documentation/devicetree/bindings/mtd/
Dbrcm,brcmnand.txt5 registers and for its data input/output buffer. On some SoCs, this controller is
67 different requirements for its additional properties, as described below each
110 number of available options for its default ECC
/linux-4.4.14/Documentation/sound/oss/
DPSS-updates22 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.4.14/Documentation/input/
Dyealink.txt130 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.4.14/Documentation/pcmcia/
Ddriver.txt21 PCMCIA device listed in its (newly updated) pcmcia_device_id list.
/linux-4.4.14/Documentation/dvb/
Dcontributors.txt4 for the initial saa7146 driver and its recent overhaul
18 (in case you are wondering where CyberLogin is, EON changed its login
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt8 CRYPTO Engines etc has its own instance of dma hardware. QMSS has also
38 its components.

1234567