| /src/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | pinctrl-vt8500.txt | 3 These SoCs contain a combined Pinmux/GPIO module. Each pin may operate as 23 Each pin configuration node lists the pin(s) to which it applies, and one or 25 configuration. Each subnode only affects those parameters that are explicitly 31 - wm,pins: An array of cells. Each cell contains the ID of a pin. 44 Each of wm,function and wm,pull may contain either a single value which
|
| H A D | lantiq,pinctrl-falcon.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a 21 Each subnode only affects those parameters that are explicitly listed. In 32 - lantiq,groups : An array of strings. Each string contains the name of a group. 50 - lantiq,pins : An array of strings. Each string contains the name of a pin.
|
| H A D | brcm,bcm2835-gpio.txt | 39 Each pin configuration node lists the pin(s) to which it applies, and one or 41 configuration. Each subnode only affects those parameters that are explicitly 65 - brcm,pins: An array of cells. Each cell contains the ID of a pin. Valid IDs 83 Each of brcm,function and brcm,pull may contain either a single value which
|
| H A D | pinctrl-sirf.txt | 17 Each of these subnodes represents some desired configuration for a group of pins. 20 - sirf,pins : An array of strings. Each string contains the name of a group.
|
| H A D | pinctrl-atlas7.txt | 64 Each of these subnodes represents some desired configuration for a group of pins. 67 - groups : An array of strings. Each string contains the name of a group.
|
| H A D | atmel,at91-pio4-pinctrl.txt | 25 Each node (or subnode) will list the pins it needs and how to configured these 34 - pinmux: integer array. Each integer represents a pin number plus mux and
|
| /src/sys/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | sifive,plic-1.0.0.txt | 13 Each interrupt can be enabled on per-context basis. Any context can claim 16 Each interrupt has a configurable priority. Higher priority interrupts are 17 serviced first. Each context can specify a priority threshold. Interrupts 38 with "-1" specifying that a context is not present. Each node pointed
|
| /src/sys/contrib/device-tree/Bindings/leds/ |
| H A D | leds-netxbig.txt | 9 - timers: Timer array. Each timer entry is represented by three integers: 12 Each LED is represented as a sub-node of the netxbig-leds device. 16 - mode-val: Mode to value mapping. Each entry is represented by two integers:
|
| H A D | leds-pwm.txt | 6 Each LED is represented as a sub-node of the pwm-leds device. Each
|
| H A D | register-bit-led.txt | 10 Each LED is represented as a sub-node of the syscon device. Each
|
| /src/sys/contrib/device-tree/Bindings/input/ |
| H A D | microchip,qt1050.txt | 19 Each button (key) is represented as a sub-node: 21 Each not specified key or key with linux,code set to KEY_RESERVED gets disabled 34 Each touchpad need some time to precharge. The value depends on the mechanical
|
| /src/sys/contrib/device-tree/Bindings/powerpc/opal/ |
| H A D | sensor-groups.txt | 7 servers. Each child node indicates a sensor group. 11 Each child node contains below properties:
|
| /src/sys/contrib/device-tree/Bindings/c6x/ |
| H A D | dscr.txt | 46 a lock register. Each tuple consists of the register offset, lock register 56 MAC addresses are contained in two registers. Each element of a MAC address 57 is contained in a single byte. This property has two tuples. Each tuple has 65 Each tuple describes a range of identical bitfields used to control one or 81 for device states controlled by the DSCR. Each tuple describes a range of
|
| /src/sys/dts/ |
| H A D | bindings-mpp.txt | 6 - pin-map : array of pin configurations. Each pin is defined by 2 cells, 13 User Manual. Each pin can have many possible functions depending on the
|
| /src/sys/contrib/device-tree/Bindings/media/xilinx/ |
| H A D | xlnx,video.txt | 8 video IP cores. Each video IP core is represented as documented in video.txt 18 in Documentation/devicetree/bindings/dma/dma.txt) per port. Each port
|
| /src/sys/contrib/device-tree/Bindings/soc/fsl/cpm_qe/qe/ |
| H A D | pincfg.txt | 4 - pio-map : array of pin configurations. Each pin is defined by 6 23 tables in User Manual. Each pin can have up to 4 possible functions in
|
| /src/contrib/libarchive/libarchive/test/ |
| H A D | README | 7 Each test is a function named test_foo in a file named test_foo.c. 9 Each file must start with this line: 24 Each test function can rely on the following:
|
| /src/sys/contrib/device-tree/Bindings/scsi/ |
| H A D | hisilicon-sas.txt | 26 Phy interrupts : Each phy has 3 interrupt sources: 43 Phy interrupts : Each controller has 2 phy interrupts: 46 Sata interrupts : Each phy on the controller has 1 Sata
|
| /src/contrib/smbfs/examples/ |
| H A D | dot.nsmbrc | 12 # This file consist from a set of sections. Each section started by section name 17 # Each section can contain zero or more parameters:
|
| /src/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | omap-mailbox.txt | 10 Each mailbox IP block/cluster has a certain number of h/w fifo queues and output 15 (excluding the SoCs that have a Interrupt Crossbar IP). Each interrupt line is 82 Each child node should have a unique node name across all the different 92 Each of the above ti,mbox-tx and ti,mbox-rx properties should have 3 cells of 116 for details). Each value of the mboxes property should contain a phandle to the
|
| /src/sys/contrib/device-tree/Bindings/gpio/ |
| H A D | nvidia,tegra186-gpio.txt | 31 implemented by the SoC. Each GPIO is assigned to a port, and a port may control 48 Each GPIO controller can generate a number of interrupt signals. Each signal 54 Each GPIO controller in fact generates multiple interrupts signals for each set 55 of ports. Each GPIO may be configured to feed into a specific one of the
|
| H A D | gpio-vf610.txt | 4 functionality. Each pair serves 32 GPIOs. The VF610 has 5 instances of 33 Note: Each GPIO port should have an alias correctly numbered in "aliases"
|
| /src/usr.bin/m4/ |
| H A D | NOTES | 37 the call frames and the arguments. Each frame is back-linked to a 39 each nested call is completed. Each argument is a character pointer
|
| /src/sys/contrib/device-tree/Bindings/remoteproc/ |
| H A D | ti,keystone-rproc.txt | 15 Each DSP Core sub-system is represented as a single DT node, and should also 16 have an alias with the stem 'rproc' defined. Each node has a number of required 32 Each entry should have the memory region's start address 55 Each entry should have the interrupt source number used by
|
| /src/contrib/googletest/googlemock/test/ |
| H A D | gmock-matchers-containers_test.cc | 2446 Matcher<set<int>> m = Each(2); in TEST_P() 2449 Matcher<const int (&)[1]> n = Each(1); // NOLINT in TEST_P() 2454 n = Each(3); in TEST_P() 2460 m = Each(GreaterThan(0)); in TEST_P() 2463 m = Each(GreaterThan(10)); in TEST_P() 2469 Matcher<vector<int>> m = Each(1); in TEST() 2478 EXPECT_THAT(some_vector, Each(1)); in TEST() 2480 EXPECT_THAT(some_vector, Not(Each(1))); in TEST() 2481 EXPECT_THAT(some_vector, Each(3)); in TEST() 2484 EXPECT_THAT(some_vector, Not(Each(3))); in TEST() [all …]
|