| /f-stack/freebsd/contrib/openzfs/module/zfs/ |
| H A D | aggsum.c | 90 bzero(as, sizeof (*as)); in aggsum_init() 91 as->as_lower_bound = as->as_upper_bound = value; in aggsum_init() 103 aggsum_fini(aggsum_t *as) in aggsum_fini() argument 107 kmem_free(as->as_buckets, as->as_numbuckets * sizeof (aggsum_bucket_t)); in aggsum_fini() 142 aggsum_value(aggsum_t *as) in aggsum_value() argument 147 if (as->as_lower_bound == as->as_upper_bound) { in aggsum_value() 148 rv = as->as_lower_bound; in aggsum_value() 162 VERIFY3U(as->as_lower_bound, ==, as->as_upper_bound); in aggsum_value() 163 rv = as->as_lower_bound; in aggsum_value() 175 asb = &as->as_buckets[CPU_SEQID_UNSTABLE % as->as_numbuckets]; in aggsum_add() [all …]
|
| /f-stack/freebsd/net80211/ |
| H A D | ieee80211_acl.c | 107 if (as == NULL) in acl_attach() 113 vap->iv_as = as; in acl_attach() 154 as->as_nacls--; in _acl_free() 190 ACL_LOCK(as); in acl_add() 205 as->as_nacls++; in acl_add() 206 ACL_UNLOCK(as); in acl_add() 219 ACL_LOCK(as); in acl_remove() 223 ACL_UNLOCK(as); in acl_remove() 240 ACL_LOCK(as); in acl_free_all() 243 ACL_UNLOCK(as); in acl_free_all() [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sound/ |
| H A D | rt5659.txt | 25 1: using IN2N pin as dmic1 data pin 26 2: using GPIO5 pin as dmic1 data pin 27 3: using GPIO9 pin as dmic1 data pin 28 4: using GPIO11 pin as dmic1 data pin 32 1: using IN2P pin as dmic2 data pin 33 2: using GPIO6 pin as dmic2 data pin 34 3: using GPIO10 pin as dmic2 data pin 35 4: using GPIO12 pin as dmic2 data pin 39 1: using JD3 as JD source
|
| H A D | tlv320adcx140.yaml | 67 array is defined as <PDMIN1 PDMIN2 PDMIN3 PDMIN4>. 89 The array is defined as <GPI1 GPI2 GPI3 GPI4>. 92 1 - GPIX is configured as a general-purpose input (GPI) 93 2 - GPIX is configured as a master clock input (MCLK) 94 3 - GPIX is configured as an ASI input for daisy-chain (SDIN) 95 4 - GPIX is configured as a PDM data input for channel 1 and channel 118 The array is defined as <GPO_CFG GPO_DRV> 123 1 - GPOX is configured as a general-purpose output (GPO) 124 2 - GPOX is configured as a device interrupt output (IRQ) 125 3 - GPOX is configured as a secondary ASI output (SDOUT2) [all …]
|
| H A D | rt5645.txt | 28 1: using IN2P pin as dmic1 data pin 29 2: using GPIO6 pin as dmic1 data pin 30 3: using GPIO10 pin as dmic1 data pin 31 4: using GPIO12 pin as dmic1 data pin 35 1: using IN2N pin as dmic2 data pin 36 2: using GPIO5 pin as dmic2 data pin 37 3: using GPIO11 pin as dmic2 data pin
|
| H A D | rt5668.txt | 17 1: using GPIO2 pin as dmic1 data pin 18 2: using GPIO5 pin as dmic1 data pin 21 0: using GPIO1 pin as dmic1 clock pin 22 1: using GPIO3 pin as dmic1 clock pin 26 1: using JD1 as JD source
|
| H A D | rt5665.txt | 23 1: using GPIO4 pin as dmic1 data pin 24 2: using IN2N pin as dmic2 data pin 28 1: using GPIO5 pin as dmic2 data pin 29 2: using IN2P pin as dmic2 data pin 33 1: using JD1 as JD source
|
| /f-stack/freebsd/contrib/device-tree/Bindings/input/ |
| H A D | nvidia,tegra20-kbc.txt | 3 can be configured as row or column. The maximum column pin can be 8 10 - nvidia,kbc-row-pins: The KBC pins which are configured as row. This is an 11 array of pin numbers which is used as rows. 12 - nvidia,kbc-col-pins: The KBC pins which are configured as column. This is an 13 array of pin numbers which is used as column. 14 - linux,keymap: The keymap for keys as described in the binding document 26 - linux,fn-keymap: a second keymap, same specification as the 32 - wakeup-source: configure keyboard as a wakeup source for suspend/resume 46 nvidia,kbc-row-pins = <0 1 2>; /* pin 0, 1, 2 as rows */ 47 nvidia,kbc-col-pins = <11 12 13>; /* pin 11, 12, 13 as columns */
|
| /f-stack/freebsd/contrib/device-tree/Bindings/hwmon/ |
| H A D | lm87.txt | 10 - has-temp3: This configures pins 18 and 19 to be used as a second 12 are configured as voltage input pins in0 and in5. 14 - has-in6: When set, pin 5 is configured to be used as voltage input 15 in6. Otherwise the pin is set as FAN1 input. 17 - has-in7: When set, pin 6 is configured to be used as voltage input 18 in7. Otherwise the pin is set as FAN2 input.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/pinctrl/ |
| H A D | pinctrl-max77620.txt | 3 Device has 8 GPIO pins which can be configured as GPIO as well as the 18 The pin configurations are defined as child of the pinctrl states node. Each 28 Following are optional properties defined as pinmux DT binding document 69 selected as FPS0, FPS1 or FPS2. 76 selected as FPS0, FPS1 or FPS2. 78 - maxim,suspend-fps-source: This is same as property 83 - maxim,suspend-fps-power-up-slot: This is same as property 89 FPS source is selected as FPS0, FPS1 or 91 - maxim,suspend-fps-power-down-slot: This is same as property 97 FPS source is selected as FPS0, FPS1 or
|
| H A D | renesas,rza1-pinctrl.txt | 113 Integers values in "pinmux" argument list are assembled as: 140 Pin #0 on port #3 is configured as alternate function #6. 141 Pin #2 on port #3 is configured as alternate function #4. 152 Pin #4 on port #1 is configured as alternate function #1. 153 Pin #5 on port #1 is configured as alternate function #1. 158 Configure TIOC0A as software driven input and TIOC0B as software driven 182 specified by software as input. 184 specified by software as output. 195 empty property as defined by the GPIO bindings documentation. 202 pins, as defined by the GPIO bindings documentation. Refer to [all …]
|
| H A D | qcom,mdm9615-pinctrl.txt | 24 Definition: identifies this node as an interrupt controller 29 Definition: must be 2. Specifying the pin number and flags, as defined 35 Definition: identifies this node as a gpio controller 40 Definition: must be 2. Specifying the pin number and flags, as defined 58 The pin configuration nodes act as a container for an arbitrary number of 62 parameters, such as pull-up, drive strength, etc. 77 The following generic properties as defined in pinctrl-bindings.txt are valid 100 Definition: The specified pins should be configured as no pull. 105 Definition: The specified pins should be configured as pull down. 110 Definition: The specified pins should be configured as pull up.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/bus/ |
| H A D | ti-sysc.txt | 4 hardware for devices connected to various interconnects such as L3 44 target module in question such as revision, sysc and syss 47 interconnect target module in question such as 53 multiple ranges such as device L4 range for control and 59 SYSCONFIG register as documented in the Technical Reference 63 target module as documented in the TRM for SYSCONFIG 67 target module as documented in the TRM for SYSCONFIG 78 - clocks clock specifier for each name in the clock-names as 82 mode as for example omap4 L4_CFG_CLKCTRL 87 optional clocks that can be specified as listed in TRM [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/gpio/ |
| H A D | gpio-thunderx.txt | 5 - gpio-controller: Marks the device node as a GPIO controller. 8 - Second cell is a standard generic flag bitfield as described in gpio.txt. 11 - compatible: "cavium,thunder-8890-gpio", unused as PCI driver binding is used. 12 - interrupt-controller: Marks the device node as an interrupt controller. 16 - Second cell is triggering flags as defined in interrupts.txt.
|
| H A D | gpio-max77620.txt | 3 Device has 8 GPIO pins which can be configured as GPIO as well as the 8 - gpio-controller : Marks the device node as a gpio controller.
|
| H A D | cdns,gpio.txt | 8 * second cell specifies the GPIO flags, as defined in 11 - gpio-controller: marks the device as a GPIO controller. 18 - interrupt-controller: marks the device as an interrupt controller. When 22 * first cell is the GPIO number you want to use as an IRQ source. 23 * second cell specifies the IRQ type, as defined in
|
| H A D | gpio-xilinx.txt | 4 (from 1 to 32 per channel). Every pin can be configured as 13 - gpio-controller : Marks the device node as a GPIO controller. 22 - xlnx,all-inputs-2 : as above but for the second channel 23 - xlnx,dout-default-2 : as above but the second channel 24 - xlnx,gpio2-width : as above but for the second channel 25 - xlnx,tri-default-2 : as above but for the second channel
|
| H A D | spear_spics.txt | 6 released as soon as transfer is over and TxFIFO becomes empty. This is not 10 Chipselects can be controlled by software by turning them as GPIOs. SPEAr 13 the control of this interface as gpio. 17 * compatible: should be defined as "st,spear-spics-gpio" 24 * gpio-controller: Marks the device node as gpio controller
|
| /f-stack/freebsd/contrib/device-tree/src/arm64/exynos/ |
| H A D | exynos5433-tmu.dtsi | 56 /* Set maximum frequency as 1800MHz */ 62 /* Set maximum frequency as 1700MHz */ 68 /* Set maximum frequency as 1600MHz */ 74 /* Set maximum frequency as 1500MHz */ 80 /* Set maximum frequency as 1400MHz */ 92 /* Set maximum frequency as 1000MHz */ 230 /* Set maximum frequency as 1200MHz */ 236 /* Set maximum frequency as 1100MHz */ 242 /* Set maximum frequency as 1000MHz */ 248 /* Set maximum frequency as 900MHz */ [all …]
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | abi_policy.rst | 29 #. Libraries or APIs marked as :ref:`experimental <experimental_apis>` may 66 example. The ABI of a milestone release may be declared as a 'major ABI 127 enhancements. API breakages due to changes such as reorganizing public 162 as not to break consuming applications. 229 This is not a problem as long as the symbol ``rte_foo@DPDK_21`` is 248 an explicit package dependency, as the soname can only indicate the 294 This is commonly known as the *ABI breakage window*, 301 as described in the section :ref:`abi_changes`. 304 as described in the section :ref:`deprecating_entire_abi`. 306 as described in section :ref:`aliasing_experimental_symbols`, [all …]
|
| /f-stack/freebsd/contrib/device-tree/Bindings/spi/ |
| H A D | spi-ath79.txt | 4 - compatible: has to be "qca,<soc-type>-spi", "qca,ar7100-spi" as fallback. 8 - #address-cells: <1>, as required by generic SPI binding. 9 - #size-cells: <0>, also as required by generic SPI binding. 11 Child nodes as per the generic SPI binding.
|
| H A D | omap-spi.txt | 10 - ti,pindir-d0-out-d1-in: Select the D0 pin as output and D1 as 11 input. The default is D0 as input and 12 D1 as output. 16 as described in the generic DMA client binding. A tx and rx
|
| /f-stack/dpdk/doc/guides/eventdevs/ |
| H A D | octeontx.rst | 9 SoC family as well as their virtual functions (VF) in SR-IOV context. 48 The OCTEON TX eventdev is exposed as a vdev device which consists of a set 88 When eth_octeontx is used as Rx adapter event schedule type 94 When timvf is used as Event timer adapter the clock source mapping is as 104 When timvf is used as Event timer adapter event schedule type 111 and they can be configured by passing limits to kernel bootargs as follows: 125 as (Rx/Timer) should be limited to the above configured value.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | arm,vic.txt | 12 - interrupt-controller : Identifies the node as an interrupt controller 13 - #interrupt-cells : The number of cells to define the interrupts. Must be 1 as 26 configured as wake up source for the system. Order of bits is the same as for 28 configured as a wake up source for the system. If unspecied, defaults to all 29 interrupt sources configurable as wake up sources.
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | multi_process.rst | 17 and as documented in the *DPDK Getting Started Guide*. 40 passing at least two cores in the coremask/corelist, as follows: 82 When running a secondary process such as that shown above, the proc-type parameter can again be spe… 145 such as a client-server mode of operation seen in the next example, 182 the following commands can be used (assuming run as root): 202 Instead, that process can be restarted as a secondary, 293 as there is no support in the server application for it to run as a secondary process. 299 …rk port and data structure initialization much as the symmetric multi-process application does whe… 302 as is done for the symmetric multi-process application, and therefore eliminates mismatched paramet… 309 which will, as in the symmetric multi-process example, [all …]
|