| /freebsd/sys/dev/isci/scil/ |
| H A D | scif_sas_remote_device_ready_substate_handlers.c | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0
9 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
22 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
28 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
60 * to the framework remote device READY sub-state handler methods.
85 * @param[in] fw_device This parameter specifies the remote device for
100 if (fw_device->ready_substate_machine.current_state_id in scif_sas_remote_device_start_task_request()
104 &fw_device->ready_substate_machine, in scif_sas_remote_device_start_task_request()
109 fw_device->request_count++; in scif_sas_remote_device_start_task_request()
[all …]
|
| H A D | scif_sas_design.h | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0
9 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
22 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
28 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
61 - Nathan Marushak
64 - Richard Boyd
99 Some of the SAS framework objects contain sub-state machines. These
100 sub-state machines are started upon entrance to the super-state and stopped
101 upon exit of the super-state.
[all …]
|
| H A D | scif_sas_remote_device_starting_substate_handlers.c | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0
9 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
22 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
28 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
60 * to the framework remote device STARTING sub-state handler methods.
61 * The STARTING sub-state machine is responsible for ensuring that
63 * device is complete before transitioning to the READY state
79 * @brief This method provides startig sub-state specific handling for
80 * when the remote device is requested to stop. This will occur
[all …]
|
| H A D | scif_sas_remote_device_states.c | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause OR GPL-2.0
9 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
22 * Foundation, Inc., 51 Franklin St - Fifth Floor, Boston, MA 02110-1301 USA.
28 * Copyright(c) 2008 - 2011 Intel Corporation. All rights reserved.
71 * to start/stop it's remote device object.
105 &fw_device->parent.state_machine, in scif_sas_remote_device_initial_state_enter()
136 // There should be no outstanding requests for this device in the in scif_sas_remote_device_stopped_state_enter()
138 ASSERT(fw_device->request_count == 0); in scif_sas_remote_device_stopped_state_enter()
142 if (fw_device->destruct_when_stopped == TRUE) in scif_sas_remote_device_stopped_state_enter()
[all …]
|
| /freebsd/sys/contrib/openzfs/include/sys/sysevent/ |
| H A D | dev.h | 9 * or https://opensource.org/licenses/CDDL-1.0.
38 * Event Class - EC_DEV_ADD
39 * Event Sub-Class - ESC_DISK
41 * Attribute Name - EV_VERSION
42 * Attribute Type - DATA_TYPE_INT32
43 * Attribute Value - event version number
45 * Attribute Name - DEV_NAME
46 * Attribute Type - DATA_TYPE_STRING
47 * Attribute Value - /dev name to the raw device.
50 * Attribute Name - DEV_PHYS_PATH
[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/mailbox/ |
| H A D | ti,omap-mailbox.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbo
[all...] |
| H A D | omap-mailbox.txt | 25 routed to different processor sub-systems on DRA7xx as they are routed through
35 Mailbox Device Node:
37 A Mailbox device node is used to represent a Mailbox IP instance/cluster within
38 a SoC. The sub-mailboxes are represented as child nodes of this parent node.
41 --------------------
42 - compatible: Should be one of the following,
43 "ti,omap2-mailbox" for OMAP2420, OMAP2430 SoCs
44 "ti,omap3-mailbox" for OMAP3430, OMAP3630 SoCs
45 "ti,omap4-mailbox" for OMAP44xx, OMAP54xx, AM33xx,
47 "ti,am654-mailbox" for K3 AM65x and J721E SoCs
[all …]
|
| H A D | mtk-gce.txt | 9 mailbox.txt for generic information about mailbox device-tree bindings.
12 - compatible: can be "mediatek,mt8173-gce", "mediatek,mt8183-gce",
13 "mediatek,mt8186-gce", "mediatek,mt8192-gce", "mediatek,mt8195-gce" or
14 "mediatek,mt6779-gce".
15 - reg: Address range of the GCE unit
16 - interrupts: The interrupt signal from the GCE block
17 - clock: Clocks according to the common clock binding
18 - clock-names: Must be "gce" to stand for GCE clock
19 - #mbox-cells: Should be 2.
25 Required properties for a client device:
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/net/ |
| H A D | marvell-pxa168.txt | 4 - compatible: should be "marvell,pxa168-eth".
5 - reg: address and length of the register set for the device.
6 - interrupts: interrupt for the device.
7 - clocks: pointer to the clock for the device.
10 - port-id: Ethernet port number. Should be '0','1' or '2'.
11 - #address-cells: must be 1 when using sub-nodes.
12 - #size-cells: must be 0 when using sub-nodes.
13 - phy-handle: see ethernet.txt file in the same directory.
18 Sub-nodes:
19 Each PHY can be represented as a sub-node. This is not mandatory.
[all …]
|
| H A D | keystone-netcp.txt | 1 This document describes the device tree bindings associated with the
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 -----------------------------
[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-v
[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/arm/ti/twl/ |
| H A D | twl.c | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause
35 * This code is based on the Linux TWL multifunctional device driver, which is
36 * copyright (C) 2005-2006 Texas Instruments, Inc.
72 /* TWL device IDs */
78 /* Each TWL device typically has more than one I2C address */
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/sound/ |
| H A D | cs35l35.txt | 5 - compatible : "cirrus,cs35l35"
7 - reg : the I2C address of the device for I2C
9 - VA-supply, VP-supply : power supplies for the device,
13 - interrupts : IRQ line info CS35L35.
14 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
17 - cirru
[all...] |
| H A D | st,stm32-sai.txt | 4 as I2S standards, LSB or MSB-justified, PCM/DSP, TDM, and AC'97.
5 The SAI contains two independent audio sub-blocks. Each sub-block has
9 - compatible: Should be "st,stm32f4-sai" or "st,stm32h7-sai"
10 - reg: Base address and size of SAI common register set.
11 - clocks: Must contain phandle and clock specifier pairs for each entry
12 in clock-names.
13 - clock-names: Must contain "pclk" "x8k" and "x11k"
15 Mandatory for "st,stm32h7-sai" compatible.
16 Not used for "st,stm32f4-sai" compatible.
19 - interrupts: cpu DAI interrupt line shared by SAI sub-blocks
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/devfreq/ |
| H A D | exynos-bus.txt | 1 * Generic Exynos Bus frequency device
4 and sub-blocks in SoC. Most Exynos SoCs share the common architecture
9 is able to measure the current load of sub-blocks.
11 The Exynos SoC includes the various sub-blocks which have the each AXI bus.
13 power line. The power line might be shared among one more sub-blocks.
14 So, we can divide into two type of device as the role of each sub-block.
16 - parent bus device
17 - passive bus device
19 Basically, parent and passive bus device share the same power line.
20 The parent bus device can only change the voltage of shared power line
[all …]
|
| /freebsd/usr.sbin/dumpcis/ |
| H A D | cis.h | 6 *-------------------------------------------------------------------------
8 /*-
9 * SPDX-License-Identifier: BSD-3-Clause
53 #define CIS_MEM_COMMON 0x01 /* Device descriptor, common memory */
67 #define CIS_MEM_ATTR 0x17 /* Device descriptor, Attribute memory */
72 #define CIS_DEVICE_OC 0x1C /* Other conditions info - common memory */
73 #define CIS_DEVICE_OA 0x1D /* Other conditions info - attribute memory */
95 * Device descriptor for memory (CIS_MEM_ATTR, CIS_MEM_COMMON)
98 * 0xF0 - Device type
99 * 0x08 - Write protect switch
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/leds/ |
| H A D | leds-ns2.txt | 1 Binding for dual-GPIO LED found on Network Space v2 (and parents).
4 - compatible: "lacie,ns2-leds".
6 Each LED is represented as a sub-node of the ns2-leds device.
8 Required sub-node properties:
9 - cmd-gpio: Command LED GPIO. See OF device-tree GPIO specification.
10 - slow-gpio: Slow LED GPIO. See OF device-tree GPIO specification.
11 - modes-map: A mapping between LED modes (off, on or SATA activity blinking) and
12 the corresponding cmd-gpio/slow-gpio values. All the GPIO values combinations
15 Optional sub-node properties:
16 - label: Name for this LED. If omitted, the label is taken from the node name.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/regulator/ |
| H A D | samsung,s2mpa01.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 S2MPA01 device provide buck and LDO regulators.
9 To register these with regulator framework instantiate under main device node
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 S2MPA01 device:
16 - LDOn
17 - valid values for n are 1 to 26
18 - Example: LDO1, LD02, LDO26
[all …]
|
| H A D | tps65132-regulator.txt | 4 - compatible: "ti,tps65132"
5 - reg: I2C slave address
8 Device supports two regulators OUTP and OUTN. A sub node within the
9 device node describe the properties of these regulators. The sub-node
11 -For regulator outp, the sub node name should be "outp".
12 -For regulator outn, the sub node name should be "outn".
14 -enable-gpios:(active high, output) Regulators are controlled by the input pins.
17 -active-discharge-gpios: (active high, output) Some configurations use delay mechanisms
20 the delay mechanism. Requires specification of ti,active-discharge-time-us
21 -ti,active-discharge-time-us: how long the active discharge gpio should be
[all …]
|
| /freebsd/contrib/ntp/scripts/monitoring/ |
| H A D | ntptrap | 1 #!/local/bin/perl --*-perl-*-
8 ;# Rainer Pruy Friedrich-Alexander Universitaet Erlangen-Nuernberg
28 #eval 'sub INADDR_ANY { 0; } sub AF_INET {2;} sub SOCK_DGRAM {2;} 1;' || die "$0: $@";
46 sub usage
48 die("usage: $0 [-p <port>] [-l <logfile>] [host] ...\n");
52 &Getopts if 0; # make -w happy
56 $opt_p = 0 # port to use locally - (0 does mean: will be chosen by kernel)
63 $DEBUGFILE="&STDERR" if $DEBUGFILE eq '-';
69 sub log
75 sub debug
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/remoteproc/ |
| H A D | ti,keystone-rproc.txt | 5 sub-systems that are used to offload some of the processor-intensive tasks or
8 These processor sub-systems usually contain additional sub-modules like L1
13 DSP Device Node:
15 Each DSP Core sub-system is represented as a single DT node, and should also
18 CorePac) to perform the device management of the remote processor and to
22 --------------------
25 - compatible: Should be one of the following,
26 "ti,k2hk-dsp" for DSPs on Keystone 2 66AK2H/K SoCs
27 "ti,k2l-dsp" for DSPs on Keystone 2 66AK2L SoCs
28 "ti,k2e-dsp" for DSPs on Keystone 2 66AK2E SoCs
[all …]
|
| H A D | ti,omap-remoteproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remotepro
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/powerpc/fsl/ |
| H A D | srio-rmu.txt | 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>
28 Definition: The logical I/O device number for the PAMU (IOMMU) to be
[all …]
|