| /linux-4.4.14/drivers/char/tpm/ |
| D | Kconfig | 12 say Yes and it will be accessible from within Linux. For
34 within Linux. To compile this driver as a module, choose M here;
42 accessible from within Linux.
52 Specification 0.20 say Yes and it will be accessible from within
63 from within Linux.
72 say Yes and it will be accessible from within Linux. To
81 will be accessible from within Linux. To compile this driver
90 will be accessible from within Linux.
101 will be accessible from within Linux. To compile this driver
110 say Yes and it will be accessible from within Linux. See
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/mips/cavium/ |
| 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)
|
| 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)
|
| D | cib.txt | 20 - #interrupt-cells: Must be <2>. The first cell is the bit within the
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | pops_clicks.txt | 5 of components within the audio subsystem. This is noticeable on PCs when an
10 because the components within the subsystem are being dynamically powered
20 suppression. Pops can be reduced within playback by powering the audio
47 An unwanted zipper noise can occur within the audio playback or capture stream
|
| D | dapm.txt | 8 Linux devices to use the minimum amount of power within the audio
13 all power switching is done within the ASoC core. No code changes or
16 activity and audio mixer settings within the device.
18 DAPM spans the whole machine. It covers power control within the entire
22 There are 4 power domains within DAPM
117 audio paths within the audio subsystem. They have the following form:-
192 Widgets are connected to each other within the codec, platform and machine by
259 An endpoint is a start or end point (widget) of an audio signal within the
|
| /linux-4.4.14/Documentation/ |
| D | cputopology.txt | 25 internal kernel map of cpuX's hardware threads within the same
30 human-readable list of cpuX's hardware threads within the same
35 internal kernel map of cpuX's hardware threads within the same
40 human-readable list of cpuX's hardware threads within the same
45 internal kernel map of cpuX's hardware threads within the same
50 human-readable list of cpuX's hardware threads within the same
|
| D | lzo.txt | 108 2-byte block from the dictionary within a 1kB distance. It is worth
130 Copy of a block within 16..48kB distance (preferably less than 10B)
138 Copy of small block within 16kB distance (preferably less than 34B)
145 Copy 3-4 bytes from block within 2kB distance
152 Copy 5-8 bytes from block within 2kB distance
|
| D | clk.txt | 34 is defined in struct clk_foo and pointed to within struct clk. This
154 include/linux/clk.h is included within that header and clk-private.h
264 framework functions from within its implementation of clock operations. This
266 within the .set_rate operation of another clock. This case must be considered
|
| D | volatile-considered-harmful.txt | 52 accesses within a critical section. But, within the kernel, I/O memory
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-bwc.txt | 20 within each of these updates is tunable and described as the "slice".
24 Quota and period are managed within the cpu subsystem via cgroupfs.
26 cpu.cfs_quota_us: the total available run-time within a period (in microseconds)
81 within a hierarchy.
87 a. it fully consumes its own quota within a period
88 b. a parent's quota is fully consumed within its period
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | ring.txt | 1 Buffer support within IIO
4 a buffer may supply and how it is specified within IIO. For more
22 The function pointers within here are used to allow the core to handle
|
| D | trigger.txt | 10 allocates a trigger structure. The key elements to then fill in within
|
| /linux-4.4.14/kernel/gcov/ |
| D | base.c | 126 static inline int within(void *addr, void *start, unsigned long size) in within() function
145 if (within(info, mod->module_core, mod->core_size)) { in gcov_module_notifier()
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-devices | 9 devices within this tree will change.
15 within the /sys/devices tree of the individual devices.
|
| D | sysfs-bus-iio-humidity-hdc100x | 6 Controls the heater device within the humidity sensor to get
|
| D | debugfs-ideapad | 8 capability and what graphic component within the machine.
|
| D | sysfs-kernel-livepatch | 34 that is patched within the object.
|
| D | sysfs-devices-system-cpu | 91 within the same physical_package_id.
94 numbers within the same physical_package_id as cpu#.
101 threads within the same core as cpu#
104 threads within the same core as cpu#
|
| D | sysfs-class-net-cdc_ncm | 98 Remainder used to align input datagram payload within
130 offsets within the NTB: Padding, shall be transmitted
|
| D | sysfs-driver-hid-logitech-lg4ff | 6 wheel. Writing a value within min and max boundaries sets the
|
| D | sysfs-driver-hid-picolcd | 37 within permitted rates.
|
| D | sysfs-class-uwb_rc-wusbhc | 18 within 'wusb_trust_timeout' ms are considered to have
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| 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
|
| D | satanh.S | 14 | Accuracy and Monotonicity: The returned result is within 3 ulps in
15 | 64 significant bit, i.e. within 0.5001 ulp to 53 bits if the
|
| D | sasin.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
|
| D | scosh.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
|
| D | ssinh.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
|
| D | stwotox.S | 14 | Accuracy and Monotonicity: The returned result is within 2 ulps in
15 | 64 significant bit, i.e. within 0.5001 ulp to 53 bits if the
|
| D | stanh.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
|
| D | slog2.S | 16 | ACCURACY and MONOTONICITY: The returned result is within 1.7
17 | ulps in 64 significant bit, i.e. within 0.5003 ulp
|
| D | satan.S | 13 | Accuracy and Monotonicity: The returned result is within 2 ulps in
14 | 64 significant bit, i.e. within 0.5001 ulp to 53 bits if the
|
| /linux-4.4.14/Documentation/netlabel/ |
| 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-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | st,stm32-rcc.txt | 32 The secondary index is the bit number within the RCC register bank, starting
36 Where bit_offset is the bit offset within the register (LSB is 0, MSB is 31).
|
| D | hi3620-clock.txt | 4 controllers within the Hi3620 SoC.
|
| D | marvell,pxa910.txt | 4 controllers within the PXA910 SoC.
|
| D | hix5hd2-clock.txt | 4 controllers within the hix5hd2 SoC.
|
| D | exynos5440-clock.txt | 4 controllers within the Exynos5440 SoC.
|
| D | marvell,pxa168.txt | 4 controllers within the PXA168 SoC.
|
| D | marvell,mmp2.txt | 4 controllers within the MMP2 SoC.
|
| D | marvell,pxa1928.txt | 4 controllers within the PXA1928 SoC. The PXA1928 contains 3 clock controller
|
| D | exynos5250-clock.txt | 4 controllers within the Exynos5250 SoC.
|
| D | exynos4415-clock.txt | 4 consumer devices within the Exynos4415 SoC.
|
| D | amlogic,meson8b-clkc.txt | 4 controllers within the SoC.
|
| D | exynos5410-clock.txt | 4 controllers within the Exynos5410 SoC.
|
| D | exynos5420-clock.txt | 4 controllers within the Exynos5420 SoC and for the Exynos5800 SoC.
|
| D | exynos4-clock.txt | 4 within the Exynos4 SoC. The clock binding described here is applicable to all
|
| D | exynos3250-clock.txt | 4 controllers within the Exynos3250 SoC.
|
| D | samsung,s3c2412-clock.txt | 4 within the SoC. The clock binding described here is applicable to the s3c2412
|
| D | samsung,s3c2410-clock.txt | 4 within the SoC. The clock binding described here is applicable to the s3c2410,
|
| D | rockchip,rk3288-cru.txt | 4 controllers within the SoC and also implements a reset controller for SoC
|
| D | samsung,s3c2443-clock.txt | 4 within the SoC. The clock binding described here is applicable to all SoCs in
|
| D | rockchip,rk3188-cru.txt | 4 controllers within the SoC and also implements a reset controller for SoC
|
| D | rockchip,rk3368-cru.txt | 4 controllers within the SoC and also implements a reset controller for SoC
|
| D | samsung,s5pv210-clock.txt | 5 within the SoC.
|
| D | samsung,s3c64xx-clock.txt | 4 within the SoC. The clock binding described here is applicable to all SoCs in
|
| D | vt8500.txt | 38 - enable-bit : shall be the bit within enable-reg to enable/disable the clock.
|
| D | exynos7-clock.txt | 5 generate and supply clocks to various hardware blocks within
|
| /linux-4.4.14/Documentation/fb/ |
| D | pxafb.txt | 73 1. overlay can start at a 32-bit word aligned position within the base
103 d. the rectangle of the overlay should be within the base plane,
122 3. for YUV planar formats, these are actually not supported within the
124 and lengths of each component within the framebuffer.
|
| /linux-4.4.14/arch/alpha/lib/ |
| D | ev6-memset.S | 64 xor $16,$6,$1 # E : will complete write be within one quadword?
69 bic $1,7,$1 # E : fit within a single quadword?
246 xor $16,$6,$1 # E : will complete write be within one quadword?
249 bic $1,7,$1 # E : fit within a single quadword
429 xor $16,$6,$1 # E : will complete write be within one quadword?
433 bic $1,7,$1 # E : fit within a single quadword
|
| /linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 21 - thermal zones: used to describe thermal data within the hardware;
37 to identify uniquely the sensor instances within
115 - trip: A phandle of a trip point node within the same thermal
123 of all cooling contributions within a thermal zone.
348 /* each zone within the SoC may have its own trips */
362 /* each zone within the SoC may have its own cooling */
375 /* each zone within the SoC may have its own trips */
389 /* each zone within the SoC may have its own cooling */
402 /* each zone within the SoC may have its own trips */
416 /* each zone within the SoC may have its own cooling */
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/hwlock/ |
| 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.
|
| D | omap-hwspinlock.txt | 13 within a hwspinlock bank.
|
| D | qcom-hwspinlock.txt | 18 offset of the hwmutex block within the syscon
|
| /linux-4.4.14/Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.txt | 16 SATA port to a combophy and a lane within that
21 - calxeda,led-order : a u32 array that map port numbers to offsets within the
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | lm95245 | 27 is given within a range of -127 to +127.875 degrees. Remote temperatures are
28 given within a range of -127 to +255 degrees. Resolution depends on
|
| D | wm8350 | 19 of the major supplies within the system. Currently the driver provides
|
| D | wm831x | 19 of the major supplies within the system. Currently the driver provides
|
| D | lm83 | 74 is given within a range of 0 to +85 degrees. Remote temperatures are
75 given within a range of 0 to +125 degrees. Resolution is 1.0 degree,
|
| D | w83793 | 82 predefined value, within a tolerance margin. So if tempX_input >
85 the PWM value. If the temperature is within the tolerance range, the PWM
|
| D | lm95234 | 30 is provided within a range of -127 to +255 degrees (+127.875 degrees for
|
| D | abituguru-datasheet | 70 terminoligy for the addressing within a bank this is not 100% correct, in
71 bank 0x24 for example the addressing within the bank selects a PWM output not
87 to hold 0x09, DATA should read 0x09 within 250 read cycles.
154 turned up which do not hold 0x08 at DATA within 250 reads after writing the
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.pvrusb2 | 61 the html files within the doc directory; these are exactly the same
78 defined functional units within the pvrusb2 driver and bears no
87 or is otherwise instanced within the data structures implemented
98 messages that can be enabled within the driver.
111 interact with the Conexant mpeg2 encoder chip within the pvrusb2
133 within the jurisdiction of pvrusb-context not here).
158 operate corresponding chips within the pvrusb2 device. It is
|
| D | README.ir | 29 The modules register the remote as keyboard within the linux input
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | brcm,cygnus-gpio.txt | 14 Must be two. The first cell is the GPIO pin number (within the
40 The list of pins (within the controller's own pin space) that properties
|
| /linux-4.4.14/Documentation/devicetree/bindings/nvmem/ |
| D | nvmem.txt | 25 reg: specifies the offset in byte within the storage device.
30 in bit and number of bits within the address range specified by reg property.
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-tz1090.txt | 23 [gpio number within the gpio bank]
44 [gpio number within the gpio bank]
|
| D | gpio-samsung.txt | 12 [pin number within the gpio controller]
|
| D | gpio-dsp-keystone.txt | 20 registers within device state control registers range.
|
| D | gpio-altera.txt | 13 - The first cell is the GPIO offset number within the GPIO controller.
|
| D | spear_spics.txt | 27 All the above bit offsets are within peripcfg register.
|
| D | 8xxx_gpio.txt | 37 cells required to specify an interrupt within
|
| D | brcm,brcmstb-gpio.txt | 17 Should be <2>. The first cell is the pin number (within the controller's
|
| /linux-4.4.14/Documentation/devicetree/bindings/c6x/ |
| D | soc.txt | 15 - nodes for IP blocks within SoC
|
| /linux-4.4.14/drivers/soc/brcmstb/ |
| D | Kconfig | 7 can be enabled individually within this menu.
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Transition-notes | 83 it is holding pd_lock. The only place within the area where we
84 release pd_lock is in pd_next_buf() (called from within the area).
93 by the thread in question. However, all such places within the area are right
96 (4) is done the same way - all places where we release pi_spinlock within
128 can be taken to callers as long as they remain within the area.
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | governors.txt | 47 How to decide what frequency within the CPUfreq policy should be used?
61 within specific "limits" | to specific frequencies
70 / what target_freq to set within
78 is within policy->{min,max}
88 highest frequency within the borders of scaling_min_freq and
96 lowest frequency within the borders of scaling_min_freq and
260 target_freq must be within policy->min and policy->max, of course.
|
| D | user-guide.txt | 133 what speed the processor shall run within the boundaries. One such
147 "cpufreq" within the cpu-device directory
221 but only within the limits of
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smd.txt | 31 - u32 representing offset to the register within the syscon
32 - u32 representing the ipc bit within the register
|
| /linux-4.4.14/Documentation/RCU/ |
| D | UP.txt | 64 1. If a number of items need to be passed to call_rcu() within
102 list, and is therefore within an RCU read-side critical section.
103 Therefore, the called function has been invoked within an RCU
109 Any lock that is acquired within an RCU callback must be
|
| D | lockdep-splat.txt | 79 code was invoked either from within an RCU read-side critical section
98 With this change, the rcu_dereference() is always within an RCU
|
| D | rcu.txt | 41 counters. These counters allow limited types of blocking within
43 counters, and permits general blocking within RCU read-side
|
| D | torture.txt | 40 to force_quiescent_state() within a burst.
110 within both an rcu_read_lock() and a preempt_disable().
159 within any given "test_boost_interval". Defaults to
262 within a timer handler. This value should be non-zero only
|
| /linux-4.4.14/Documentation/firmware_class/ |
| D | README | 101 (probably within initramfs).
116 within the kernel image, probably within initramfs.
|
| /linux-4.4.14/Documentation/ABI/removed/ |
| D | devfs | 6 races, contains a naming policy within the kernel that is
|
| /linux-4.4.14/arch/arm/include/debug/ |
| D | vf.S | 22 and \rv, \rp, #0xffffff @ offset within 16MB section
|
| D | tegra.S | 154 92: and \rv, \rp, #0xffffff @ offset within 1MB section
|
| /linux-4.4.14/arch/avr32/boards/favr-32/ |
| D | Kconfig | 14 Must be within the range 32000 to 50000, which should be suitable to
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | nvidia,tegra30-ahub.txt | 59 For RX CIFs, the numbers indicate the register number within AHUB routing
61 For TX CIFs, the numbers indicate the bit position within the AHUB routing
|
| D | soc-ac97link.txt | 3 These bindings can be included within any other device node.
|
| D | wm8962.txt | 21 performed. And note that only the value within [0x0, 0xffff] is valid.
|
| D | fsl,asrc.txt | 7 three substreams within totally 10 channels.
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | 88pm860x.txt | 6 - regulators: A node that houses a sub-node for each regulator within the
|
| D | 88pm800.txt | 6 - regulators: A node that houses a sub-node for each regulator within the
|
| D | isl9305.txt | 7 - regulators: A node that houses a sub-node for each regulator within the
|
| D | max8907.txt | 14 - regulators: A node that houses a sub-node for each regulator within the
|
| D | da9211.txt | 7 - regulators: A node that houses a sub-node for each regulator within the
|
| /linux-4.4.14/Documentation/networking/ |
| D | irda.txt | 1 To use the IrDA protocols within Linux you will need to get a suitable copy
|
| D | ax25.txt | 1 To use the amateur radio protocols within Linux you will need to get a
|
| /linux-4.4.14/Documentation/devicetree/bindings/reset/ |
| D | brcm,bcm63138-pmb.txt | 11 - #reset-cells: must be 2 first cell is the address within the bus instance designated
|
| /linux-4.4.14/arch/x86/mm/ |
| D | pageattr.c | 113 within(unsigned long addr, unsigned long start, unsigned long end) in within() function
261 if (pcibios_enabled && within(pfn, BIOS_BEGIN >> PAGE_SHIFT, BIOS_END >> PAGE_SHIFT)) in static_protections()
270 if (within(address, (unsigned long)_text, (unsigned long)_etext)) in static_protections()
277 if (within(pfn, __pa_symbol(__start_rodata) >> PAGE_SHIFT, in static_protections()
292 within(address, (unsigned long)_text, in static_protections()
1136 if (within(vaddr, PAGE_OFFSET, in __cpa_process_fault()
1284 if (!(within(vaddr, PAGE_OFFSET, in cpa_process_alias()
1302 if (!within(vaddr, (unsigned long)_text, _brk_end) && in cpa_process_alias()
1303 within(cpa->pfn, highmap_start_pfn(), highmap_end_pfn())) { in cpa_process_alias()
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | hix5hd2-phy.txt | 12 - hisilicon,power-reg: offset and bit number within peripheral-syscon,
|
| /linux-4.4.14/Documentation/usb/ |
| D | mtouchusb.txt | 45 the controller. This means calibration must be performed within the
65 this driver! If you want touch drivers only supported within X, please go to:
|
| D | error-codes.txt | 96 b) no response packet received within the
101 b) no response packet received within the
111 -ETIME (**) No response packet received within the prescribed
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | marvell-orion-net.txt | 10 describes up to 3 ethernet port nodes within that controller. The reason for
11 the multiple levels is that the port registers are interleaved within a single
|
| D | broadcom-bcm87xx.txt | 11 address within the MMD, the third cell contains a mask to be ANDed
|
| D | samsung-sxgbe.txt | 22 When fixed length is needed for burst mode, it can be set within allowable
|
| D | cavium-pip.txt | 36 - reg: The port number within the interface group.
|
| /linux-4.4.14/arch/cris/arch-v32/mm/ |
| D | mmu.S | 78 ; Bits 0-12 : Offset within a page
79 ; Bits 13-23 : PTE offset within a PMD
80 ; Bits 24-31 : PMD offset within the PGD
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | marvell.txt | 16 devices within the system controller chip. The node name begins
28 memory-mapped registers contained within the system controller
34 within the system controller chip.
36 registers within the system controller chip.
101 and the second level describes up to 3 ethernet nodes within
103 registers for the node are interleaved within a single set
135 within the silicon block the device uses.
|
| /linux-4.4.14/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 116 should travel to the host within one USB transaction need to be written to
124 allocated within one MOST frame, is calculated that fit into _one_ 512 byte
129 This frame_size is the number of synchronous data within an USB transaction,
134 packets within one USB transaction. This renders
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | topology.txt | 46 The ARM CPU topology is defined within the cpu-map node, which is a direct
79 be defined within the cpu-map node and every core/thread in the system
80 must be defined within the topology. Any other configuration is
90 are siblings within a single common parent node must be given a unique and
104 Description: must be declared within a cpu-map node, one node
|
| D | arm,scpi.txt | 41 limits but only discrete points within the range. The firmware
46 range within the specified range. The firmware provides the
47 range of values within a specified range.
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-calling.txt | 51 doesn't handle the completed call within the timeout specified, the firmware
61 and clear all the flags. If the driver does not perform this task within the
|
| D | README.vbi | 12 all lines can be stored while still fitting within the maximum allowed size.
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | interrupts.txt | 47 index of the interrupt within the controller.
70 index of the interrupt within the controller, while the second cell is used
|
| D | samsung,exynos4210-combiner.txt | 25 * Second Cell: Interrupt number within the group.
|
| D | brcm,bcm2835-armctrl-ic.txt | 25 The 2nd cell contains the interrupt number within the bank. Valid values
|
| /linux-4.4.14/Documentation/devicetree/bindings/rtc/ |
| D | atmel,at91sam9-rtc.txt | 11 encode the offset within the GPBR block (or in other words, the
|
| /linux-4.4.14/arch/tile/gxio/ |
| D | Kconfig | 7 # Support direct access to the common I/O DMA facility within the
|
| /linux-4.4.14/drivers/mcb/ |
| D | Kconfig | 12 FPGA based devices. It is used to identify MCB based IP-Cores within
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/msm/ |
| D | qcom,kpss-acc.txt | 4 There is one ACC register region per CPU within the KPSS remapped region as
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
| D | clockdomain.txt | 18 - clocks : link phandles of clocks within this domain
|
| /linux-4.4.14/arch/openrisc/ |
| D | TODO.openrisc | 2 since 2.6.35. There are, however, remaining items to be completed within
|
| /linux-4.4.14/drivers/ptp/ |
| D | Kconfig | 16 be used to achieve synchronization within a few dozen
19 synchronization to within a few hundred nanoseconds.
|
| /linux-4.4.14/Documentation/trace/ |
| D | tracepoint-analysis.txt | 15 what is going on within the system. There are a large number of methods for
218 There may also be a requirement to identify what functions within a program
219 were generating events within the kernel. To begin this sort of analysis, the
257 within the VDSO. With simple binaries, this will often be the case so let's
300 To see where within the function pixmanFillsse2 things are going wrong:
|
| D | tracepoints.txt | 120 within an if statement with the following:
134 false otherwise. The trace_<tracepoint>() should always be within the
|
| /linux-4.4.14/drivers/media/usb/au0828/ |
| D | Kconfig | 29 capture within the au0828 driver.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 12 within a processor subsystem, and there can be more than one line going to a
30 A Mailbox device node is used to represent a Mailbox IP instance within a SoC.
51 - ti,mbox-num-fifos: Number of h/w fifo queues within the mailbox IP block
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic-timer.txt | 12 all timers within the group can be used.
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | persistent-data.txt | 46 copy-on-write) or allocating a fresh one. Shadowing is elided within
63 its own data within the space it's managing.
|
| D | linear.txt | 11 <offset>: Starting sector within the device.
|
| D | striped.txt | 16 <offset>: Starting sector within the device.
|
| D | dm-flakey.txt | 24 <offset>: Starting sector within the device.
|
| D | zero.txt | 13 write data anywhere within the sparse device and read it back like a normal
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | transactional_memory.txt | 48 transactional or non-transactional accesses within the system. In this
77 Syscalls made from within an active transaction will not be performed and the
81 Syscalls made from within a suspended transaction are performed as normal and
198 in parts within transactions.
|
| /linux-4.4.14/fs/bfs/ |
| D | Kconfig | 10 on your /stand slice from within Linux. You then also need to say Y
|
| /linux-4.4.14/Documentation/devicetree/bindings/mmc/ |
| D | sunxi-mmc.txt | 21 please refer to mmc.txt within this directory
|
| D | fsl-imx-esdhc.txt | 35 tuning step can't find the proper delay window within limited tuning retries.
|
| /linux-4.4.14/Documentation/devicetree/bindings/pwm/ |
| D | pwm-tipwmss.txt | 11 physical address map of child's base address, physical address within
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | qcom-rpm.txt | 42 - u32 representing offset to the register within the syscon
43 - u32 representing the ipc bit within the register
140 The regulator node houses sub-nodes for each regulator within the device. Each
|
| D | twl6040.txt | 36 Optional properties within vibra { } section:
|
| D | qcom,spmi-pmic.txt | 7 locations/definitions within these regions, with some of these regions
|
| /linux-4.4.14/tools/perf/config/ |
| D | utilities.mak | 46 # Use this to escape newlines from within a shell call;
62 # Use this to unescape newlines from within a shell call;
109 # within the context of a command line of a makefile rule
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 10 - reg: Port-id within a given master
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-bus-firewire | 35 Specifier_id and version within each tuple are separated
66 Offset of the unit directory within the parent device's
|
| D | sysfs-module | 24 placed in this location within sysfs. See the
|
| D | vdso | 9 within their rights to crash.) In addition, if you pass a bad
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.debug | 44 Do not output any debug BUG messages within the kernel.
|
| /linux-4.4.14/arch/arm/common/ |
| D | vlock.S | 58 @ r1: CPU ID (0-based index within cluster)
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/fsl/ |
| D | qman.txt | 15 DPAA logic modules, maintains packet ordering within flows. Besides providing
31 Definition: Registers region within the CCSR address space
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | fiemap.txt | 13 A fiemap request is encoded within struct fiemap:
29 fm_start, and fm_length specify the logical range within the file
65 Extent information is returned within the embedded fm_extents array
155 Data is located within a meta data block.
|
| D | seq_file.txt | 21 position within the virtual file - that position is, likely as not, in the
177 The seq_file code manages positioning within the output created by the
219 So far, we have a nice set of functions which can produce output within the
221 can see. Creating a file within the kernel requires, of course, the
318 These helpers will interpret pos as a position within the list and iterate
|
| D | afs.txt | 85 volume location servers within that cell, with the latter separated by colons.
145 servers, volumes, and active servers known within that cell.
224 to my internal DNS. My "root.afs" partition has a mount point within it for
|
| D | ubifs.txt | 18 2 MTD devices support 3 main operations - read from some offset within an
19 eraseblock, write to some offset within an eraseblock, and erase a whole
|
| /linux-4.4.14/block/partitions/ |
| D | Kconfig | 133 partitions from within Linux if you have also said Y to "UFS
152 partitions from within Linux if you have also said Y to "UFS
162 VTOC and further mount UnixWare partitions read-only from within
232 within Linux if you have also said Y to "UFS file system support",
|
| /linux-4.4.14/Documentation/namespaces/ |
| D | compatibility-list.txt | 25 within the namespace it was obtained in and may refer to some
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/exynos/ |
| D | exynos_hdmi.txt | 14 b) pin number within the gpio controller.
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | isp.doc | 101 to access the functions within the ISP. Since the isp.sa hex file contains
119 the entry code jumps to the appropriate emulation code within the code section.
193 supply new emulation code. This new emulation code should reside within
|
| /linux-4.4.14/net/ipv6/ |
| D | Kconfig | 162 Tunneling means encapsulating data of one protocol type within
175 Tunneling means encapsulating data of one protocol type within
219 Tunneling means encapsulating data of one protocol type within
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | mvebu-mbus.txt | 20 the second cell for the address offset within the window.
30 within the internal register window (see below).
83 the window ID and the second one for the offset within the window.
|
| D | renesas,bsc.txt | 4 The Renesas Bus State Controller (BSC, sometimes called "LBSC within Bus
|
| /linux-4.4.14/Documentation/fault-injection/ |
| D | fault-injection.txt | 91 in the walked stacktrace lies within the required range, and
92 none lies within the rejected range.
99 for a caller within [require-start,require-end) OR
|
| /linux-4.4.14/net/dccp/ccids/ |
| D | Kconfig | 21 within a factor of two of the sending rate of a TCP flow under the
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-ali1535 | 23 within the part have moved and some have been redefined slightly.
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 46 Represents the "Flipper" interrupt controller within the "Hollywood" chip.
141 Represents the "Hollywood" interrupt controller within the
|
| /linux-4.4.14/Documentation/devicetree/bindings/remoteproc/ |
| D | wkup_m3_rproc.txt | 13 within the SoC. It is added as a child node of the parent interconnect bus
|
| /linux-4.4.14/Documentation/devicetree/bindings/misc/ |
| D | sram.txt | 26 within the sram to bus addresses
|
| /linux-4.4.14/drivers/iio/ |
| D | Kconfig | 16 bool "Enable buffer support within IIO"
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | ti,omap-iommu.txt | 26 number (0-indexed) within the sub-system. This property
|
| /linux-4.4.14/Documentation/devicetree/bindings/display/ |
| D | atmel,lcdc.txt | 22 - default-mode: a videomode within the display with timing parameters
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | wdt.txt | 11 to within a timeout or the machine will reboot. Each write delays the reboot
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | overview.txt | 31 on an x86-compatible system can work within this paradigm. Of course,
53 Note first that the struct device dev within the struct pci_dev is
|
| /linux-4.4.14/drivers/pinctrl/sh-pfc/ |
| D | Kconfig | 20 This enables support for GPIOs within the SoC's pin function
|
| /linux-4.4.14/firmware/ |
| D | README.AddingFirmware | 36 within the company that owns the code).
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-diff.txt | 120 baseline entry, are displayed with empty space within baseline column
177 - period_percent being the % of the hist entry period value within
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | overview.txt | 117 Power Domain: is the new current limit within the domain
121 Regulator Domains: is the new current limit within the
|
| /linux-4.4.14/Documentation/gpio/ |
| D | board.txt | 120 - chip_hwnum is the hardware number of the GPIO within the chip
126 - idx is the index of the GPIO within the function.
|
| /linux-4.4.14/Documentation/power/ |
| D | swsusp-dmcrypt.txt | 29 always the same major/minor within the initrd as well as
30 within your running system. The easiest way to achieve this is
|
| /linux-4.4.14/Documentation/hid/ |
| D | hiddev.txt | 75 returns to hiddev.c the individual usages that have changed within
86 within <linux/hiddev.h>, along with some other useful #defines and
168 given its report type, report id, field index, and index within the
|
| /linux-4.4.14/Documentation/serial/ |
| D | tty.txt | 29 discipline. The reference count of the tty_ldisc structure within a tty
31 counts the number of threads of execution within an ldisc method (plus those
131 hardware driver through the function pointers within the tty->driver
252 fail in this situation if used within these functions. Ldisc and driver
|
| D | moxa-smartio | 129 Each port within the same multiport board shares the same IRQ. Up to
321 assign it within driver's source code. If you will not
332 c. Change the address within this array using vi. For
395 within the shell script "msmknod". First, you have to open "msmknod"
501 Each port within the same multiport board shares the same IRQ. Please set
|
| /linux-4.4.14/Documentation/rapidio/ |
| D | rapidio.txt | 18 bus types and registering them within the device model.
58 ports towards their final destination. The packet destination port within a
74 master port that is used to communicate with devices within the network.
96 register at least one master port within the RapidIO network. To register mport
97 within the subsystem controller driver's initialization code calls function
|
| /linux-4.4.14/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 102 interrupts within specified range from 'minvec' to 'maxvec'.
126 interrupts within a range. See chapter 4.3.1.3 to get the idea how to
252 MSI-X interrupts within specified range from 'minvec' to 'maxvec'.
282 interrupts within a range. E.g., an network adapter might need let's say
286 (since it can allocate any number within the range, without any notion of
334 number of MSI-X interrupts within a range. E.g., let's assume a device that
450 The MSI-X capability specifies a BAR and offset within that BAR for the
|
| /linux-4.4.14/drivers/virtio/ |
| D | Kconfig | 47 of memory within a KVM guest.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | partition.txt | 26 - reg : The partition's offset and size within the mtd bank.
|
| /linux-4.4.14/drivers/staging/wilc1000/ |
| D | Kconfig | 46 within the chip as well as configure the WILC1000 for data DMA.
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| D | spi-davinci.txt | 21 IP to the interrupt controller within the SoC. Possible values
|
| /linux-4.4.14/Documentation/devicetree/bindings/soc/ |
| D | qcom,smd-rpm.txt | 66 The regulator node houses sub-nodes for each regulator within the device. Each
|
| /linux-4.4.14/arch/x86/kernel/ |
| D | ftrace.c | 76 within(unsigned long addr, unsigned long start, unsigned long end) in within() function
91 if (within(ip, (unsigned long)_text, (unsigned long)_etext)) in text_ip_addr()
|