| /freebsd/sys/contrib/openzfs/include/sys/sysevent/ |
| H A D | dev.h | 1 // SPDX-License-Identifier: CDDL-1.0
10 * or https://opensource.org/licenses/CDDL-1.0.
39 * Event Class - EC_DEV_ADD
40 * Event Sub-Class - ESC_DISK
42 * Attribute Name - EV_VERSION
43 * Attribute Type - DATA_TYPE_INT32
44 * Attribute Value - event version number
46 * Attribute Name - DEV_NAME
47 * Attribute Type - DATA_TYPE_STRING
48 * Attribute Value - /dev name to the raw device.
[all …]
|
| /freebsd/sys/cddl/contrib/opensolaris/uts/common/sys/sysevent/ |
| H A D | dev.h | 40 * Event Class - EC_DEV_ADD
41 * Event Sub-Class - ESC_DISK
43 * Attribute Name - EV_VERSION
44 * Attribute Type - DATA_TYPE_INT32
45 * Attribute Value - event version number
47 * Attribute Name - DEV_NAME
48 * Attribute Type - DATA_TYPE_STRING
49 * Attribute Value - /dev name to the raw device.
52 * Attribute Name - DEV_PHYS_PATH
53 * Attribute Type - DATA_TYPE_STRING
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/thermal/ |
| H A D | thermal.txt | 6 such as trip points, polling intervals, sensors and cooling devices
15 - 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;
25 * Thermal sensor devices
27 Thermal sensor devices are nodes providing temperature sensing capabilities on
28 thermal zones. Typical devices are I2C ADC converters and bandgaps. These are
29 nodes providing temperature data to thermal zones. Thermal sensor devices may
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/opp/ |
| H A D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
16 applicable across wide range of devices. For illustration purpose, this document
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
31 Missing property means devices have independent clock/voltage/current
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/net/ |
| H A D | keystone-netcp.txt | 6 switch sub-module to send and receive packets. NetCP also includes a packet
13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates
16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP
17 sub-modules exist as a loadable kernel module which plug in to the netcp core.
18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is
19 mandatory to have the ethernet switch sub-module for the ethernet interface to
20 be operational. Any other sub-module like the PA is optional.
24 -----------------------------
26 -----------------------------
28 |-> NetCP Devices -> |
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/regulator/ |
| H A D | samsung,s2mps11.txt | 4 This is a part of device tree bindings for S2M family multi-function devices.
5 More information can be found in bindings/mfd/sec-core.txt file.
7 The S2MPS11/13/14/15 and S2MPU02 devices provide buck and LDO regulators.
10 a sub-node named "regulators" with more sub-nodes for each regulator using the
12 - Documentation/devicetree/bindings/regulator/regulator.txt
15 Names of regulators supported by different devices:
16 - LDOn
17 - valid values for n are:
18 - S2MPS11: 1 to 38
19 - S2MPS13: 1 to 40
[all …]
|
| H A D | palmas-pmic.txt | 6 spin devices should use the tps659038 as it's compatible value.
7 This is the list of those devices:
11 - compatible : Should be from the list
12 ti,twl6035-pmic
13 ti,twl6036-pmic
14 ti,twl6037-pmic
15 ti,tps65913-pmic
16 ti,tps65914-pmic
17 ti,tps65917-pmic
18 ti,tps659038-pmic
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/interconnect/ |
| H A D | samsung,exynos-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/interconnect/samsung,exynos-bus.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chanwoo Choi <cw00.choi@samsung.com>
11 - Krzysztof Kozlowski <krzk@kernel.org>
15 sub-blocks in SoC. Most Exynos SoCs share the common architecture for buses.
20 sub-blocks.
22 The Exynos SoC includes the various sub-blocks which have the each AXI bus.
24 line. The power line might be shared among one more sub-blocks. So, we can
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | srio-rmu.txt | 4 this node is required. For devices with RMAN this node should NOT exist. The
5 node is composed of three types of sub-nodes ("fsl-srio-msg-unit",
6 "fsl-srio-dbell-unit" and "fsl-srio-port-write-unit").
10 - compatible
13 Definition: Must include "fsl,srio-rmu-vX.Y", "fsl,srio-rmu".
18 - reg
20 Value type: <prop-encoded-array>
25 - fsl,liodn
26 Usage: optional-but-recommended (for devices with PAMU)
27 Value type: <prop-encoded-array>
[all …]
|
| /freebsd/sys/arm/ti/twl/ |
| H A D | twl.c | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause
33 * Audio CODEC devices.
36 * copyright (C) 2005-2006 Texas Instruments, Inc.
43 * This driver acts as a bus for more specific companion devices.
84 /* The TWL devices typically use 4 I2C address for the different internal
112 #define TWL_LOCK(_sc) mtx_lock(&(_sc)->sc_mtx)
113 #define TWL_UNLOCK(_sc) mtx_unlock(&(_sc)->sc_mtx)
115 mtx_init(&_sc->sc_mtx, device_get_nameunit(_sc->sc_dev), \
117 #define TWL_LOCK_DESTROY(_sc) mtx_destroy(&_sc->sc_mtx);
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | samsung,sec-core.txt | 1 Binding for Samsung S2M and S5M family multi-function device
4 This is a part of device tree bindings for S2M and S5M family multi-function
5 devices.
8 of multi-function devices which include voltage and current regulators, RTC,
9 charger controller, clock outputs and other sub-blocks. It is interfaced
10 to the host controller using an I2C interface. Each sub-block is usually
14 This document describes bindings for main device node. Optional sub-blocks
15 must be a sub-nodes to it. Bindings for them can be found in:
16 - bindings/regulator/samsung,s2mpa01.txt
17 - bindings/regulator/samsung,s2mps11.txt
[all …]
|
| H A D | da9150.txt | 1 Dialog Semiconductor DA9150 Combined Charger/Fuel-Gauge MFD bindings
3 DA9150 consists of a group of sub-devices:
6 ------ -----------
7 da9150-gpadc : General Purpose ADC
8 da9150-charger : Battery Charger
9 da9150-fg : Battery Fuel-Gauge
14 - compatible : Should be "dlg,da9150"
15 - reg: Specifies the I2C slave address
16 - interrupts: IRQ line info for da9150 chip.
17 - interrupt-controller: da9150 has internal IRQs (own IRQ domain).
[all …]
|
| H A D | wm831x.txt | 7 - compatible : One of the following chip-specific strings:
16 - reg : I2C slave address when connected using I2C, chip select number
19 - gpio-controller : Indicates this device is a GPIO controller.
20 - #gpio-cells : Must be 2. The first cell is the pin number and the
23 - interrupts : The interrupt line the IRQ signal for the device is
26 - interrupt-controller : wm831x devices contain interrupt controllers and
27 may provide interrupt services to other devices.
28 - #interrupt-cells: Must be 2. The first cell is the IRQ number, and the
30 ../interrupt-controller/interrupts.txt
32 Optional sub-nodes:
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | sa.4 | 39 devices of the sequential access class that are attached to the system
43 The sequential access class includes tape and other linear access devices.
65 .Bl -enum
68 referred to as sub-mode 00 below.
80 It should be noted that tape devices are exclusive open devices, except in
84 .Sh SUB-MODES
86 .Sq sub-modes .
87 The sub-modes differ in the action taken when the device is closed:
88 .Bl -tag -width XXXX
112 block-size modes.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/misc/ |
| H A D | fsl,qoriq-mc.txt | 3 The Freescale Management Complex (fsl-mc) is a hardware resource
5 network-oriented packet processing applications. After the fsl-mc
8 blocks that can be used to create functional hardware objects/devices
12 For an overview of the DPAA2 architecture and fsl-mc bus see:
16 same hardware "isolation context" and a 10-bit value called an ICID
21 between ICIDs and IOMMUs, so an iommu-map property is used to define
28 For arm-smmu binding, see:
32 The msi-map property is used to associate the devices with both the ITS
36 Documentation/devicetree/bindings/interrupt-controller/msi.txt.
39 Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/phy/ |
| H A D | phy-miphy365x.txt | 8 - compatible : Should be "st,miphy365x-phy"
9 - st,syscfg : Phandle / integer array property. Phandle of sysconfig group
11 an entry for each port sub-node, specifying the control
14 Required nodes : A sub-node is required for each channel the controller
16 'reg' and 'reg-names' properties are used inside these
21 - #phy-cells : Should be 1 (See second example)
23 - PHY_TYPE_SATA
24 - PHY_TYPE_PCI
25 - reg : Address and length of register sets for each device in
26 "reg-names"
[all …]
|
| /freebsd/usr.sbin/bluetooth/bluetooth-config/ |
| H A D | bluetooth-config.8 | 29 .Nm bluetooth-config
30 .Nd a script to manage config files for the bluetooth sub system
39 utility is an interactive script to provide a frontend to the complex bluetooth sub system daemons.
42 .Bl -tag -width indent+
52 will help finding and setting up bluetooth controllers, scan for nearby bluetooth devices in
57 to securely pair with new devices and, if the device offers HID endpoints such as mice or
65 .Bl -tag -width ".Pa /etc/bluetooth/hosts" -compact
67 .It Pa sysrc -n bthidd_config
68 .It Pa sysrc -n hcsecd_config
72 scan -n ubt0 -a 00:26:bb:7a:58:95
[all …]
|
| /freebsd/share/man/man9/ |
| H A D | superio.9 | 2 .\" SPDX-License-Identifier: BSD-2-Clause
81 set of functions are used for managing Super I/O devices.
84 locating devices,
127 is -1.
150 parameter selects sub-functions of a device that supports them.
151 For devices that do not have sub-functions,
|
| /freebsd/sys/contrib/device-tree/Bindings/mtd/ |
| H A D | mtd-physmap.txt | 1 CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
3 Flash chips (Memory Technology Devices) are often used for solid state
4 file systems on embedded devices.
6 - compatible : should contain the specific model of mtd chip(s)
7 used, if known, followed by either "cfi-flash", "jedec-flash",
8 "mtd-ram" or "mtd-rom".
9 - reg : Address range(s) of the mtd chip(s)
11 non-identical chips can be described in one node.
12 - bank-width : Width (in bytes) of the bank. Equal to the
14 - device-width : (optional) Width of a single mtd chip. If
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/soc/dove/ |
| H A D | pmu.txt | 4 - compatible: value should be "marvell,dove-pmu".
5 May also include "simple-bus" if there are child devices, in which
7 - reg: two base addresses and sizes of the PM controller and PMU.
8 - interrupts: single interrupt number for the PMU interrupt
9 - interrupt-controller: must be specified as the PMU itself is an
11 - #interrupt-cells: must be 1.
12 - #reset-cells: must be 1.
13 - domains: sub-node containing domain descriptions
16 - ranges: defines the address mapping for child devices, as per the
18 "simple-bus".
[all …]
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/history/ |
| H A D | history_002_pos.ksh | 1 #!/bin/ksh -p
2 # SPDX-License-Identifier: CDDL-1.0
11 # or https://opensource.org/licenses/CDDL-1.0.
50 [[ -f $tmpfile ]] && rm -f $tmpfile
51 [[ -f $tmpfile2 ]] && rm -f $tmpfile2
53 datasetexists $dataset && destroy_dataset $dataset -Rf
55 rm -rf /history.$$
58 log_assert "Verify zfs sub-commands which modify state are logged."
79 devices on devices off
88 compression gzip compression gzip-$((RANDOM%9 + 1))
[all …]
|
| /freebsd/sbin/devd/ |
| H A D | devd.conf.5 | 26 .\" Copyright (c) 1999-2000 by Internet Software Consortium
59 .Bl -tag -width ".Ic options"
90 In this way generic statements can be overridden for devices or
94 .Bd -literal -offset indent
101 .Ss Sub-statements
102 The following sub-statements are supported within the
105 .Bl -tag -width ".Ic directory"
114 .It Ic pid-file Qq Pa /var/run/devd.pid ;
116 .It Ic set Ar regexp-name Qq Ar (some|regexp) ;
118 .Ar regexp-name .
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/clock/ |
| H A D | samsung,s2mps11.txt | 4 This is a part of device tree bindings for S2M and S5M family multi-function
5 devices.
6 More information can be found in bindings/mfd/sec-core.txt file.
12 main device node a sub-node named "clocks".
15 - Documentation/devicetree/bindings/clock/clock-bindings.txt
18 Required properties of the "clocks" sub-node:
19 - #clock-cells: should be 1.
20 - compatible: Should be one of: "samsung,s2mps11-clk", "samsung,s2mps13-clk",
21 "samsung,s2mps14-clk", "samsung,s5m8767-clk"
28 Clock ID Devices
[all …]
|
| /freebsd/sys/xen/xenbus/ |
| H A D | xenbusb_if.m | 1 #-
43 * \brief Enumerate all devices of the given type on this bus.
46 * \param _type String indicating the device sub-tree (e.g. "vfb", "vif")
52 * Devices that are found should be entered into the NewBus hierarchy via
54 * and ignores duplicate devices, so it can be called unconditionally
103 * \param _path The tree relative sub-path to the modified node. The empty
|
| /freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | canaan,k210-fpioa.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/canaan,k210-fpio
[all...] |