Searched full:at (Results 1 – 25 of 2201) sorted by relevance
12345678910>>...89
| /Documentation/admin-guide/media/ |
| D | dvb_references.rst | 9 The DVB mailing list linux-dvb is hosted at vger. Please see
12 There are also some other old lists hosted at:
14 reasons, please check the archive at https://linuxtv.org/pipermail/linux-dvb/.
16 The media subsystem Wiki is hosted at https://linuxtv.org/wiki/.
21 The API documentation is documented at the Kernel tree. You can find it
22 in both html and pdf formats, together with other useful documentation at:
26 You may also find useful material at https://linuxtv.org/downloads/.
29 a script at the kernel tree, at scripts/get_dvb_firmware.
|
| D | fimc.rst | 16 availability, LCD writeback support, etc. The driver is located at
31 - dynamic pipeline re-configuration at runtime (re-attachment of any FIMC
47 The driver supports Media Controller API as defined at :ref:`media_controller`.
51 to the SoC peripheral camera input at runtime and optionally to control internal
65 V4L2 memory-to-memory interface at /dev/video? device node. This is standalone
74 The driver supports V4L2 Video Capture Interface as defined at
77 At the capture and mem-to-mem video nodes only the multi-planar API is
84 node is also created per each available and enabled at the platform level
97 When we configure these devices through sub-device API at user space, the
102 devices belonging to the pipeline is done at the video node driver.
[all …]
|
| /Documentation/devicetree/bindings/mips/img/ |
| D | xilfpga.txt | 20 - 128Mbyte DDR RAM at 0x0000_0000
21 - 8Kbyte RAM at 0x1000_0000
22 - axi_intc at 0x1020_0000
23 - axi_uart16550 at 0x1040_0000
24 - axi_gpio at 0x1060_0000
25 - axi_i2c at 0x10A0_0000
26 - custom_gpio at 0x10C0_0000
27 - axi_ethernetlite at 0x10E0_0000
28 - 8Kbyte BootRAM at 0x1FC0_0000
39 A CPU sub-node is also required for at least CPU 0. Required properties:
[all …]
|
| /Documentation/hwmon/ |
| D | isl68137.rst | 14 Publicly available at the Renesas website
25 Publicly available (after August 2020 launch) at the Renesas website
35 Publicly available (after August 2020 launch) at the Renesas website
45 Publicly available (after August 2020 launch) at the Renesas website
55 Publicly available (after August 2020 launch) at the Renesas website
65 Publicly available (after August 2020 launch) at the Renesas website
75 Publicly available (after August 2020 launch) at the Renesas website
85 Publicly available (after August 2020 launch) at the Renesas website
95 Publicly available (after August 2020 launch) at the Renesas website
105 Publicly available (after August 2020 launch) at the Renesas website
[all …]
|
| D | lm90.rst | 12 Datasheet: Publicly available at the National Semiconductor website
22 Datasheet: Publicly available at the National Semiconductor website
32 Datasheet: Publicly available at the National Semiconductor website
42 Datasheet: Publicly available at the National Semiconductor website
52 Datasheet: Publicly available at the ON Semiconductor website
62 Datasheet: Publicly available at the ON Semiconductor website
72 Datasheet: Publicly available at the ON Semiconductor website
82 Datasheet: Publicly available at the ON Semiconductor website
92 Datasheet: Publicly available at the Maxim website
102 Datasheet: Publicly available at the Maxim website
[all …]
|
| D | lm75.rst | 12 Datasheet: Publicly available at the National Semiconductor website
22 Datasheet: Publicly available at the National Semiconductor website
32 Datasheet: Publicly available at the Maxim website
42 Datasheet: Publicly available at the Maxim website
52 Datasheet: Publicly available at the Microchip website
62 Datasheet: Publicly available at the Microchip website
72 Datasheet: Publicly available at the Analog Devices website
82 Datasheet: Publicly available at the ST website
92 Datasheet: Publicly available at the ST website
102 Datasheet: Publicly available at the Texas Instruments website
[all …]
|
| D | adm1021.rst | 12 Datasheet: Publicly available at the Analog Devices website
20 Datasheet: Publicly available at the Analog Devices website
36 Datasheet: Publicly available at the Maxim website
44 Datasheet: Publicly available at the Maxim website
52 Datasheet: Publicly available at the National Semiconductor website
60 Datasheet: Publicly available at the Philips website
68 Datasheet: Publicly available at the Philips website
76 Datasheet: Publicly available at the TI website
84 Datasheet: Publicly available at the Onsemi website
122 is read at least once. This means that the cause for the alarm may already
|
| D | adt7475.rst | 12 Datasheet: Publicly available at the On Semiconductors website
20 Datasheet: Publicly available at the On Semiconductors website
28 Datasheet: Publicly available at the On Semiconductors website
36 Datasheet: Publicly available at the On Semiconductors website
128 - point1: Set the PWM speed at the lower temperature bound
129 - point2: Set the PWM speed at the higher temperature bound
136 for a channel at a given time, in which case the maximum value (fastest
142 At Tmin - hysteresis the PWM output can either be off (0% duty cycle) or at the
145 off. A value of 1 means the fans will run at auto_point1_pwm.
|
| D | ad7314.rst | 10 Datasheet: Publicly available at Analog Devices website.
16 Datasheet: Publicly available at Analog Devices website.
22 Datasheet: Publicly available at Analog Devices website.
|
| /Documentation/misc-devices/ |
| D | eeprom.rst | 28 24C01 1K 0x50 (shadows at 0x51 - 0x57)
32 (additional data at 0x51, 0x53, 0x55, 0x57)
33 24C08 8K 0x50, 0x54 (additional data at 0x51, 0x52,
35 24C16 16K 0x50 (additional data at 0x51 - 0x57)
38 Atmel 34C02B 2K 0x50 - 0x57, SW write protect at 0x30-37
39 Catalyst 34FC02 2K 0x50 - 0x57, SW write protect at 0x30-37
40 Catalyst 34RC02 2K 0x50 - 0x57, SW write protect at 0x30-37
41 Fairchild 34W02 2K 0x50 - 0x57, SW write protect at 0x30-37
42 Microchip 24AA52 2K 0x50 - 0x57, SW write protect at 0x30-37
43 ST M34C02 2K 0x50 - 0x57, SW write protect at 0x30-37
[all …]
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 44 descriptor pointer (GDACTDPA). The GDACTDPA points at the descr
53 hardware is ahead, the tail pointer will be pointing at a "full"
63 When traffic is flowing, then the head pointer will be pointing at
71 pointer, at which point the OS will notice that the head descr is
75 all be pointing at the same descr, which should be "empty". All of the
80 of the ring, starting at the tail pointer, and listing the status
86 net eth1: Chain tail located at descr=20
87 net eth1: Chain head is at 20
88 net eth1: HW curr desc (GDACTDPA) is at 21
90 net eth1: HW next desc (GDACNEXTDA) is at 22
[all …]
|
| /Documentation/virt/kvm/ |
| D | nested-vmx.rst | 23 available at:
225 - Abel Gordon, abelg <at> il.ibm.com
226 - Nadav Har'El, nyh <at> il.ibm.com
227 - Orit Wasserman, oritw <at> il.ibm.com
228 - Ben-Ami Yassor, benami <at> il.ibm.com
229 - Muli Ben-Yehuda, muli <at> il.ibm.com
232 - Anthony Liguori, aliguori <at> us.ibm.com
233 - Mike Day, mdday <at> us.ibm.com
234 - Michael Factor, factor <at> il.ibm.com
235 - Zvi Dubitzky, dubi <at> il.ibm.com
[all …]
|
| /Documentation/arm64/ |
| D | perf.rst | 15 Userspace always runs at EL0 and thus this attribute will exclude EL0.
23 The kernel runs at EL2 with VHE and EL1 without. Guest kernels always run
24 at EL1.
42 hypervisor to be any code that runs at EL2 which is predominantly used for
54 The KVM host may run at EL0 (userspace), EL1 (non-VHE kernel) and EL2 (VHE
57 The KVM guest may run at EL0 (userspace) and EL1 (kernel).
81 transition at EL2 - however there is a period of time between
86 window at the guest entry/exit where host events are not captured.
|
| /Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 11 file at first.
20 翻訳者： Tsugikazu Shibata <tshibata at ab dot jp dot nec dot com>
21 校正者： 武井伸光さん、<takei at webmasters dot gr dot jp>
22 かねこさん (Seiji Kaneko) <skaneko at a2 dot mbn dot or dot jp>
23 小林 雅典さん (Masanori Kobayasi) <zap03216 at nifty dot ne dot jp>
24 野口さん (Kenji Noguchi) <tokyo246 at gmail dot com>
25 神宮信太郎さん <jin at libjingu dot jp>
|
| /Documentation/vm/ |
| D | zswap.rst | 38 Whether Zswap is enabled at the boot time depends on whether
42 Zswap can also be enabled and disabled at runtime using the sysfs interface.
43 An example command to enable zswap at runtime, assuming sysfs is mounted
44 at ``/sys``, is::
48 When zswap is disabled at runtime it will stop storing pages that are
70 but it can be overridden at boot time by setting the ``zpool`` attribute,
71 e.g. ``zswap.zpool=zbud``. It can also be changed at runtime using the sysfs
104 Kconfig option, but it can be overridden at boot time by setting the
106 It can also be changed at runtime using the sysfs "compressor"
111 When the zpool and/or compressor parameter is changed at runtime, any existing
[all …]
|
| /Documentation/filesystems/ |
| D | sharedsubtree.rst | 59 The above command replicates the mount at /mnt to the mountpoint /tmp
70 Now let's say we mount a device at /tmp/a::
80 Note that the mount has propagated to the mount at /mnt as well.
99 the new mount at /tmp becomes a shared mount and it is a replica of
100 the mount at /mnt.
102 Now let's make the mount at /tmp; a slave of /mnt
114 Note the mount event has propagated to the mount at /tmp
116 However let's see what happens if we mount something on the mount at /tmp
125 Note how the mount event has not propagated to the mount at
136 let's say we have a mount at /mnt and we make it unbindable::
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 9 the link into hibernate state. That will save power at the
20 the descriptor could be found at UFS specifications 2.1.
29 the descriptor could be found at UFS specifications 2.1.
38 about the descriptor could be found at UFS specifications 2.1.
48 at UFS specifications 2.1.
57 about the descriptor could be found at UFS specifications 2.1.
67 at UFS specifications 2.1.
77 be found at UFS specifications 2.1.
88 be found at UFS specifications 2.1.
98 about the descriptor could be found at UFS specifications 2.1.
[all …]
|
| D | sysfs-bus-iio-counter-104-quad-8 | 31 counter freezes at count = preset when counting up, and
32 at count = 0 when counting down. At either of these
44 The counter is reset to 0 at count = preset when
46 value at count = 0 when counting down; the counter does
47 not freeze at the bundary points, but counts
57 present at the channel Y count inputs in quadrature clock mode;
122 A logic low level is the active level at this index
|
| /Documentation/doc-guide/ |
| D | parse-headers.rst | 9 if a symbol is not found at the documentation. That helps to keep the
70 The output is written at the (OUT_FILE).
110 at C_FILE.
116 The ignore or replace statement will apply to typedef statements at C_FILE.
123 at C_FILE.
130 at C_FILE.
137 at C_FILE.
142 also be explicitly defined at the replace statement.
153 Ignore a #define _VIDEODEV2_H at the C_FILE.
173 symbol at the C domain.
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-mhi | 6 using a BHI (Boot Host Interface) register read after at least
8 without having the device power on at least once, the file will
18 at least one attempt to power up the device has been done. If
19 read without having the device power on at least once, the file
|
| /Documentation/staging/ |
| D | crc32.rst | 34 Just like with ordinary division, you proceed one digit (bit) at a time.
53 Notice how, to get at bit 32 of the shifted remainder, we look
54 at bit 31 of the remainder *before* shifting it.
59 Also, to add the CRC to a message, we need a 32-bit-long hole for it at
60 the end, so we have to add 32 extra cycles shifting in zeros at the
89 We can do it 8 bits at a time rather than 1 bit at a time::
110 word at a time and increase the inner loop count to 32.
113 bulk of a message byte-at-a-time and adding bit-at-a-time processing
114 for any fractional bytes at the end.
117 the byte-at-a-time table method, popularized by Dilip V. Sarwate,
[all …]
|
| /Documentation/x86/ |
| D | pti.rst | 29 enabled by setting CONFIG_PAGE_TABLE_ISOLATION=y at compile time.
30 Once enabled at compile-time, it can be disabled at boot with the
57 This sharing at the PGD level also inherently shares all the lower
66 this protection comes at a cost:
80 must be done at interrupt, syscall, and exception entry
83 cycles, and are required at every entry and exit.
88 that stacks must be switched at entry time.
98 are changed. This makes switching the page tables (at context
109 and one for the entry/exit structures. At fork(), we need to
131 2. Allow PTI to be enabled/disabled at runtime in addition to the
[all …]
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | memcg_test.rst | 22 Allocated at boot or memory hotplug. Freed at memory hot removal.
26 Allocated at swapon(). Freed at swapoff().
34 a page/swp_entry may be charged (usage += PAGE_SIZE) at
58 At try_charge(), there are no flags to say "this page is charged".
59 at this point, usage += PAGE_SIZE.
61 At commit(), the page is associated with the memcg.
63 At cancel(), simply usage -= PAGE_SIZE.
70 Anonymous page is newly allocated at
75 At swap-in, the page is taken from swap-cache. There are 2 cases.
82 At swap-out, typical state transition is below.
[all …]
|
| D | hugetlb.rst | 10 visible at /sys/fs/cgroup. At bootup, this group includes all the tasks in
71 doesn't support page reclaim, enforcing the limit at page fault time implies
87 group and enforces the controller limit at reservation time and at the fault of
89 enforced at reservation time (on mmap or shget), reservation limits never causes
92 limit, enforcing memory usage at fault time and causing the application to
96 reservation limits are enforced at reservation time (on mmap or shget), and
131 harder to reparent reservations at offline time.
|
| /Documentation/scsi/ |
| D | scsi-generic.rst | 36 The most recent documentation of the sg driver is kept at the Linux
44 and pdf. This document can also be found at:
49 be found at http://sg.danny.cz/sg/. A larger version
50 is at: http://sg.danny.cz/sg/p/scsi-generic_long.txt.
53 found at http://www.torque.net/sg/p/original/SCSI-Programming-HOWTO.txt
60 can be found at the top of the /usr/src/linux/drivers/scsi/sg.c file.
63 part can be found at http://www.tldp.org/HOWTO/SCSI-2.4-HOWTO .
77 capabilities. They can be found at: http://sg.danny.cz/sg/sg3_utils.html and
80 Another approach is to look at the applications that use the sg driver.
|
12345678910>>...89