| /freebsd/sys/contrib/device-tree/Bindings/leds/ |
| H A D | leds-bcm6328.txt | 4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
8 or by hardware using this driver.
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
14 should be controlled by a hardware signal instead of the MODE register value,
15 with 0 meaning hardware control enabled and 1 hardware control disabled. This
16 is usually 1:1 for hardware to LED signals, but through the activity/link
18 explained later in brcm,link-signal-sources). Even if a LED is hardware
20 but you can't turn it off if the hardware decides to light it up. For this
21 reason, hardware controlled LEDs aren't registered as LED class devices.
[all …]
|
| H A D | leds-bcm6328.yaml | 14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
18 Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or by hardware
20 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
21 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
25 should be controlled by a hardware signal instead of the MODE register value,
26 with 0 meaning hardware control enabled and 1 hardware control disabled. This
27 is usually 1:1 for hardware to LED signals, but through the activity/link
29 explained later in brcm,link-signal-sources). Even if a LED is hardware
31 but you can't turn it off if the hardware decides to light it up. For this
32 reason, hardware controlled LEDs aren't registered as LED class devices.
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/spi/ |
| H A D | sprd,spi-adi.yaml | 17 framework for its hardware implementation is alike to SPI bus and its timing
21 48 hardware channels to access analog chip. For 2 software read/write channels,
22 users should set ADI registers to access analog chip. For hardware channels,
23 we can configure them to allow other hardware components to use it independently,
24 which means we can just link one analog chip address to one hardware channel,
25 then users can access the mapped analog chip address by this hardware channel
26 triggered by hardware components instead of ADI software channels.
28 Thus we introduce one property named "sprd,hw-channels" to configure hardware
29 channels, the first value specifies the hardware channel id which is used to
30 transfer data triggered by hardware automatically, and the second value specifies
[all …]
|
| H A D | spi-sprd-adi.txt | 5 framework for its hardware implementation is alike to SPI bus and its timing
9 48 hardware channels to access analog chip. For 2 software read/write channels,
10 users should set ADI registers to access analog chip. For hardware channels,
11 we can configure them to allow other hardware components to use it independently,
12 which means we can just link one analog chip address to one hardware channel,
13 then users can access the mapped analog chip address by this hardware channel
14 triggered by hardware components instead of ADI software channels.
16 Thus we introduce one property named "sprd,hw-channels" to configure hardware
17 channels, the first value specifies the hardware channel id which is used to
18 transfer data triggered by hardware automatically, and the second value specifies
[all …]
|
| /freebsd/sys/dev/ixgbe/ |
| H A D | ixgbe_api.c | 62 * @hw: pointer to hardware structure
75 * @hw: pointer to hardware structure
78 * Does not touch the hardware. This function must be called prior to any
257 * ixgbe_init_hw - Initialize the hardware
258 * @hw: pointer to hardware structure
260 * Initialize the hardware by resetting and then starting the hardware
269 * ixgbe_reset_hw - Performs a hardware reset
270 * @hw: pointer to hardware structure
272 * Resets the hardware by resetting the transmit and receive units, masks and
282 * ixgbe_start_hw - Prepares hardware for Rx/Tx
[all …]
|
| H A D | ixgbe_x540.c | 54 * @hw: pointer to hardware structure
57 * Does not touch the hardware.
166 * @hw: pointer to hardware structure
183 * @hw: pointer to hardware structure
195 * @hw: pointer to hardware structure
208 * ixgbe_reset_hw_X540 - Perform hardware reset
209 * @hw: pointer to hardware structure
211 * Resets the hardware by resetting the transmit and receive units, masks
310 * ixgbe_start_hw_X540 - Prepare hardware for Tx/Rx
311 * @hw: pointer to hardware structure
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/arm64/fujitsu/a64fx/ |
| H A D | cache.json | 45 …"PublicDescription": "This event counts L1D_CACHE_REFILL caused by software or hardware prefetch.",
48 … "BriefDescription": "This event counts L1D_CACHE_REFILL caused by software or hardware prefetch."
51 …"PublicDescription": "This event counts L2D_CACHE_REFILL caused by software or hardware prefetch.",
54 … "BriefDescription": "This event counts L2D_CACHE_REFILL caused by software or hardware prefetch."
63 "PublicDescription": "This event counts L1D_CACHE_REFILL caused by hardware prefetch.",
66 "BriefDescription": "This event counts L1D_CACHE_REFILL caused by hardware prefetch."
87 "PublicDescription": "This event counts L2D_CACHE_REFILL caused by hardware prefetch.",
90 "BriefDescription": "This event counts L2D_CACHE_REFILL caused by hardware prefetch."
105 …ns where demand access hits an L2 cache refill buffer allocated by software or hardware prefetch.",
108 …ons where demand access hits an L2 cache refill buffer allocated by software or hardware prefetch."
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | ath.4 | 89 AR5212, AR5416 and later parts have hardware support for the
136 .Sh HARDWARE
191 .It "ath%d: unable to attach hardware; HAL status %u"
192 The Atheros Hardware Access Layer was unable to configure the hardware
210 .It "ath%d: hardware error; resetting"
211 An unrecoverable error in the hardware occurred.
213 The driver will reset the hardware and continue.
215 The receive FIFO in the hardware overflowed before the data could be
217 This typically occurs because the hardware ran short of receive
219 The driver will reset the hardware and continue.
[all …]
|
| H A D | pwmc.4 | 49 driver provides device-control access to a channel of PWM hardware.
54 Some PWM hardware is organized with multiple channels sharing a
60 hardware which share the same resources.
61 Consult the documentation for the underlying PWM hardware device driver
70 is a sequential number assigned to each PWM hardware controller
73 is the channel number within that hardware controller.
137 The hardware channel number the instance is attached to.
149 device is described with a child node of the pwm hardware controller node.
150 When the hardware supports multiple channels within the controller, it is
153 child node for every channel the hardware supports.
[all …]
|
| H A D | hwpmc.4 | 36 .Nd "Hardware Performance Monitoring Counter support"
71 driver virtualizes the hardware performance monitoring facilities in
95 measures hardware events for the system as a whole.
101 In counting modes, the PMCs count hardware events.
110 hardware events have been observed.
119 These PMCs count hardware events whenever a thread in their attached process is
130 have seen the configured number of hardware events.
140 These PMCs count hardware events seen by them independent of the
164 Processes are allowed to allocate as many PMCs as the hardware and
224 It signifies that the PMC will track hardware events for its
[all …]
|
| H A D | iicmux.4 | 50 the driver for the specific mux hardware in use.
55 I2C bus multiplexer (mux) hardware.
59 used by individual mux hardware drivers.
60 It will be loaded automatically when needed by a mux hardware driver.
67 Some hardware may be able to connect multiple downstream buses at the
80 Some mux hardware has the ability to disconnect all downstream buses
82 Other hardware must always have one of the downstream buses connected.
83 Individual mux hardware drivers typically provide a way to select which
98 The mux hardware maintains that upstream-to-downstream connection until
101 Before releasing ownership, the mux driver returns the mux hardware to
|
| /freebsd/sys/dev/scc/ |
| H A D | scc_if.m | 35 # The SCC hardware interface. The core SCC code is hardware independent.
36 # The details of the hardware are abstracted by the SCC hardware interface.
49 # attach() - attach hardware.
51 # have been allocated. The intend of this method is to setup the hardware
53 # The reset parameter informs the hardware driver whether a full device
55 # be used as system console and a hardware reset would disrupt output.
79 # service them on an interrupt priority basis. If the hardware cannot provide
86 # probe() - detect hardware.
88 # hardware exists. This function should also set the device description
89 # to something that represents the hardware.
|
| /freebsd/sys/contrib/device-tree/Bindings/net/ |
| H A D | fsl,fman-port.yaml | 13 The Frame Manager (FMan) supports several types of hardware ports:
31 Specifies the hardware port id.
32 Each hardware port on the FMan has its own hardware PortID.
33 Super set of all hardware Port IDs available at FMan Reference
34 Manual under "FMan Hardware Ports in Freescale Devices" table.
36 Each hardware port is assigned a 4KB, port-specific page in
37 the FMan hardware port memory region (which is part of the
38 FMan memory map). The first 4 KB in the FMan hardware ports
40 The subsequent 63 4KB pages are allocated to the hardware
|
| /freebsd/sys/contrib/device-tree/Bindings/mailbox/ |
| H A D | mediatek,gce-props.yaml | 14 single-core command dispatcher for MediaTek hardware. The Command Queue
19 driver. A device driver that uses the CMDQ driver to configure its hardware
21 channel corresponding to a GCE hardware thread to send a message, specifying
22 that the GCE thread to configure its hardware. The mailbox provider can also
23 reserve a mailbox channel to configure GCE hardware register by the specific
33 Some gce-events are hardware-bound and cannot be changed by software.
38 On the other hand, some gce-events are not hardware-bound and can be
40 event ID 855, which is not bound to any hardware, to 1 when the driver
44 to any hardware and is not yet used in any software driver.
45 To determine if the event ID is bound to the hardware or used by a
|
| /freebsd/lib/libpmc/ |
| H A D | pmc.3 | 29 .Nd library for accessing hardware performance monitoring counters
38 hardware performance counters to gather performance data about
64 These PMCs only measure hardware events when the processes they are
88 to availability of hardware resources.
91 measured by hardware.
92 The syntax used for specifying a hardware event along with additional
220 Fixed function hardware counters presents in CPUs conforming to the
224 Programmable hardware counters present in CPUs conforming to the
228 Programmable hardware counters present in
249 Capabilities of performance monitoring hardware are denoted using
[all …]
|
| H A D | pmc_disable.3 | 30 .Nd administrative control of hardware performance counters
40 These functions allow specific hardware performance monitoring
42 The hardware performance counters available on each CPU are numbered
52 disables the hardware counter numbered by argument
59 enables the hardware counter numbered by argument
64 Hardware PMCs that are currently in use by applications cannot be
67 hardware PMCs in the system with the same pmc number as being in-use.
76 specified a hardware PMC is currently in use.
|
| /freebsd/share/man/man9/ |
| H A D | ieee80211_crypto.9 | 120 The cryptographic framework supports hardware acceleration of ciphers
122 driver is unable to provide necessary hardware services.
150 hardware.
171 they are involved only when providing hardware acceleration of
196 handles hardware key state reloading from software key state, such
199 Drivers identify ciphers they have hardware support for through the
204 If hardware support is available then a driver should also fill in the
217 for updating hardware key state.
227 Otherwise, e.g. if hardware resources are not available, the driver will
235 mbuf flag to indicate the hardware has decrypted the payload.
[all …]
|
| /freebsd/sys/dev/uart/ |
| H A D | uart_if.m | 36 # The UART hardware interface. The core UART code is hardware independent.
37 # The details of the hardware are abstracted by the UART hardware interface.
52 # attach() - attach hardware.
56 # The intend of this method is to setup the hardware for normal operation.
61 # detach() - detach hardware.
65 # The intend of this method is to disable the hardware.
82 # by the hardware driver are cleared as a side-effect. A second call to
105 # service them on an interrupt priority basis. If the hardware cannot provide
122 # probe() - detect hardware.
124 # hardware exists. This function should also set the device description
[all …]
|
| /freebsd/share/doc/smm/02.config/ |
| H A D | 2.t | 48 available hardware
53 for identical hardware, but may have different locations for the root
96 code in the driver which understood how to handle this non-standard hardware
118 on the hardware and expected job mix. The rules
137 Hardware devices
142 those hardware devices
145 addresses, bus interconnects, etc. A system's hardware may be configured
147 whatsoever. Most people do not configure hardware devices into the
150 against a hardware
153 has hardware problems).
[all …]
|
| /freebsd/sys/contrib/device-tree/src/mips/brcm/ |
| H A D | bcm63268-comtrend-vr-3032u.dts | 29 brcm,hardware-controlled;
35 brcm,hardware-controlled;
66 brcm,hardware-controlled;
71 brcm,hardware-controlled;
76 brcm,hardware-controlled;
81 brcm,hardware-controlled;
86 brcm,hardware-controlled;
91 brcm,hardware-controlled;
96 brcm,hardware-controlled;
|
| /freebsd/sys/dev/isci/scil/ |
| H A D | scu_remote_node_context.h | 61 * hardware to describe a remote node context.
73 * @brief This structure contains the SCU hardware definition for an SSP
90 * This field tells the SCU hardware how many simultaneous connections that
96 * This field tells the SCU hardware which logical port to associate with this
113 * This field must be set to TRUE when the hardware DMAs the remote node
114 * context to the hardware SRAM. When the remote node is being invalidated
153 * This field tells the SCU hardware how long this device may occupy the
159 * This field tells the SCU hardware how long to maintain a connection when
172 * This field is tells the hardware what to program for the connection rate in
178 * This field tells the SCU hardware what to program for the features in the
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/regulator/ |
| H A D | regulator.yaml | 59 description: ramp delay for regulator(in uV/us) For hardware which supports
96 depends on the capabilities of every hardware so each device binding
104 every hardware so each device binding document explains which values
128 hardware performs emergency shutdown. Zero can be passed to disable
134 the hardware probably is malfunctional and damage prevention is requested.
139 description: Set over current warning limit. This is a limit where hardware
147 hardware performs emergency shutdown. Zero can be passed to disable
154 the hardware probably is malfunctional and damage prevention is requested
160 description: Set over voltage warning limit. This is a limit where hardware
169 hardware perform
[all...] |
| /freebsd/sys/net/ |
| H A D | if_arp.h | 46 u_short ar_hrd; /* format of hardware address */
47 #define ARPHRD_ETHER 1 /* ethernet hardware format */
49 #define ARPHRD_FRELAY 15 /* frame relay hardware format */
50 #define ARPHRD_IEEE1394 24 /* firewire hardware format */
51 #define ARPHRD_INFINIBAND 32 /* infiniband hardware format */
53 u_char ar_hln; /* length of hardware address */
58 #define ARPOP_REVREQUEST 3 /* request protocol address given hardware */
67 u_char ar_sha[]; /* sender hardware address */
69 u_char ar_tha[]; /* target hardware address */
88 struct sockaddr arp_ha; /* hardware addres
[all...] |
| /freebsd/sys/contrib/device-tree/Bindings/crypto/ |
| H A D | brcm,spu-crypto.txt | 1 The Broadcom Secure Processing Unit (SPU) hardware supports symmetric
2 cryptographic offload for Broadcom SoCs. A SoC may have multiple SPU hardware
7 brcm,spum-crypto - for devices with SPU-M hardware
8 brcm,spu2-crypto - for devices with SPU2 hardware
9 brcm,spu2-v2-crypto - for devices with enhanced SPU2 hardware features like SHA3
11 brcm,spum-nsp-crypto - for the Northstar Plus variant of the SPU-M hardware
|
| /freebsd/sys/dev/ioat/ |
| H A D | ioat.h | 48 * operations can be pipelined on some hardware. E.g., operation 2's source
74 * Hardware revision number. Different hardware revisions support different
82 * Hardware capabilities. Different hardware revisions support different
84 * them from hardware version.
87 * only be supported on the first two channels of some hardware.
142 * - ERANGE if the given value exceeds the delay supported by the hardware.
143 * (All current hardware supports a maximum of 0x3fff microseconds delay.)
144 * - ENODEV if the hardware does not support interrupt coalescing.
150 * ioat_set_interrupt_coalesce(). If the hardware does not support coalescing,
242 * Issues a null operation. This issues the operation to the hardware, but the
[all …]
|