Searched full:defined (Results 1 – 25 of 1398) sorted by relevance
12345678910>>...56
| /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
|
| /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 …]
|
| /Documentation/driver-api/media/drivers/ccs/ |
| D | mk-ccs-regs | 24 $help = 1 if ! defined $header || ! defined $limitc || ! defined $limith;
26 if (defined $help) {
43 my $lh_hdr = ! defined $kernel
46 my $uint32_t = ! defined $kernel ? 'uint32_t' : 'u32';
47 my $uint16_t = ! defined $kernel ? 'uint16_t' : 'u16';
53 if (defined $regarray) {
78 print $fh "// $license\n$copyright$note\n" if defined $fh;
98 if defined $kernel;
101 (defined $kernel ? "CCI_REG_PRIVATE_SHIFT" : 16) . "\n";
109 if (defined $kernel) {
[all …]
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | qcom,bcm-voter.yaml | 47 # Example 1: apps bcm_voter on SDM845 SoC should be defined inside &apps_rsc node
48 # as defined in Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml
55 # Example 2: disp bcm_voter on SDM845 should be defined inside &disp_rsc node
56 # as defined in Documentation/devicetree/bindings/soc/qcom/qcom,rpmh-rsc.yaml
|
| /Documentation/devicetree/bindings/display/samsung/ |
| D | samsung,exynos5-dp.yaml | 54 Interlace scan mode. Progressive if defined, interlaced if not defined.
60 VSYNC polarity configuration. High if defined, low if not defined
66 HSYNC polarity configuration. High if defined, low if not defined
|
| /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.
|
| /Documentation/devicetree/bindings/gpio/ |
| 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
|
| 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
|
| /Documentation/devicetree/bindings/regulator/ |
| D | sky81452-regulator.txt | 5 - any required generic properties defined in regulator.txt
8 - any available generic properties defined in regulator.txt
|
| 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 | tps51632-regulator.txt | 13 Any property defined as part of the core regulator binding, defined in
|
| /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:
|
| /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;
|
| /Documentation/devicetree/bindings/clock/ |
| D | samsung,exynos5410-clock.yaml | 16 Expected external clocks, defined in DTS as fixed-rate clocks with a matching
20 All available clocks are defined as preprocessor macros in
33 defined using standard clock bindings with "fin_pll" clock-output-name.
|
| D | renesas,rzg2l-cpg.yaml | 48 and a core clock reference, as defined in
51 a module number, as defined in <dt-bindings/clock/r9a0*-cpg.h>.
60 The power domain specifiers defined in <dt-bindings/clock/r9a0*-cpg.h> could
65 The single reset specifier cell must be the reset number, as defined in
|
| 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
|
| /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.
|
| /Documentation/scsi/ |
| D | scsi_mid_low_api.rst | 114 All functions defined within an LLD and all data defined at file scope
116 called "xxx" could be defined as
337 * Defined in: drivers/scsi/scsi_scan.c
360 * Defined in: drivers/scsi/hosts.c
380 * Defined in: drivers/scsi/scsi.c [see source code for more notes]
396 * Defined in: drivers/scsi/scsicam.c
413 * Defined in: drivers/scsi/scsi_lib.c
437 * Defined in: drivers/scsi/hosts.c .
453 * Defined in: drivers/scsi/hosts.c
472 * Defined in: drivers/scsi/hosts.c
[all …]
|
| /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.
|
| /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 …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | syscon-poweroff.yaml | 15 defined by the register map pointed by syscon reference plus the offset
16 with the value and mask defined in the poweroff node.
28 description: Update only the register bits defined by the mask (32 bit).
|
| D | syscon-reboot.yaml | 15 defined by the SYSCON register map base plus the offset with the value and
16 mask defined in the reboot node. Default will be little endian mode, 32 bit
28 description: Update only the register bits defined by the mask (32 bit).
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-cti.yaml | 21 number is defined at design time, the maximum of each defined in the DEVID
25 programmable channels, usually 4, but again implementation defined and
31 are implementation defined, except when the CTI is connected to an ARM v8
51 and usages. These can be defined along with the signal indexes with the
52 constants defined in <dt-bindings/arm/coresight-cti-dt.h>
55 is defined in the binding as type PE_EDBGREQ. These types will appear in an
251 # v8 architecturally defined CTI - CPU + ETM connections generated by the
265 # Implementation defined CTI - CPU + ETM connections explicitly defined..
312 # Implementation defined CTI - non CoreSight component connections.
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | mediatek,ccorr.yaml | 34 4 arguments defined in this property. Each GCE subsys id is mapping to
35 a client defined in the header include/dt-bindings/gce/<chip>-gce.h.
40 to gce. The event id is defined in the gce header
|
12345678910>>...56