Home
last modified time | relevance | path

Searched full:named (Results 1 – 25 of 395) sorted by relevance

12345678910>>...16

/Documentation/ABI/testing/
Dsysfs-class-led-trigger-netdev21 Signal the link state of the named network device.
26 of the named network device.
35 Signal transmission of data on the named network device.
47 Signal reception of data on the named network device.
/Documentation/dev-tools/kunit/
Dstyle.rst8 strongly encouraged that they are named and written according to the guidelines
39 Test subsystems should be named after the code being tested, either after the
41 subsystems should be named to avoid ambiguity where necessary.
70 be named ``parport_pc``.
86 Test suites are named after the subsystem they are part of. If a subsystem
122 tests be added, then that suite could be named ``kasan_unittest`` or similar.
131 Tests should be named after what they're testing. This is often the name of the
133 As tests are C functions, they should be named and written in accordance with
162 * be named ``CONFIG_<name>_KUNIT_TEST``: where <name> is the name of the test
194 KUnit tests can often be compiled as a module. These modules should be named
/Documentation/devicetree/bindings/i2c/
Di2c-st.txt10 - A pinctrl state named "default" must be defined to set pins in mode of
21 - A pinctrl state named "idle" could be defined to set pins in idle state
23 - A pinctrl state named "sleep" could be defined to set pins in sleep state
/Documentation/devicetree/bindings/sound/
Dsirf-audio-port.txt11 named "tx") and one for reception (should be named "rx").
Dbrcm,bcm2835-i2s.txt12 named "tx") and one for reception (should be named "rx").
Dsirf-usp.txt11 named "tx") and one for reception (should be named "rx").
/Documentation/admin-guide/gpio/
Dgpio-mockup.rst33 GPIO lines exposed by it should be named.
42 The directory is named after the chip's label. A symlink is also created, named
/Documentation/devicetree/bindings/serial/
Dnxp,lpc1850-uart.txt14 be at least one channel named "tx" for transmit
15 and named "rx" for receive.
Dpl011.yaml47 When present, must have one state named "default",
48 and may contain a second name named "sleep". The former
60 the clock named UARTCLK on the IP block, i.e. the clock
/Documentation/devicetree/bindings/input/touchscreen/
Dresistive-adc-touch.txt17 - iio-channels: The third channel named "pressure" is optional and can be
21 - iio-channel-names: optional channel named "pressure".
/Documentation/devicetree/bindings/remoteproc/
Dmtk,scp.txt12 regions. These should be named "sram" & "cfg".
15 should be named "main".
/Documentation/devicetree/bindings/ata/
Dpata-common.yaml25 Specifies the host controller node. PATA host controller nodes are named
39 nodes will be named "ide-port".
Dsata-common.yaml25 Specifies the host controller node. SATA host controller nodes are named
38 nodes will be named "sata-port".
/Documentation/devicetree/bindings/spi/
Dmicrochip,spi-pic32.txt18 named "spi-tx" for transmit and named "spi-rx" for receive.
/Documentation/networking/device_drivers/atm/
Dcxacru.rst19 Detected devices will appear as ATM devices named "cxacru". In /sys/class/atm/
20 these are directories named cxacruN where N is the device number. A symlink
21 named device points to the USB interface device's directory which contains
/Documentation/admin-guide/perf/
Darm-cmn.rst23 PMU devices will be named arm_cmn_{1..n}.
32 named "rnid_*".
39 register. The event templates are named with prefixes to cover all
/Documentation/networking/
Dnetif-msg.rst34 Initially this message level variable was uniquely named in each driver
56 - Adding a per-interface private variable named "msg_enable". The
76 The set of message levels is named
/Documentation/devicetree/bindings/clock/
Dclock-bindings.txt42 - this node defines a device with two clock outputs, the first named
43 "ckil" and the second named "ckih". Consumer nodes always reference
76 clock-ranges: Empty property indicating that child nodes can inherit named
88 This represents a device with two clock inputs, named "baud" and "register".
128 * The oscillator is fixed-frequency, and provides one clock output, named "osc".
Dclk-s5pv210-audss.txt17 a clock named "xxti".
20 specified, it is fixed to a clock named "iiscdclk0".
/Documentation/devicetree/bindings/gpio/
Dgpio.txt7 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose
10 for new bindings. Also, GPIO properties named "[<name>-]gpio" are valid and old
167 of passed named are less than ngpios) will still be used up until the last
284 2.3) GPIO ranges from named pin groups
290 Both both <pinctrl-base> and <count> must set to 0 when using named pin groups
301 If numerical and named pin groups are mixed, the string corresponding to a
324 in pinctrl2 are defined using the pin groups named "foo" and "bar".
327 were referenced by any gpio-ranges property to contain a property named
/Documentation/devicetree/bindings/regulator/
Dsky81452-regulator.txt4 - regulator node named lout.
/Documentation/devicetree/bindings/usb/
Dulpi.txt5 binding. The host controller shall have a "ulpi" named node as a child, and
/Documentation/i2c/busses/
Di2c-sis630.rst21 This can be interesting for chipsets not named
36 named chipsets.
/Documentation/devicetree/bindings/display/
Drenesas,du.txt38 named.
40 functional clocks must be named "du.x" with "x" being the channel
44 supplied they must be named "dclkin.x" with "x" being the input clock
61 channels. The resets must be named "du.x" with "x" being the numerical
/Documentation/devicetree/bindings/input/
Ddlink,dir685-touchkeys.txt5 board inside the router is named E119921.

12345678910>>...16