Home
last modified time | relevance | path

Searched +full:one +full:- +full:cell (Results 1 – 25 of 483) sorted by relevance

12345678910>>...20

/freebsd/contrib/mandoc/
H A Dtbl.742 macro, consist of at most one line of
46 lines, one or more
51 All input must be 7-bit ASCII.
54 case-insensitive options separated by spaces, tabs, or commas.
61 .Bl -tag -width Ds
63 Draw a single-line box around each table cell.
65 Draw a single-line box around the table.
69 Center the table instead of left-adjusting it.
73 Use the single-character argument as the decimal point with the
83 Draw a double-line box around the table.
[all …]
H A Dtbl.365 utility and not designed for stand-alone use.
73 .Bl -tag -width Ds
107 This structure describes the options of one table.
114 This structure describes one layout line in a table
135 This structure describes one layout cell in a table,
152 This structure describes one data line in a table
194 This structure describes one data cell in a table by specifying
224 .Bl -tag -width Ds
252 for later calls, return the next one or
277 .Bl -tag -width Ds
[all …]
/freebsd/sys/contrib/device-tree/Bindings/powerpc/4xx/
H A Dcpm.txt4 - compatible : compatible list, currently only "ibm,cpm"
5 - dcr-access-method : "native"
6 - dcr-reg : < DCR register range >
9 - er-offset : All 4xx SoCs with a CPM controller have
10 one of two different order for the CPM
15 er-offset = <1>.
16 - unused-units : specifier consist of one cell. For each
17 bit in the cell, the corresponding bit
20 - idle-doze : specifier consist of one cell. For each
21 bit in the cell, the corresponding bit
[all …]
/freebsd/contrib/tcpdump/
H A Dl2vpn.c18 #include "netdissect-stdinc.h"
27 …* https://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#bgp-l2-encapsulation-types-
33 { 3, "ATM transparent cell transport"},
39 { 9, "ATM n-to-one VCC cell transport"},
40 { 10, "ATM n-to-one VPC cell transport"},
43 { 17, "Structure-agnostic E1 over packet"},
44 { 18, "Structure-agnostic T1 (DS1) over packet"},
46 { 20, "Structure-agnostic T3 (DS3) over packet"},
47 { 21, "Nx64kbit/s Basic Service using Structure-aware"},
49 { 40, "Structure-agnostic E3 over packet"},
[all …]
/freebsd/sys/contrib/device-tree/Bindings/thermal/
H A Dthermal.txt15 - thermal sensors: devices which may be used to take temperature
17 - cooling devices: devices which may be used to dissipate heat.
18 - trip points: describe key temperatures at which cooling is recommended. The
20 - cooling maps: used to describe links between trip points and cooling devices;
21 - thermal zones: used to describe thermal data within the hardware;
30 control one or more internal sensors.
33 - #thermal-sensor-cells: Used to provide sensor device specific information
35 Size: one cell nodes with only one sensor, and at least 1 on nodes
62 - #cooling-cells: Used to provide cooling device specific information
64 Size: one cell to specify minimum and maximum cooling state used
[all …]
/freebsd/sys/contrib/device-tree/Bindings/mailbox/
H A Dbrcm,iproc-flexrm-mbox.txt5 hardware blocks. There is one device tree entry per FlexRM block. The
6 FlexRM driver will create a mailbox-controller instance for given FlexRM
10 --------------------
11 - compatible: Should be "brcm,iproc-flexrm-mbox"
12 - reg: Specifies base physical address and size of the FlexRM
14 - msi-parent: Phandles (and potential Device IDs) to MSI controllers
16 interrupts) to CPU. There is one MSI for each FlexRM ring.
17 Refer devicetree/bindings/interrupt-controller/msi.txt
18 - #mbox-cells: Specifies the number of cells needed to encode a mailbox
21 The 1st cell is the mailbox channel number.
[all …]
H A Dnvidia,tegra186-hsp.txt13 - name : Should be hsp
14 - compatible
16 one of:
17 - "nvidia,tegra186-hsp"
18 - "nvidia,tegra194-hsp", "nvidia,tegra186-hsp"
19 - reg : Offset and length of the register set for the device.
20 - interrupt-names
24 - "doorbell"
25 - "sharedN", where 'N' is a number from zero up to the number of
26 external interrupts supported by the HSP instance minus one.
[all …]
/freebsd/sys/contrib/device-tree/Bindings/gpio/
H A Dgpio-mvebu.txt5 - compatible : Should be "marvell,orion-gpio", "marvell,mv78200-gpio",
6 "marvell,armadaxp-gpio" or "marvell,armada-8k-gpio".
8 "marvell,orion-gpio" should be used for Orion, Kirkwood, Dove,
9 Discovery (except MV78200) and Armada 370. "marvell,mv78200-gpio"
12 "marvel,armadaxp-gpio" should be used for all Armada XP SoCs
15 "marvell,armada-8k-gpio" should be used for the Armada 7K and 8K
17 Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt
20 - reg: Address and length of the register set for the device. Only one
21 entry is expected, except for the "marvell,armadaxp-gpio" variant
22 for which two entries are expected: one for the general registers,
[all …]
H A Dnvidia,tegra186-gpio.txt28 just one of these physical aliases.
42 extremely non-linear. The header file <dt-bindings/gpio/tegra186-gpio.h>
43 describes the port-level mapping. In that file, the naming convention for ports
52 both the overall controller HW module and the sets-of-ports as "controllers".
55 of ports. Each GPIO may be configured to feed into a specific one of the
56 interrupt signals generated by a set-of-ports. The intent is for each generated
59 per-port-set signals is reported via a separate register. Thus, a driver needs
66 - compatible
68 One of:
69 - "nvidia,tegra186-gpio".
[all …]
/freebsd/sys/contrib/device-tree/Bindings/arm/
H A Dvexpress-sysreg.txt2 --------------------------------------
9 - compatible value : = "arm,vexpress,sysreg";
10 - reg : physical base address and the size of the registers window
13 - gpio-controller : specifies that the node is a GPIO controller
14 - #gpio-cells : size of the GPIO specifier, should be 2:
15 - first cell is the pseudo-GPIO line number:
16 0 - MMC CARDIN
17 1 - MMC WPROT
18 2 - NOR FLASH WPn
19 - second cell can take standard GPIO flags (currently ignored).
[all …]
/freebsd/sys/contrib/device-tree/Bindings/mips/cavium/
H A Dbootbus.txt7 - compatible: "cavium,octeon-3860-bootbus"
11 - reg: The base address of the Boot Bus' register bank.
13 - #address-cells: Must be <2>. The first cell is the chip select
14 within the bootbus. The second cell is the offset from the chip select.
16 - #size-cells: Must be <1>.
18 - ranges: There must be one one triplet of (child-bus-address,
19 parent-bus-address, length) for each active chip select. If the
27 - compatible: "cavium,octeon-3860-bootbus-config"
29 - cavium,cs-index: A single cell indicating the chip select that
32 - cavium,t-adr: A cell specifying the ADR timing (in nS).
[all …]
/freebsd/crypto/heimdal/appl/afsutil/
H A Dafslog.11 .\" Copyright (c) 2002 - 2007 Kungliga Tekniska Högskolan
43 .Op Fl Fl no-v4
44 .Op Fl Fl no-v5
48 .Oo Fl c Ar cell \*(Ba Xo
49 .Fl Fl cell= Ns Ar cell
60 .Bk -words
66 .Op Ar cell | path ...
78 .Bl -tag -width Ds
79 .It Fl Fl no-v4
83 .It Fl Fl no-v5
[all …]
/freebsd/sys/contrib/device-tree/Bindings/sound/
H A Dcirrus,madera.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - patches@opensource.cirrus.com
21 include/dt-bindings/sound/madera.h
26 - $ref: dai-common.yaml#
29 '#sound-dai-cells':
31 The first cell indicating the audio interface.
38 INnAR INnBL INnBR. For non-muxed inputs the first two cells
43 left and right B inputs. Valid mode values are one of the
[all …]
/freebsd/sys/contrib/device-tree/Bindings/clock/
H A Dux500.txt1 Clock bindings for ST-Ericsson Ux500 clocks
4 - compatible : shall contain only one of the following:
5 "stericsson,u8500-clks"
6 "stericsson,u8540-clks"
7 "stericsson,u9540-clks"
8 - reg : shall contain base register location and length for
13 - prcmu-clock: a subnode with one clock cell for PRCMU (power,
14 reset, control unit) clocks. The cell indicates which PRCMU
15 clock in the prcmu-clock node the consumer wants to use.
16 - prcc-periph-clock: a subnode with two clock cells for
[all …]
/freebsd/contrib/llvm-project/llvm/lib/Target/Hexagon/
H A DBitTracker.h1 //===- BitTracker.h ---------------------------------------------*- C++ -*-===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
151 // any register, it is more of an abstraction of the two-element set of
152 // possible bit values. One extension here is the "Ref" type, which
159 One, // Bit = 1. enumerator
160 Ref // Bit value same as the one described in RefI.
170 // for one register will be a simple "ref" for another register.
174 // In practice there is a special case for values that are not associa-
183 // one in which V will be contained. If the RefI.Pos refers to the posi-
[all …]
/freebsd/sys/contrib/device-tree/Bindings/dma/
H A Dsnps,dma-spear1340.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/dma/snps,dma-spear1340.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <vireshk@kernel.org>
11 - Andy Shevchenko <andriy.shevchenko@linux.intel.com>
14 - $ref: dma-controller.yaml#
19 - const: snps,dma-spear1340
20 - items:
21 - enum:
[all …]
/freebsd/sys/contrib/device-tree/Bindings/iommu/
H A Diommu.txt13 Example: 32-bit DMA to 64-bit physical addresses
15 * Implement scatter-gather at page level granularity so that the device does
29 IOMMUs can be single-master or multiple-master. Single-master IOMMU devices
30 typically have a fixed association to the master device, whereas multiple-
31 master IOMMU devices can translate accesses from more than one master.
34 "dma-ranges" property that describes how the physical address space of the
35 IOMMU maps to memory. An empty "dma-ranges" property means that there is a
39 --------------------
40 - #iommu-cells: The number of cells in an IOMMU specifier needed to encode an
44 the specific IOMMU. Below are a few examples of typical use-cases:
[all …]
/freebsd/sys/contrib/device-tree/Bindings/pinctrl/
H A Dbrcm,bcm2835-gpio.txt7 - compatible: "brcm,bcm2835-gpio"
8 - compatible: should be one of:
9 "brcm,bcm2835-gpio" - BCM2835 compatible pinctrl
10 "brcm,bcm7211-gpio" - BCM7211 compatible pinctrl
11 "brcm,bcm2711-gpio" - BCM2711 compatible pinctrl
12 "brcm,bcm7211-gpio" - BCM7211 compatible pinctrl
13 - reg: Should contain the physical address of the GPIO module's registers.
14 - gpio-controller: Marks the device node as a GPIO controller.
15 - #gpio-cells : Should be two. The first cell is the pin number and the
16 second cell is used to specify optional parameters:
[all …]
/freebsd/sys/contrib/device-tree/Bindings/interrupt-controller/
H A Darm,vic.txt3 One or more Vectored Interrupt Controllers (VIC's) can be connected in an ARM
5 nested or have the outputs wire-OR'd together.
9 - compatible : should be one of
10 "arm,pl190-vic"
11 "arm,pl192-vic"
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
14 the VIC has no configuration options for interrupt sources. The cell is a u32
16 - reg : The register bank for the VIC.
20 - interrupts : Interrupt source for parent controllers if the VIC is nested.
[all …]
H A Dcdns,xtensa-pic.txt1 * Xtensa built-in Programmable Interrupt Controller (PIC)
4 - compatible: Should be "cdns,xtensa-pic".
5 - interrupt-controller: Identifies the node as an interrupt controller.
6 - #interrupt-cells: The number of cells to define the interrupts.
8 When it's 1, the first cell is the internal IRQ number.
9 When it's 2, the first cell is the IRQ number, and the second cell
18 compatible = "cdns,xtensa-pic";
19 /* one cell: internal irq number,
20 * two cells: second cell == 0: internal irq number
21 * second cell == 1: external irq number
[all …]
H A Dti,c64x+megamod-pic.txt2 -------------------
8 Priority 2 and 3 are reserved. Priority 4-15 are used for interrupt
12 --------------------
13 - compatible: Should be "ti,c64x+core-pic";
14 - #interrupt-cells: <1>
17 ------------------------------
18 Single cell specifying the core interrupt priority level (4-15) where
22 -------
23 core_pic: interrupt-controller@0 {
24 interrupt-controller;
[all …]
/freebsd/sys/contrib/device-tree/Bindings/mmc/
H A Dfsl-imx-esdhc.txt7 by mmc.txt and the properties used by the sdhci-esdhc-imx driver.
10 - compatible : Should be "fsl,<chip>-esdhc", the supported chips include
11 "fsl,imx25-esdhc"
12 "fsl,imx35-esdhc"
13 "fsl,imx51-esdhc"
14 "fsl,imx53-esdhc"
15 "fsl,imx6q-usdhc"
16 "fsl,imx6sl-usdhc"
17 "fsl,imx6sx-usdhc"
18 "fsl,imx6ull-usdhc"
[all …]
/freebsd/sys/contrib/device-tree/Bindings/powerpc/fsl/
H A Dmpc5200.txt2 ----------------------------
4 (c) 2006-2009 Secret Lab Technologies Ltd
8 ------------------
9 For mpc5200 on-chip devices, the format for each compatible value is
10 <chip>-<device>[-<mode>]. The OS should be able to match a device driver
20 else; the 5200 compatible properties will contain only one item;
21 "fsl,mpc5200-<device>".
29 compatible = "fsl,mpc5200b-<device>","fsl,mpc5200-<device>";
34 ie. ethernet on mpc5200: compatible = "fsl,mpc5200-fec";
35 ethernet on mpc5200b: compatible = "fsl,mpc5200b-fec", "fsl,mpc5200-fec";
[all …]
/freebsd/sys/contrib/device-tree/Bindings/extcon/
H A Dwlf,arizona.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - patches@opensource.cirrus.com
20 wlf,hpdet-channel:
30 wlf,use-jd2:
35 wlf,use-jd2-nopull:
40 wlf,jd-invert:
45 wlf,micd-software-compare:
50 wlf,micd-detect-debounce:
[all …]
/freebsd/sys/contrib/device-tree/Bindings/i3c/
H A Di3c.txt8 -------------------
10 - #address-cells - should be <3>. Read more about addresses below.
11 - #size-cells - should be <0>.
12 - compatible - name of the I3C master controller driving the I3C bus
16 The node describing an I3C bus should be named i3c-master.
19 -------------------
24 - i3c-scl-hz: frequency of the SCL signal used for I3C transfers.
27 - i2c-scl-hz: frequency of the SCL signal used for I2C transfers.
40 --------------------------------------
41 - reg: contains 3 cells
[all …]

12345678910>>...20