| /linux/drivers/char/tpm/ |
| H A D | Kconfig | 15 say Yes and it will be accessible from within Linux. For
69 within Linux. To compile this driver as a module, choose M here;
81 within Linux. To compile this driver as a module, choose M here;
89 say Yes and it will be accessible from within Linux.
99 say Yes and it will be accessible from within Linux.
111 within Linux on Socionext SynQuacer platform.
129 accessible from within Linux.
139 Specification 0.20 say Yes and it will be accessible from within
150 from within Linux.
159 say Yes and it will be accessible from within Linux. To
[all …]
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-devices-system-cpu | 64 Description: internal kernel map of CPUs within the same core.
69 Description: human-readable list of CPUs within the same core.
86 Description: internal kernel map of CPUs within the same die.
94 Description: human-readable list of CPUs within the same die.
99 Description: internal kernel map of CPUs within the same cluster.
103 Description: human-readable list of CPUs within the same cluster.
108 Description: internal kernel map of cpuX's hardware threads within the same
113 Description: human-readable list of cpuX's hardware threads within the same
119 Description: internal kernel map of cpuX's hardware threads within the same
124 Description: human-readable list of cpuX's hardware threads within the same
|
| /linux/Documentation/devicetree/bindings/mips/cavium/ |
| H A D | ciu.txt | 12 - #interrupt-cells: Must be <2>. The first cell is the bank within
14 within the bank and may have a value between 0 and 63.
22 * 2) Bit within the register (0..63)
|
| H A D | ciu2.txt | 12 - #interrupt-cells: Must be <2>. The first cell is the bank within
14 the bit within the bank and may also have a value between 0 and 63.
22 * 2) Bit within the register (0..63)
|
| /linux/Documentation/devicetree/bindings/ptp/ |
| H A D | ptp-ines.txt | 7 port index within the IP core.
14 Required format of the port handle within the PHY node:
17 the port channel within the IP core
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | arm-ni.rst | 5 NI-700 and friends implement a distinct PMU for each clock domain within the
8 the clock domain ID within that particular instance. If multiple NI instances
9 exist within a system, the PMU devices can be correlated with the underlying
|
| /linux/Documentation/sound/soc/ |
| H A D | pops-clicks.rst | 6 of components within the audio subsystem. This is noticeable on PCs when an
11 because the components within the subsystem are being dynamically powered
21 suppression. Pops can be reduced within playback by powering the audio
50 An unwanted zipper noise can occur within the audio playback or capture stream
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-scmi-raw | 10 entry if it arrived within the configured timeout.
25 entry if it arrived within the configured timeout.
27 from this same entry too if it arrived within the configured
78 entry if it arrived on channel <m> within the configured
102 entry if it arrived on channel <m> within the configured
105 from this same entry too if it arrived within the configured
|
| H A D | sysfs-devices | 9 devices within this tree will change.
15 within the /sys/devices tree of the individual devices.
|
| /linux/Documentation/netlabel/ |
| H A D | draft-ietf-cipso-ipsecurity-01.txt | 42 the fixed fields within these two options are administered by the Defense
77 systems within a single Domain of Interpretation (DOI). A DOI is a
82 mapping to hosts within the authority's domain. These mappings may be
123 a mapping table within CIPSO hosts to map these numbers to their
139 to identify which mapping was used for the values within the option.
151 all tags, as well as fields within a tag, are not aligned on any particular
230 restriction of 40 bytes the value within this field is between 4 and 34.
316 restriction of 40 bytes the value within this field is between 4 and 34.
347 by their position within a bit field. The length of each category is 2
350 value. The categories MUST be listed in ascending order within the tag.
[all …]
|
| /linux/security/ipe/ |
| H A D | Kconfig | 59 This option enables the 'dmverity_roothash' property within IPE
68 This option enables the 'dmverity_signature' property within IPE
79 This option enables the 'fsverity_digest' property within IPE
90 This option enables the 'fsverity_signature' property within IPE
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | ti-pci.txt | 37 should contain the register offset within syscon
47 they are locally accessed within the DIF CS space
49 they are locally accessed within the DIF CS2 space
55 should contain the register offset within syscon
|
| /linux/Documentation/mm/ |
| H A D | page_frags.rst | 6 which resides within a 0 or higher order compound page. Multiple
7 fragments within that page are individually refcounted, in the page's
32 only usable within the softirq context.
|
| /linux/Documentation/fb/ |
| H A D | pxafb.rst | 96 1. overlay can start at a 32-bit word aligned position within the base
130 d. the rectangle of the overlay should be within the base plane,
151 3. for YUV planar formats, these are actually not supported within the
153 and lengths of each component within the framebuffer.
|
| /linux/arch/m68k/fpsp040/ |
| H A D | sacos.S | 13 | Accuracy and Monotonicity: The returned result is within 3 ulps in
14 | 64 significant bit, i.e. within 0.5001 ulp to 53 bits if the
|
| /linux/arch/alpha/lib/ |
| H A D | ev6-memset.S | 65 xor $16,$6,$1 # E : will complete write be within one quadword?
70 bic $1,7,$1 # E : fit within a single quadword?
248 xor $16,$6,$1 # E : will complete write be within one quadword?
251 bic $1,7,$1 # E : fit within a single quadword
432 xor $16,$6,$1 # E : will complete write be within one quadword?
436 bic $1,7,$1 # E : fit within a single quadword
|
| /linux/Documentation/arch/xtensa/ |
| H A D | booting.rst | 19 virtual or physical address. In either case it must be within the default
20 virtual mapping. It is considered physical if it is within the range of
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-kwork.txt | 107 Only analyze samples within given time window: <start>,<stop>. Times
137 Only analyze samples within given time window: <start>,<stop>. Times
176 Only analyze samples within given time window: <start>,<stop>. Times
206 Only analyze samples within given time window: <start>,<stop>. Times
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | wiznet,w5x00.txt | 5 For each device connected to a SPI bus, define a child node within
14 - interrupts: Specify the interrupt index within the interrupt controller (referred
|
| H A D | microchip,enc28j60.txt | 5 For each device connected to a SPI bus, define a child node within
11 - interrupts: Specify the interrupt index within the interrupt controller (referred
|
| /linux/Documentation/driver-api/tty/ |
| H A D | tty_ldisc.rst | 29 discipline. The reference count of the tty_ldisc structure within a tty counts
31 the number of threads of execution within an ldisc method (plus those about to
78 in this situation if used within these functions. Ldisc and driver code
|
| /linux/Documentation/devicetree/bindings/cpu/ |
| H A D | cpu-topology.txt | 42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct
77 only be defined within the cpu-map node and every core/thread in the
78 system must be defined within the topology. Any other configuration is
88 which are siblings within a single common parent node must be given a unique and
102 Description: must be declared within a cpu-map node, one node
120 Description: must be declared within a cpu-map node, one node
122 clustering within a single physical socket and cluster
|
| /linux/LICENSES/dual/ |
| H A D | Apache-2.0 | 78 subsequently incorporated within the Work.
97 lawsuit) alleging that the Work or a Contribution incorporated within
120 include a readable copy of the attribution notices contained within
123 places: within a NOTICE text file distributed as part of the
124 Derivative Works; within the Source form or documentation, if
125 provided along with the Derivative Works; or, within a display
129 add Your own attribution notices within Derivative Works that You
|
| /linux/Documentation/devicetree/bindings/hwlock/ |
| H A D | hwlock.txt | 51 The following example has a node requesting two hwlocks, a hwlock within
53 hwlock within the hwlock device node 'hwlock2' with #hwlock-cells value of 2.
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | brcm,nsp-gpio.txt | 12 Must be two. The first cell is the GPIO pin number (within the
39 The list of pins (within the controller's own pin space) that properties
|