Searched full:custom (Results 1 – 25 of 222) sorted by relevance
123456789
| /Documentation/userspace-api/media/cec/ |
| D | cec-pin-error-inj.rst | 53 # tx-custom-low-usecs <usecs> define the 'low' time for the custom pulse
54 # tx-custom-high-usecs <usecs> define the 'high' time for the custom pulse
55 # tx-custom-pulse transmit the custom pulse once the bus is idle
64 # <op>[,<mode>] tx-custom-bit <bit> send the custom pulse instead of this bit
67 # <op>[,<mode>] tx-custom-start send the custom pulse instead of the start pulse
95 to create custom pulses on the CEC bus.
307 Custom Pulses
310 ``tx-custom-low-usecs <usecs>``
311 This defines the duration in microseconds that the custom pulse pulls
314 ``tx-custom-high-usecs <usecs>``
[all …]
|
| /Documentation/devicetree/bindings/iio/temperature/ |
| D | adi,ltc2983.yaml | 108 9 - Custom Thermocouple
128 adi,custom-thermocouple:
130 Used for digitizing custom thermocouples.
147 - adi,custom-thermocouple
214 18 - RTD Custom
254 adi,custom-rtd:
256 Used for digitizing custom RTDs.
291 - adi,custom-rtd
308 26 - Thermistor Custom Steinhart-Hart
309 27 - Custom Thermistor
[all …]
|
| /Documentation/driver-api/firmware/ |
| D | fw_search_path.rst | 15 to activate the first optional custom fw_path_para. The custom path can
25 You would echo into it your custom path and firmware requested will be searched
|
| D | fallback-mechanisms.rst | 12 CONFIG_FW_LOADER_USER_HELPER_FALLBACK is disabled, only the custom fallback
20 informing the kernel that you have a custom fallback mechanism and it will
61 * Custom fallback mechanism
164 Firmware custom fallback mechanism
185 but you want to suppress kobject uevents, as you have a custom solution which
187 load firmware for you through a custom path.
196 The logic behind using MAX_JIFFY_OFFSET for non-uevents is that a custom
|
| D | lookup-order.rst | 19 is issued or the custom firmware loading is relied upon for firmware
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-power-wilco | 17 Custom:
32 Used when charge_type="Custom", as described above. Measured in
39 Used when charge_type="Custom", as described above. Measured in
|
| /Documentation/security/tpm/ |
| D | tpm_event_log.rst | 37 a custom configuration table defined by the stub itself. Unfortunately,
46 final events table size while the stub is still running to the custom
48 concatenating two halves of the event log from the custom configuration table
|
| /Documentation/networking/ |
| D | xdp-rx-metadata.rst | 46 | headroom | custom metadata | data |
73 | headroom | custom metadata | data |
84 contents. Currently, every driver has custom kernel code to parse
103 This means that for redirected packets only custom metadata is
108 that will also only have access to the custom metadata.
|
| /Documentation/hwmon/ |
| D | sch5636.rst | 20 their own custom hwmon solution based upon the SCH5636.
24 it is dealing with a Fujitsu Theseus and not with another custom SCH5636 based
|
| D | powerz.rst | 24 The device communicates with the custom protocol over USB.
|
| D | pm6764tr.rst | 27 custom configurations. The PM6764TR device features up to 4-phase programmable operation.
|
| /Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 48 their own custom extensions. These custom extensions aren't required
59 code for any custom extensions that they wish.)
|
| /Documentation/arch/arm/omap/ |
| D | omap.rst | 11 v4.3+ Update is needed for custom .config files to make sure
15 v4.18+ Update is needed for custom .config files to make sure
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | adi,ad3552r.yaml | 83 custom-output-range-config:
86 description: Configuration of custom range when
123 # custom-output-range-config must be used
128 - custom-output-range-config
232 custom-output-range-config {
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | tplink,safeloader-partitions.yaml | 15 a custom ASCII-based format. That format was first found in TP-Link
16 devices with a custom SafeLoader bootloader. Later it was adapted to
|
| /Documentation/dev-tools/kunit/api/ |
| D | resource.rst | 10 state on a per-test basis, register custom cleanup actions, and more.
|
| /Documentation/devicetree/bindings/media/ |
| D | si4713.txt | 5 and a digital interface, which supports I2S, left-justified and a custom
|
| /Documentation/sphinx/ |
| D | kerneldoc-preamble.sty | 18 % Custom width parameters for TOC
137 % Define custom macros to on/off CJK
141 % Define custom macros for switching CJK font setting
205 % Custom macros to on/off CJK and switch CJK fonts (Dummy)
|
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 41 They also allow to call a custom constructor function when a non-zero
61 - initialize the variable using a custom constructor and data when provided
74 - initialize the variable using a custom constructor and data when provided
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_build.rst | 30 To build both static libbpf.a and shared libbpf.so against a custom libelf
|
| /Documentation/devicetree/bindings/display/ |
| D | elgin,jg10309-01.yaml | 14 board and is a custom display.
|
| /Documentation/devicetree/bindings/reset/ |
| D | snps,axs10x-reset.yaml | 13 This binding describes the ARC AXS10x boards custom IP-block which allows
|
| /Documentation/driver-api/memory-devices/ |
| D | ti-gpmc.rst | 50 custom timing routines, a kind of reverse engineering without
52 in mainline having custom timing routine) and by simulation.
|
| /Documentation/filesystems/nfs/ |
| D | rpc-server-gss.rst | 49 The classic upcall mechanism uses a custom text based upcall mechanism
50 to talk to a custom daemon called rpc.svcgssd that is provide by the
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | motorola,cpcap-adc.yaml | 13 On Motorola phones like droid 4 there is a custom CPCAP PMIC. This PMIC
|
123456789