Searched refs:which (Results 1 – 25 of 2322) sorted by relevance
12345678910>>...93
| /Documentation/timers/ |
| D | hpet.rst | 10 each of which can generate oneshot interrupts and at least one of which has
12 also called "timers", which can be misleading since usually timers are
17 role. Many x86 BIOS writers don't route HPET interrupts at all, which
24 platform code which uses timer 0 or 1 as the main timer to intercept HPET
28 The driver provides a userspace API which resembles the API found in the
|
| D | highres.rst | 6 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
13 The slides contain five figures (pages 2, 15, 18, 20, 22), which illustrate the
37 The main differences to the timer wheel, which holds the armed timer_list type
51 sources, which are registered in the framework and selected on a quality based
53 initializes data structures, which are used by the generic time keeping code to
91 service handler, which is almost inherently hardware dependent.
114 a function pointer in the device description structure, which has to be called
125 The framework adds about 700 lines of code which results in a 2KB increase of
153 which inform hrtimers about availability of new hardware. hrtimers validates
155 switching to high resolution mode. This ensures also that a kernel which is
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | exynos5433-clock.txt | 10 which generates clocks for IMEM/FSYS/G3D/GSCL/HEVC/MSCL/G2D/MFC/PERIC/PERIS
13 which generates clocks for LLI (Low Latency Interface) IP.
15 which generates clocks for DRAM Memory Controller domain.
17 which generates clocks for UART/I2C/SPI/I2S/PCM/SPDIF/PWM/SLIMBUS IPs.
19 which generates clocks for PMU/TMU/MCT/WDT/RTC/SECKEY/TZPC IPs.
21 which generates clocks for USB/UFS/SDMMC/TSI/PDMA IPs.
23 which generates clocks for G2D/MDMA IPs.
25 which generates clocks for Display (DECON/HDMI/DSIM/MIXER) IPs.
27 which generates clocks for Cortex-A5/BUS/AUDIO clocks.
30 which generates global data buses clock and global peripheral buses clock.
[all …]
|
| D | ux500.txt | 10 CLKRST4, which does not exist.
14 reset, control unit) clocks. The cell indicates which PRCMU
18 The first cell indicates which PRCC block the consumer
20 cell indicates which clock inside the PRCC block it wants,
24 The first cell indicates which PRCC block the consumer
26 cell indicates which clock inside the PRCC block it wants,
|
| /Documentation/x86/ |
| D | mds.rst | 17 MSBDS leaks Store Buffer Entries which can be speculatively forwarded to a
20 memory address, which can be exploited under certain conditions. Store
23 buffer is repartitioned which can expose data from one thread to the other.
26 L1 miss situations and to hold data which is returned or sent in response
29 deallocated it can retain the stale data of the preceding operations which
30 can then be forwarded to a faulting or assisting load operation, which can
37 contain stale data from a previous operation which can be forwarded to
38 faulting or assisting loads under certain conditions, which again can be
56 - to have a disclosure gadget which exposes the speculatively accessed
59 - to control the pointer through which the disclosure gadget exposes the
[all …]
|
| D | booting-dt.rst | 9 supports one calling convention which is documented in
12 which requires at least boot protocol 2.09.
18 does not parse / consider data which is already covered by the boot
20 or initrd address. It simply holds information which can not be retrieved
|
| /Documentation/process/ |
| D | 4.Coding.rst | 8 code. It is the code which will be examined by other developers and merged
9 (or not) into the mainline tree. So it is the quality of this code which
13 number of ways in which kernel developers can go wrong. Then the focus
14 will shift toward doing things right and the tools which can help in that
28 which does not meet the coding style guidelines. The presence of that code
46 The other trap is to assume that code which is already in the kernel is
56 The coding style document also should not be read as an absolute law which
58 style (a line which becomes far less readable if split to fit within the
81 At a simple level, consider a function which has an argument which is
84 provides. By that time, though, chances are good that the code which
[all …]
|
| D | license-rules.rst | 19 which is required to be compatible with the GPL-2.0::
32 The User-space API (UAPI) header files, which describe the interface of
35 which does not extend the GPL requirements to any software which uses it to
37 into any source files which create an executable running on the Linux
43 tools which are used in the context of license compliance.
48 under which the content of the file is contributed. SPDX license
64 possible line in a file which can contain a comment. For the majority
65 of files this is the first line, except for scripts which require the
84 appropriate comment mechanism which the tool accepts shall be used. This
88 there are still older assembler tools which cannot handle C++ style
[all …]
|
| D | 1.Intro.rst | 27 :ref:`development_coding` is about the coding process; several pitfalls which
30 which can help to ensure that kernel patches are correct.
56 kernel has evolved into a best-of-breed operating system component which
75 offer this kind of openness, which is a characteristic of the free software
84 evolved its own distinct ways of operating which allow it to function
132 - Code which has been merged into the mainline kernel is available to all
133 Linux users. It will automatically be present on all distributions which
148 Code which is in the mainline, instead, does not require this work as the
151 which has been merged into the mainline has significantly lower
154 - Beyond that, code which is in the kernel will often be improved by other
[all …]
|
| /Documentation/security/ |
| D | sak.rst | 8 An operating system's Secure Attention Key is a security tool which is
10 is an undefeatable way of killing all programs which could be
42 systems which implement C2 level security. This author does not
46 2. On the PC keyboard, SAK kills all applications which have
49 Unfortunately this includes a number of things which you don't
54 You can identify processes which will be killed by SAK with the
67 initscript which launches gpm and changing it thusly:
86 These commands cause **all** daemons which are launched by the
|
| /Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 11 completely by the bt8xx chip, which is common on all boards. But
15 bttv-cards.c, which holds the information required for each board.
18 log, telling which card type is used. Like this one::
28 new entries which are not listed yet. If there isn't one for your
52 (``BT848_GPIO_OUT_EN``), it says which pins are actively driven by the
58 which does the sound routing. But every board is a little different.
63 As mentioned above, there is a array which holds the required
74 gpiomask specifies which pins are used to control the audio mux chip.
80 (i.e. which pins must be high/low for tuner/mute/...). This will be
92 You can have a look at the board to see which of the gpio pins are
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra20-emc.txt | 33 next level of nodes below the emc table are used to specify which settings
34 apply for which ram-code settings.
43 for which this node (and children) are valid.
53 There are two ways of specifying which tables to use:
56 and they will always be used (based on which frequency is used).
66 used to select which tables to use.
72 the valid frequency for which the table should be used (in kHz).
73 - clock-frequency : the clock frequency for the EMC at which this
|
| /Documentation/usb/ |
| D | gadget_configfs.rst | 14 A USB Linux Gadget is a device which has a UDC (USB Device Controller) and can
18 A gadget is seen by its host as a set of configurations, each of which contains
19 a number of interfaces which, from the gadget's perspective, are known as
25 and which functions each configuration will provide.
101 where <name> can be any string which is legal in a filesystem and the
148 At this moment a number of gadgets is created, each of which has a number of
150 is specifying which function is available in which configuration (the same
302 Both items and groups can have attributes, which are represented as files.
304 which can be read-only or read-write, depending on what they represent.
307 configfs_attributes which are generic and of the same type for all
[all …]
|
| /Documentation/filesystems/ |
| D | ocfs2-online-filecheck.rst | 15 Then, a mount option (errors=continue) is introduced, which would return the
23 This effort is to check/fix small issues which may hinder day-to-day operations
31 This feature is not suited for extravagant checks which involve dependency of
43 by the inode number which caused the error. This inode number would be the
50 Here, <devname> indicates the name of OCFS2 volume device which has been already
52 communicate with kernel space, tell which file(inode number) will be checked or
53 fixed. Currently, three operations are supported, which includes checking
97 small linked list buffer which would contain the last (N) inodes
98 fixed/checked, the detailed errors which were fixed/checked are printed in the
|
| D | ext2.rst | 48 resuid=n The user ID which may use the reserved blocks.
49 resgid=n The group ID which may use the reserved blocks.
89 which is decided when the filesystem is created. Smaller blocks mean
101 bitmap and the inode usage bitmap which show which blocks and inodes
108 in the same block group as the inode which contains them.
130 and which OS created it.
145 structure contains pointers to the filesystem blocks which contain the
152 There are some reserved fields which are currently unused in the inode
153 structure and several which are overloaded. One field is reserved for the
157 by the HURD to reference the inode of a program which will be used to
[all …]
|
| /Documentation/i2c/ |
| D | instantiating-devices.rst | 6 level. Instead, the software must know which devices are connected on each
16 for many embedded systems. On such systems, each I2C bus has a number which
18 which live on this bus.
54 additional properties which might be needed to set up the device, please refer
62 which is currently located at :doc:`../firmware-guide/acpi/enumeration`.
71 struct i2c_board_info which is registered by calling
129 The above code instantiates 1 I2C device on the I2C bus which is on the
133 present or not (for example for an optional feature which is not present
159 The above code instantiates up to 1 I2C device on the I2C bus which is on
164 The driver which instantiated the I2C device is responsible for destroying
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-g-selection.rst | 39 functionality performed by the subdevs which affect the image size. This
50 ``VIDIOC_SUBDEV_S_SELECTION`` are only valid if the ``which`` field is set to
58 targets are the targets which configure the hardware. The BOUNDS target
64 To discover which targets are supported, the user can perform
81 - ``which``
117 ``pad`` references a non-existing pad, the ``which`` field
123 subdevice and the ``which`` field is set to ``V4L2_SUBDEV_FORMAT_ACTIVE``.
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | iqs5xx.txt | 12 - interrupts : GPIO to which the device's active-high RDY
15 - reset-gpios : GPIO to which the device's active-low NRST
46 which may already be specified by the device's
50 which may already be specified by the device's
54 which may already be specified by the device's
|
| /Documentation/networking/ |
| D | sysfs-tagging.rst | 26 and KOBJ_NS_TYPES, and ns will point to the namespace to which it
42 - call kobj_ns_type_register() with its ``kobj_ns_type_operations`` which has
44 - current_ns() which returns current's namespace
45 - netlink_ns() which returns a socket's namespace
46 - initial_ns() which returns the initial namesapce
|
| /Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 4 L1 Terminal Fault is a hardware vulnerability which allows unprivileged
5 speculative access to data which is available in the Level 1 Data Cache
6 when the page table entry controlling the virtual address, which is used
24 - Intel processors which have the ARCH_CAP_RDCL_NO bit set in the
46 If an instruction accesses a virtual address for which the relevant page
72 PTE which is marked non present. This allows a malicious user space
73 application to attack the physical memory to which these PTEs resolve.
79 inversion, which is permanently enabled and has no performance
80 impact. The kernel ensures that the address bits of PTEs, which are not
90 OSes, which can control the PTEs directly, and malicious guest user
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-ryos | 4 Description: When written, this file lets one select which data from which
12 Description: The mouse can store 5 profiles which can be switched by the
28 which profile to read.
38 which profile to read.
48 which profile to read.
58 which profile to read.
68 which profile to read.
78 which profile to read.
86 Profile index for which this settings occur is included in
89 which profile to read.
[all …]
|
| /Documentation/vm/ |
| D | z3fold.rst | 9 It is a zbud derivative which allows for higher compression
21 up to 3 pages unlike zbud which can store at most 2. Therefore the
26 handle which encodes actual location of the allocated object.
30 which makes it a better fit for small and response-critical systems.
|
| /Documentation/trace/ |
| D | intel_th.rst | 23 - Software Trace Hub (STH), trace source, which is a System Trace
25 - Memory Storage Unit (MSU), trace output, which allows storing
29 - Global Trace Hub (GTH), which is a switch and a central component
34 notable of them is "active", which enables or disables trace output
41 STH registers an stm class device, through which it provides interface
46 buffer, which can later on be read from its device nodes via read() or
60 created and assigned an id number that reflects the order in which TH
62 begin with this id: 0-gth, 0-msc0, 0-msc1, 0-pti, 0-sth, which is
72 # figure out which GTH port is the first memory controller::
109 capture from a remote debug host, which should be connected via one of
[all …]
|
| /Documentation/powerpc/ |
| D | eeh-pci-error-recovery.rst | 23 Another "traditional" technique is to ignore such errors, which
138 If so, these make a call to eeh_dn_check_failure(), which in turn
179 which causes uevents to go out to user space. This triggers
185 which restarts the device driver and triggers more user-space
220 struct device_driver->remove() which is just
224 struct pci_driver->remove() which is just
234 which is just pcnet32_close() // in pcnet32.c
236 which does what you wanted
241 which
249 which calls struct pci_driver->remove() which is pcnet32_remove_one()
[all …]
|
| /Documentation/core-api/ |
| D | padata.rst | 9 Padata is a mechanism by which the kernel can farm jobs out to be done in
12 It was originally developed for IPsec, which needs to perform encryption and
52 parallel cpumask describes which processors will be used to execute jobs
53 submitted to this instance in parallel and a serial cpumask defines which
64 Reading one of these files shows the user-supplied cpumask, which may be
84 padata_priv structure, which represents one job::
141 pains to ensure that jobs are completed in the order in which they were
165 job by defining a padata_mt_job structure, which is explained in the Interface
166 section. This includes a pointer to the thread function, which padata will
168 function, which accepts three arguments, ``start``, ``end``, and ``arg``, where
[all …]
|
12345678910>>...93