| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | snprintf.c | 14 /* The third specifier, %pB, depends on compiler inlining so don't check it */
18 /* The third specifier, %p, is a hashed pointer which changes on every reboot */
110 ASSERT_ERR(load_single_snprintf("%pi5"), "invalid specifier 1"); in test_snprintf_negative()
111 ASSERT_ERR(load_single_snprintf("%a"), "invalid specifier 2"); in test_snprintf_negative()
112 ASSERT_ERR(load_single_snprintf("%"), "invalid specifier 3"); in test_snprintf_negative()
113 ASSERT_ERR(load_single_snprintf("%12345678"), "invalid specifier 4"); in test_snprintf_negative()
114 ASSERT_ERR(load_single_snprintf("%--------"), "invalid specifier 5"); in test_snprintf_negative()
115 ASSERT_ERR(load_single_snprintf("%lc"), "invalid specifier 6"); in test_snprintf_negative()
116 ASSERT_ERR(load_single_snprintf("%llc"), "invalid specifier 7"); in test_snprintf_negative()
|
| /linux/Documentation/devicetree/bindings/pci/ |
| H A D | pci-ep.yaml | 27 - description: IOMMU specifier base (currently always 1 cell)
34 IOMMU specifier per the iommu-map property.
58 Maps a Device ID to an MSI and associated MSI specifier data.
85 associated with the listed MSI, with the MSI specifier
93 - description: (optional) The msi-specifier produced for the first
94 Device ID matched by the entry. Currently, msi-specifier is 0 or
102 mapped to an msi-specifier per the msi-map property.
|
| /linux/Documentation/devicetree/bindings/display/imx/ |
| H A D | nxp,imx8mq-dcss.yaml | 60 - description: Phandle and clock specifier of IMX8MQ_CLK_DISP_AXI_ROOT
61 - description: Phandle and clock specifier of IMX8MQ_CLK_DISP_RTRM
62 - description: Phandle and clock specifier of either IMX8MQ_VIDEO2_PLL1_REF_SEL or
67 - description: Phandle and clock specifier of IMX8MQ_SYS1_PLL_800M
68 - description: Phandle and clock specifier of IMX8MQ_SYS1_PLL_800M
69 - description: Phandle and clock specifier of IMX8MQ_CLK_27M
|
| /linux/Documentation/devicetree/bindings/serial/ |
| H A D | serial.yaml | 31 Must contain a GPIO specifier, referring to the GPIO pin to be used as
37 Must contain a GPIO specifier, referring to the GPIO pin to be used as
43 Must contain a GPIO specifier, referring to the GPIO pin to be used as
49 Must contain a GPIO specifier, referring to the GPIO pin to be used as
55 Must contain a GPIO specifier, referring to the GPIO pin to be used as
61 Must contain a GPIO specifier, referring to the GPIO pin to be used as
|
| /linux/Documentation/devicetree/bindings/pwm/ |
| H A D | pwm.txt | 11 single-pwm ::= <pwm-phandle> <pwm-specifier>
13 pwm-specifier : array of #pwm-cells specifying the given PWM
43 pwm-specifier typically encodes the chip-relative PWM number and the PWM
46 Optionally, the pwm-specifier can encode a number of flags (defined in
50 Example with optional PWM specifier for inverse polarity
|
| /linux/drivers/dma/ |
| H A D | of-dma.c | 25 * @dma_spec: pointer to DMA specifier as found in the device tree
48 * @dma_spec: pointer to DMA specifier as found in the device tree
216 * of_dma_match_channel - Check if a DMA specifier matches name
219 * @index: index of DMA specifier in list of DMA specifiers
220 * @dma_spec: pointer to DMA specifier as found in the device tree
222 * Check if the DMA specifier pointed to by the index in a list of DMA
224 * a valid pointer to the DMA specifier is found. Otherwise returns -ENODEV.
312 * @dma_spec: pointer to DMA specifier as found in the device tree
318 * and the argument of the dma specifier is the 32-bit filter_param. Returns
340 * @dma_spec: pointer to DMA specifier as found in the device tree
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | srio-rmu.txt | 61 specifier. The format of the specifier is defined by the
91 specifier. The format of the specifier is defined by the
121 specifier. The format of the specifier is defined by the
|
| /linux/Documentation/devicetree/bindings/powerpc/4xx/ |
| H A D | cpm.txt | 16 - unused-units : specifier consist of one cell. For each
20 - idle-doze : specifier consist of one cell. For each
24 - standby : specifier consist of one cell. For each
28 - suspend : specifier consist of one cell. For each
|
| /linux/Documentation/devicetree/bindings/net/bluetooth/ |
| H A D | nokia,h4p-bluetooth.txt | 16 - reset-gpios: GPIO specifier, used to reset the BT module (active low)
17 - bluetooth-wakeup-gpios: GPIO specifier, used to wakeup the BT module (active high)
18 - host-wakeup-gpios: GPIO specifier, used to wakeup the host processor (active high)
20 - clocks: should contain a clock specifier for every name in clock-names
|
| H A D | realtek,bluetooth.yaml | 34 description: GPIO specifier, used to wakeup the BT module
38 description: GPIO specifier, used to enable the BT module
42 description: GPIO specifier, used to wakeup the host processor
|
| H A D | brcm,bluetooth.yaml | 39 description: GPIO specifier for the line BT_REG_ON used to
44 description: GPIO specifier for the line BT_RST_N used to
50 description: GPIO specifier for the line BT_WAKE used to
57 description: GPIO specifier for the line HOST_WAKE used
|
| /linux/Documentation/devicetree/bindings/mux/ |
| H A D | mux-consumer.yaml | 17 single-mux-ctrl ::= <mux-ctrl-phandle> [mux-ctrl-specifier]
19 mux-ctrl-specifier : array of #mux-control-cells specifying the
39 mux-ctrl-specifier typically encodes the chip-relative mux controller number.
41 mux-ctrl-specifier can typically be left out.
|
| /linux/Documentation/devicetree/bindings/arm/ux500/ |
| H A D | power_domain.txt | 13 - #power-domain-cells : Number of cells in a power domain specifier, must be 1.
24 - power-domains: A phandle and PM domain specifier. Below are the list of
27 Index Specifier
|
| /linux/Documentation/devicetree/bindings/media/ |
| H A D | hix5hd2-ir.txt | 8 - interrupts: interrupt-specifier for the sole interrupt generated by
9 the device. The interrupt specifier format depends on the interrupt
11 - clocks: clock phandle and specifier pair.
|
| H A D | st-rc.txt | 7 - interrupts: interrupt-specifier for the sole interrupt generated by
8 the device. The interrupt specifier format depends on the interrupt
20 - clocks : phandle with clock-specifier pair for IRB.
|
| /linux/Documentation/devicetree/bindings/reset/ |
| H A D | reset.txt | 15 specifier - a list of DT cells that represents the reset signal within the
16 provider. The length (number of cells) and semantics of the reset specifier
35 #reset-cells: Number of cells in a reset specifier; Typically 0 for nodes
48 resets: List of phandle and reset specifier pairs, one pair
|
| /linux/Documentation/devicetree/bindings/power/reset/ |
| H A D | ltc2952-poweroff.txt | 10 - watchdog-gpios: phandle + gpio-specifier for the GPIO connected to the
12 - kill-gpios: phandle + gpio-specifier for the GPIO connected to the
16 - trigger-gpios: phandle + gpio-specifier for the GPIO connected to the
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | msi-controller.yaml | 20 The number of cells in an msi-specifier, required if not zero.
26 The meaning of the msi-specifier is defined by the device tree
39 interrupt specifier and "span" is the size of the
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | hisilicon,histb-xhci.txt | 9 - clocks: a list of phandle + clock-specifier pairs, one for each
16 - resets: a list of phandle and reset specifier pairs as listed in
20 - phys: a list of phandle + phy specifier pairs
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| H A D | iommu.txt | 40 - #iommu-cells: The number of cells in an IOMMU specifier needed to encode an
43 The meaning of the IOMMU specifier is defined by the device tree binding of
47 therefore no additional information needs to be encoded in the specifier.
64 IOMMU binding for the exact meaning of the cells that make up the specifier.
75 - iommus: A list of phandle and IOMMU specifier pairs that describe the IOMMU
172 /* the specifier represents the ID of the master */
|
| /linux/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio.txt | 42 The exact meaning of each specifier cell is controller specific, and must be
56 GPIO_ACTIVE_HIGH is 0, so in this example gpio-specifier is "18 0" and encodes
83 1.1) GPIO specifier best practices
86 A gpio-specifier should contain a flag indicating the GPIO polarity; active-
90 The gpio-specifier's polarity flag should represent the physical level at the
94 the GPIO controller and the device, then the gpio-specifier will represent the
112 In particular, the polarity cannot be derived from the gpio-specifier, since
120 in the binding. The gpio-specifier should represent the polarity of the signal
132 cells in a gpio-specifier.
|
| /linux/Documentation/devicetree/bindings/hwlock/ |
| H A D | hwlock.txt | 26 associated hwlock args specifier as indicated by
29 a phandle and a corresponding args specifier.
40 the node hwlock1. hwlock1 is a hwlock provider with an argument specifier
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | phy-bindings.txt | 8 #phy-cells: Number of cells in a PHY specifier; The meaning of all those
30 In order to differentiate between these 2 PHYs, an additional specifier should be
71 device defined previously. Note that the phy handle has an additional specifier
|
| H A D | phy-hisi-inno-usb2.txt | 9 - clocks: The phandle and clock specifier pair for INNO USB2 PHY device
11 - resets: The phandle and reset specifier pair for INNO USB2 PHY device reset
23 - resets: The phandle and reset specifier pair for PHY port reset signal.
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| H A D | interconnect.txt | 21 - #interconnect-cells : number of cells in a interconnect specifier needed to
46 interconnects : Pairs of phandles and interconnect provider specifier to denote
57 specifier pairs.
|