| /linux-6.12.1/arch/arm64/boot/dts/renesas/ |
| D | gmsl-cameras.dtsi | 35 #if !defined(GMSL_CAMERA_RDACM20) && !defined(GMSL_CAMERA_RDACM21)
36 #error "Camera model should be defined by the board file"
39 #if defined(GMSL_CAMERA_RDACM20) && defined(GMSL_CAMERA_RDACM21)
43 #if !defined(GMSL_CAMERA_0) && !defined(GMSL_CAMERA_1) && \
44 !defined(GMSL_CAMERA_2) && !defined(GMSL_CAMERA_3) && \
45 !defined(GMSL_CAMERA_4) && !defined(GMSL_CAMERA_5) && \
46 !defined(GMSL_CAMERA_6) && !defined(GMSL_CAMERA_7)
51 #if defined(GMSL_CAMERA_0) || defined(GMSL_CAMERA_1) || \
52 defined(GMSL_CAMERA_2) || defined(GMSL_CAMERA_3)
56 #if defined(GMSL_CAMERA_4) || defined(GMSL_CAMERA_5) || \
[all …]
|
| /linux-6.12.1/Documentation/arch/riscv/ |
| D | hwprobe.rst | 7 is defined in <asm/hwprobe.h>::
22 will be cleared to -1, and its value set to 0. The CPU set is defined by
46 The following keys are defined:
49 as defined by the RISC-V privileged architecture specification.
52 defined by the RISC-V privileged architecture specification.
55 defined by the RISC-V privileged architecture specification.
59 are defined:
62 rv64ima, as defined by version 2.2 of the user ISA and version 1.10 of the
75 defined by commit cd20cee ("FMIN/FMAX now implement
78 * :c:macro:`RISCV_HWPROBE_IMA_C`: The C extension is supported, as defined
[all …]
|
| D | acpi.rst | 7 The ISA string parsing rules for ACPI are defined by `Version ASCIIDOC
8 Conversion, 12/2022 of the RISC-V specifications, as defined by tag
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 146 The controller and driver support a mix of IEEE standard defined statistics,
147 RFC defined statistics, and driver or Altera defined statistics. The four
158 "tx_packets" is equivalent to aFramesTransmittedOK defined in IEEE 802.3-2012,
162 "rx_packets" is equivalent to aFramesReceivedOK defined in IEEE 802.3-2012,
167 "rx_crc_errors" is equivalent to aFrameCheckSequenceErrors defined in IEEE
172 "rx_align_errors" is equivalent to aAlignmentErrors defined in IEEE 802.3-2012,
177 "tx_bytes" is equivalent to aOctetsTransmittedOK defined in IEEE 802.3-2012,
181 "rx_bytes" is equivalent to aOctetsReceivedOK defined in IEEE 802.3-2012,
185 "tx_pause" is equivalent to aPAUSEMACCtrlFramesTransmitted defined in IEEE
189 "rx_pause" is equivalent to aPAUSEMACCtrlFramesReceived defined in IEEE
[all …]
|
| /linux-6.12.1/scripts/ |
| D | checkkconfigsymbols.py | 134 defined = {}
159 undefined_b, defined = check_symbols(args.ignore)
179 undefined, defined = check_symbols(args.ignore)
188 sims = find_sims(symbol, args.ignore, defined)
270 def find_sims(symbol, ignore, defined=[]): argument
273 if defined:
274 return difflib.get_close_matches(symbol, set(defined), 10)
287 defined.extend(res[0])
289 return difflib.get_close_matches(symbol, set(defined), 10)
423 defined, references = parse_kconfig_file(kfile)
[all …]
|
| /linux-6.12.1/Documentation/userspace-api/media/dvb/ |
| D | fe_property_parameters.rst | 77 The modulation can be one of the types defined by enum :c:type:`fe_modulation`.
83 supported by each delivery system, as currently defined by specs.
108 defined currently at the Kernel. The reason is simple: no driver
164 The acceptable values are defined by :c:type:`fe_spectral_inversion`.
192 The acceptable values are defined by :c:type:`fe_code_rate`.
207 The acceptable values are defined by :c:type:`fe_sec_voltage`.
227 The acceptable values are defined by :c:type:`fe_pilot`.
239 The acceptable values are defined by :c:type:`fe_rolloff`.
273 The acceptable values are defined by :c:type:`fe_delivery_system`.
440 defined by :c:type:`fe_code_rate`.
[all …]
|
| /linux-6.12.1/tools/power/cpupower/utils/idle_monitor/ |
| D | idle_monitors.def | 1 #if defined(__i386__) || defined(__x86_64__)
|
| /linux-6.12.1/Documentation/devicetree/bindings/regulator/ |
| D | tps65023.txt | 12 initialization data for defined regulators. The definition for each of
13 these nodes is defined using the standard binding for regulators found at
16 Each regulator is defined using the standard binding for regulators.
|
| D | sky81452-regulator.txt | 5 - any required generic properties defined in regulator.txt
8 - any available generic properties defined in regulator.txt
|
| D | tps65217.txt | 9 initialization data for defined regulators. Not all regulators for the given
10 device need to be present. The definition for each of these nodes is defined
20 Each regulator is defined using the standard binding for regulators.
|
| D | tps65218.txt | 10 initialization data for defined regulators. Not all regulators for the given
11 device need to be present. The definition for each of these nodes is defined
17 Each regulator is defined using the standard binding for regulators.
|
| D | tps51632-regulator.txt | 13 Any property defined as part of the core regulator binding, defined in
|
| /linux-6.12.1/Documentation/devicetree/bindings/gpio/ |
| D | microchip,pic32-gpio.txt | 9 the second cell is used to specify the gpio polarity as defined in
10 defined in <dt-bindings/gpio/gpio.h>:
16 is used to specify the trigger type as defined in
|
| D | cdns,gpio.txt | 8 * second cell specifies the GPIO flags, as defined in
19 defined, interrupts, interrupt-parent and #interrupt-cells
23 * second cell specifies the IRQ type, as defined in
|
| /linux-6.12.1/Documentation/kbuild/ |
| D | kconfig-macro-language.rst | 62 A simply expanded variable is defined using the := assignment operator. Its
66 A recursively expanded variable is defined using the = assignment operator.
73 side was originally defined as a simple variable. Otherwise, its evaluation is
81 "user-defined function" in contrast to "built-in function" listed below).
84 expanded differently if different parameters are passed. Hence, a user-defined
85 function is defined using the = assignment operator. The parameters are
88 In fact, recursively expanded variables and user-defined functions are the same
90 When we say "variable" in a broad sense, it includes "user-defined function".
172 In Make, a user-defined function is referenced by using a built-in function,
177 Kconfig invokes user-defined functions and built-in functions in the same way.
|
| /linux-6.12.1/Documentation/devicetree/bindings/clock/ |
| D | maxim,max77686.txt | 11 (gated/ungated) over I2C. Clocks are defined as preprocessor macros in
16 (gated/ungated) over I2C. Clocks are defined as preprocessor macros in
20 (gated/ungated) over I2C. Clocks are defined as preprocessor macros in
38 Clocks are defined as preprocessor macros in above dt-binding header for
|
| /linux-6.12.1/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imx27-pinctrl.txt | 56 control registers. They have to be defined as child nodes of the iomux device
57 node. If gpio subnodes are defined "#address-cells", "#size-cells" and "ranges"
90 For convenience there are macros defined in imx27-pinfunc.h which provide PIN
92 are defined in the i.MX27 reference manual.
|
| /linux-6.12.1/Documentation/devicetree/bindings/thermal/ |
| D | db8500-thermal.txt | 10 if greater than 0, the following properties must be defined;
15 point N, this is required if trip point N is defined, set it 0 if none,
16 otherwise the following cooling device names must be defined;
|
| /linux-6.12.1/Documentation/watchdog/ |
| D | mlx-wdt.rst | 16 Actual HW timeout can be defined as a power of 2 msec.
22 Actual HW timeout is defined in sec. and it's the same as
23 a user-defined timeout.
43 There are several actions that can be defined in the watchdog:
|
| /linux-6.12.1/Documentation/devicetree/bindings/sound/ |
| D | davinci-evm-audio.txt | 17 - Either codec-clock-rate or the codec-clock reference has to be defined. If
18 the both are defined the driver attempts to set referenced clock to the
19 defined rate and takes the rate from the clock reference.
|
| /linux-6.12.1/Documentation/devicetree/bindings/ata/ |
| D | ahci-dm816.txt | 7 the controller (as defined by the AHCI 1.1 standard)
10 phandles for clock providers with '0' defined for
|
| /linux-6.12.1/Documentation/iio/ |
| D | ep93xx_adc.rst | 15 Numbering scheme for channels 0..4 is defined in EP9301 and EP9302 datasheets.
17 not defined. So the last three are numbered randomly, let's say.
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | colorspaces-defs.rst | 7 In V4L2 colorspaces are defined by four values. The first is the
24 On :ref:`HSV formats <hsv-formats>` the *Hue* is defined as the angle on
87 - Use the default transfer function as defined by the colorspace.
116 - Use the default Y'CbCr encoding as defined by the colorspace.
163 - Use the default quantization encoding as defined by the
|
| /linux-6.12.1/Documentation/devicetree/bindings/mfd/ |
| D | tps6507x.txt | 7 initialization data for defined regulators. Not all regulators for the
9 is defined using the standard binding for regulators found at
31 If this property is not defined, it defaults to 0 (not enabled).
|
| /linux-6.12.1/tools/perf/Documentation/ |
| D | perf-script-perl.txt | 39 When perf script is invoked using a trace script, a user-defined
41 no handler function defined for a given event type, the event is
74 The handler function for this event would be defined as:
132 *trace_begin*, if defined, is called before any event is processed and
141 *trace_end*, if defined, is called after all events have been
151 *trace_unhandled*, if defined, is called after for any event that
152 doesn't have a handler explicitly defined for it. The standard set
|