| /linux/Documentation/networking/device_drivers/ethernet/altera/ |
| A D | altera_tse.rst | 147 RFC defined statistics, and driver or Altera defined statistics. The four
167 "rx_crc_errors" is equivalent to aFrameCheckSequenceErrors defined in IEEE
181 "rx_bytes" is equivalent to aOctetsReceivedOK defined in IEEE 802.3-2012,
189 "rx_pause" is equivalent to aPAUSEMACCtrlFramesReceived defined in IEEE
200 "rx_unicast" is equivalent to ifInUcastPkts defined in RFC 2863. This
212 "tx_discards" is equivalent to ifOutDiscards defined in RFC 2863. This
217 "tx_unicast" is equivalent to ifOutUcastPkts defined in RFC 2863. This
229 "ether_drops" is equivalent to etherStatsDropEvents defined in RFC 2819.
233 "rx_total_bytes" is equivalent to etherStatsOctets defined in RFC 2819.
237 "rx_total_packets" is equivalent to etherStatsPkts defined in RFC 2819.
[all …]
|
| /linux/scripts/ |
| A D | checkkconfigsymbols.py | 134 defined = {}
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:
287 defined.extend(res[0])
424 defined_symbols.extend(defined)
435 defined = []
439 return defined, references
451 defined.append(symbol_def[0])
[all …]
|
| /linux/Documentation/devicetree/bindings/display/exynos/ |
| A D | exynos_dp.txt | 6 -dptx-phy node(defined inside dp-controller node)
36 Progressive if defined, Interlaced if not defined
39 High if defined, Low if not defined
42 High if defined, Low if not defined
|
| /linux/Documentation/devicetree/bindings/net/ |
| A D | fsl-enetc.txt | 21 already defined in Documentation/devicetree/bindings/net/ethernet.txt or
31 - mdio : "mdio" node, defined in mdio.txt.
33 - ethernet-phy : "ethernet-phy" node, defined in phy.txt.
54 In this case, the mdio node should be defined as another PCIe
65 already defined in Documentation/devicetree/bindings/net/mdio.txt.
94 - fixed-link : "fixed-link" node, defined in "fixed-link.txt".
|
| /linux/Documentation/userspace-api/media/dvb/ |
| A D | fe_property_parameters.rst | 83 supported by each delivery system, as currently defined by specs.
103 defined currently at the Kernel. The reason is simple: no driver
187 The acceptable values are defined by :c:type:`fe_code_rate`.
202 The acceptable values are defined by :c:type:`fe_sec_voltage`.
222 The acceptable values are defined by :c:type:`fe_pilot`.
234 The acceptable values are defined by :c:type:`fe_rolloff`.
268 The acceptable values are defined by :c:type:`fe_delivery_system`.
435 defined by :c:type:`fe_code_rate`.
449 The modulation used by a given ISDB Layer, as defined by
911 The acceptable values are defined by :c:type:`fe_hierarchy`.
[all …]
|
| /linux/Documentation/devicetree/bindings/usb/ |
| A D | fsl-usb.txt | 18 - port0 : boolean; if defined, indicates port0 is connected for
20 "port1" (or both) must be defined for "fsl-usb2-mph" compatible
22 - port1 : boolean; if defined, indicates port1 is connected for
24 "port0" (or both) must be defined for "fsl-usb2-mph" compatible
28 "host" if not defined for backward compatibility.
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| A 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/rpmh-rsc.txt
55 # Example 2: disp bcm_voter on SDM845 should be defined inside &disp_rsc node
56 # as defined in Documentation/devicetree/bindings/soc/qcom/rpmh-rsc.txt
|
| /linux/Documentation/devicetree/bindings/arm/ |
| A D | coresight-cti.yaml | 22 number is defined at design time, the maximum of each defined in the DEVID
26 programmable channels, usually 4, but again implementation defined and
32 are implementation defined, except when the CTI is connected to an ARM v8
52 and usages. These can be defined along with the signal indexes with the
53 constants defined in <dt-bindings/arm/coresight-cti-dt.h>
56 is defined in the binding as type PE_EDBGREQ. These types will appear in an
235 # v8 architecturally defined CTI - CPU + ETM connections generated by the
249 # Implementation defined CTI - CPU + ETM connections explicitly defined..
296 # Implementation defined CTI - non CoreSight component connections.
|
| /linux/Documentation/kbuild/ |
| A 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/Documentation/devicetree/bindings/regulator/ |
| A 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.
|
| A D | sky81452-regulator.txt | 5 - any required generic properties defined in regulator.txt
8 - any available generic properties defined in regulator.txt
|
| A 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.
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| A D | i2c-mux-pinctrl.txt | 35 For each named state defined in the pinctrl-names property, an I2C child bus
40 such a state is defined, it must be the last entry in pinctrl-names. For
50 If an idle state is defined, whenever an access is not being made to a device
53 If an idle state is not defined, the most recently used pinctrl state will be
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| A 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
|
| A 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
|
| A D | gpio_oxnas.txt | 11 the second cell is used to specify the gpio polarity as defined in
12 defined in <dt-bindings/gpio/gpio.h>:
17 is used to specify the trigger type as defined in
|
| /linux/tools/power/cpupower/utils/idle_monitor/ |
| A D | idle_monitors.def | 1 #if defined(__i386__) || defined(__x86_64__)
|
| /linux/Documentation/devicetree/bindings/power/reset/ |
| A 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.
25 description: Update only the register bits defined by the mask (32 bit).
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| A 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/Documentation/devicetree/bindings/clock/ |
| A 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
|
| A D | brcm,kona-ccu.txt | 15 the name of a defined CCU. For example:
18 are defined below.
24 are defined below.
68 be used. These specifiers are defined in:
113 be used. These specifiers are defined in:
|
| /linux/Documentation/devicetree/bindings/thermal/ |
| A 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/Documentation/watchdog/ |
| A 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/Documentation/trace/coresight/ |
| A D | coresight-config.rst | 14 programming of the CoreSight system with pre-defined configurations that
20 be defined and enabled as named configurations.
33 is device dependent, and can be defined in terms of absolute register values,
36 The feature is defined using a descriptor. This descriptor is used to load onto
80 The features defined may be on any type of device that is registered
102 Presets are optionally defined by the configuration, up to 15 can be defined.
103 If no preset is selected, then the parameter values defined in the feature
|
| /linux/Documentation/devicetree/bindings/iio/adc/ |
| A D | adi,ad7949.yaml | 42 external reference defined by vrefin-supply (or vref-supply).
43 vrefin-supply will take precedence over vref-supply if both are defined.
45 If no supplies are defined, the reference selection will default to
|