Searched full:here (Results 1 – 25 of 877) sorted by relevance
12345678910>>...36
| /Documentation/gpu/rfc/ |
| D | i915_small_bar.h | 20 * here, also note that no current region type will ever return -1 here.
30 * Without this (or if this is an older kernel) the value here will
32 * for I915_MEMORY_CLASS_DEVICE regions (for other types the value here
55 * value here will always equal the @probed_size).
57 * Note that if the value returned here is zero, then
75 * value here will always equal the
79 * accounting. Without this the value here will always
82 * regions (for other types the value here will also
85 * If this is an older kernel the value here will be
97 * Note that new buffer flags should be added here, at least for the stuff that
[all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 14 Danielsson <pvrusb2@dax.nu> whose web page can be found here:
20 here.
67 here for comments that explain how to do that.
83 here. Hotplugging is ultimately coordinated here. All high level
123 will work through here.
128 within the jurisdiction of pvrusb-context not here).
141 compatible commands to the I2C modules. It is here where state
146 compatible commands to the I2C modules. It is here where state
154 through here that other V4L modules can reach into this driver to
169 however the underlying architecture here was intended to allow for
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-powercap | 16 Here <control type> determines how the power is going to be
92 constraint can have an optional name. Here "X" can have values
102 Here "X" can have values from 0 to max integer.
111 Here "X" can have values from 0 to max integer.
120 Here "X" can have values from 0 to max integer.
128 Here "X" can have values from 0 to max integer.
136 constraint. Here "X" can have values from 0 to max integer.
144 constraint. Here "X" can have values from 0 to max integer.
|
| D | sysfs-class-iommu | 7 given IOMMU here to allow association of IOMMU to
16 given device here to allow association of device to
|
| D | configfs-iio | 20 High resolution timers directory. Creating a directory here
33 Dummy IIO devices directory. Creating a directory here will result
|
| D | debugfs-ec | 9 the EC here (XY -> GPE number from `/sys/kernel/debug/ec/*/gpe`):
12 The io file is binary and a userspace tool located here:
|
| D | debugfs-pfo-nx-crypto | 15 only errors counted here are those returned from the hcall, H_COP_OP.
19 recorded here (the hcall will retry until -EBUSY goes away).
|
| /Documentation/arch/arm/ |
| D | memory.rst | 34 The CPU vectors are mapped here if the
49 by fix_to_virt() will be located here.
63 located here through iotable_init().
78 placed here using dynamic mappings.
82 of the memory is shadowed here with 1 bit
86 Per-thread mappings are placed here via
91 place their vector page here. NULL pointer
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | mc-peripheral-props.yaml | 15 those properties are listed here. The controller specific properties
17 from here.
34 # The controller specific properties go here.
|
| /Documentation/admin-guide/ |
| D | index.rst | 7 organization here — this material was not written to be a single, coherent
32 Here is a set of documents aimed at users who are trying to track down
54 ABI will be found here.
65 subsystems expectations will be found here.
|
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_apis.rst | 9 The APIs described here **should not** be used on new drivers or applications.
16 The APIs described here doesn't necessarily reflect the current
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-tipwmss.txt | 33 /* child nodes go here */
46 /* child nodes go here */
57 /* child nodes go here */
|
| /Documentation/userspace-api/media/rc/ |
| D | rc-protos.rst | 33 detailed description here https://www.sbprojects.net/knowledge/ir/rc5.php.
183 described here https://www.sbprojects.net/knowledge/ir/jvc.php.
279 described here https://www.sbprojects.net/knowledge/ir/nec.php. Note
354 This is the rc-6 in mode 0. rc-6 is described here
362 This is the rc-6 in mode 6a, 20 bits. rc-6 is described here
370 This is the rc-6 in mode 6a, 24 bits. rc-6 is described here
378 This is the rc-6 in mode 6a, 32 bits. rc-6 is described here
397 This is a protocol used by Sharp VCRs, is described here
431 The rc-mm protocol is described here
438 The rc-mm protocol is described here
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | microchip,mcp3564.yaml | 14 Delta-Sigma ADCs with an SPI interface. Datasheet can be found here:
15 Datasheet for MCP3561, MCP3562, MCP3564 can be found here:
17 Datasheet for MCP3561R, MCP3562R, MCP3564R can be found here:
19 Datasheet for MCP3461, MCP3462, MCP3464 can be found here:
21 Datasheet for MCP3461R, MCP3462R, MCP3464R can be found here:
|
| /Documentation/translations/zh_CN/maintainer/ |
| D | pull-requests.rst | 81 Here is the big char/misc patch set for the 4.15-rc1 merge window.
82 Contained in here is the normal set of new functions added to all
104 Signed-off-by: Your-name-here <your_email@domain>
|
| /Documentation/driver-api/tty/ |
| D | tty_driver.rst | 25 For reference, both allocation and deallocation functions are explained here in
34 Here comes the documentation of flags accepted by tty_alloc_driver() (or
102 The linking routines are documented here:
113 All members of struct tty_driver are documented here. The required members are
|
| /Documentation/ |
| D | subsystem-apis.rst | 8 from the point of view of a kernel developer. Much of the information here
66 **Fixme**: much more organizational work is needed here.
|
| D | conf.py | 42 # add these directories to sys.path here. If the directory is relative to the
43 # documentation root, use os.path.abspath to make it absolute, like shown here.
49 # If your documentation needs a minimal Sphinx version, state it here.
52 # Add any Sphinx extension module names here, as strings. They can be
162 # Add any paths that contain templates here, relative to this directory.
293 # Add any paths that contain custom static files (such as style sheets) here,
345 # Add any paths that contain custom static files (such as style sheets) here,
533 # FIXME: Do not add the index file here; the result will be too big. Adding
534 # multiple PDF files here actually tries to get the cross-referencing right
|
| /Documentation/bpf/ |
| D | prog_flow_dissector.rst | 49 +-- flow dissector starts here
67 +-- flow dissector starts here
86 +-- flow dissector starts here
98 The takeaway here is as follows: BPF flow dissector program can be called with
|
| /Documentation/networking/ |
| D | team.rst | 7 Team devices are driven from userspace via libteam library which is here:
|
| D | net_failover.rst | 38 Here is an example libvirt XML snippet that shows such configuration:
67 The second device definition is for the VF passthrough interface. Here the
87 Here, ens10 is the 'failover' master interface, ens10nsby is the slave 'standby'
90 One point to note here is that some user space network configuration daemons
120 Here is a sample script that shows the steps to initiate live migration from
|
| /Documentation/timers/ |
| D | timers-howto.rst | 40 There are a few more options here, while any of them may
77 Explained originally here:
100 tolerances here are very situation specific, thus it
|
| /Documentation/driver-api/80211/ |
| D | mac80211.rst | 26 programming model should be in here, including the definition of
70 appropriate chapter, a BIG FAT note should be here about this though and
80 what should be here
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 49 so outline what is contained here, why it should be merged, and what, if
95 Here is the big char/misc patch set for the 4.15-rc1 merge window.
96 Contained in here is the normal set of new functions added to all
118 Signed-off-by: Your-name-here <your_email@domain>
148 can be used here instead as well (but note that some people behind
|
| /Documentation/admin-guide/acpi/ |
| D | index.rst | 5 Here we document in detail how to interact with various mechanisms in
|
12345678910>>...36