Home
last modified time | relevance | path

Searched refs:hardware (Results 1 – 25 of 743) sorted by relevance

12345678910>>...30

/freebsd/sys/contrib/device-tree/Bindings/leds/
H A Dleds-bcm6328.txt4 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 …]
/freebsd/sys/contrib/device-tree/Bindings/spi/
H A Dspi-sprd-adi.txt5 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/contrib/device-tree/src/mips/brcm/
H A Dbcm63268-comtrend-vr-3032u.dts29 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/scc/
H A Dscc_if.m35 # 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/crypto/
H A Dbrcm,spu-crypto.txt1 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/sbin/dhclient/
H A Dparse.c158 parse_hardware_param(FILE *cfile, struct hardware *hardware) in parse_hardware_param() argument
168 hardware->htype = HTYPE_ETHER; in parse_hardware_param()
171 hardware->htype = HTYPE_IEEE802; in parse_hardware_param()
174 hardware->htype = HTYPE_FDDI; in parse_hardware_param()
195 if (hlen > sizeof(hardware->haddr)) { in parse_hardware_param()
199 hardware->hlen = hlen; in parse_hardware_param()
200 memcpy((unsigned char *)&hardware->haddr[0], t, in parse_hardware_param()
201 hardware->hlen); in parse_hardware_param()
202 if (hlen < sizeof(hardware->haddr)) in parse_hardware_param()
203 memset(&hardware->haddr[hlen], 0, in parse_hardware_param()
[all …]
H A Ddhcpd.h113 struct hardware *haddr;
117 struct hardware { struct
201 struct hardware hw_address;
263 int, unsigned int, struct iaddr, struct hardware *);
289 void parse_hardware_param(FILE *, struct hardware *);
313 struct sockaddr_in *, struct hardware *);
317 struct dhcp_packet *, int, unsigned int, struct iaddr, struct hardware *);
425 ssize_t decode_hw_header(unsigned char *, int, struct hardware *);
/freebsd/contrib/llvm-project/lldb/source/Breakpoint/
H A DStoppointSite.cpp15 StoppointSite::StoppointSite(break_id_t id, addr_t addr, bool hardware) in StoppointSite() argument
16 : m_id(id), m_addr(addr), m_is_hardware_required(hardware), m_byte_size(0), in StoppointSite()
20 bool hardware) in StoppointSite() argument
21 : m_id(id), m_addr(addr), m_is_hardware_required(hardware), in StoppointSite()
/freebsd/sys/dev/uart/
H A Duart_if.m36 # 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/sys/contrib/device-tree/Bindings/serial/
H A Dnvidia,tegra194-tcu.txt3 The TCU is a system for sharing a hardware UART instance among multiple
7 with the hardware implementing the TCU.
16 "rx" - Mailbox for receiving data from hardware UART
17 "tx" - Mailbox for transmitting data to hardware UART
H A Dsirf-uart.txt8 - fifosize : Should define hardware rx/tx fifo size
12 - uart-has-rtscts: we have hardware flow controller pins in hardware
/freebsd/sys/contrib/device-tree/Bindings/arm/msm/
H A Dqcom,saw2.txt4 Adaptive Voltage Scaling (AVS) hardware. The SPM is a programmable
5 power-controller that transitions a piece of hardware (like a processor or
10 Multiple revisions of the SAW hardware are supported using these Device Nodes.
13 data due the differences in hardware capabilities. Hence the SoC name, the
14 version of the SAW hardware in that SoC and the distinction between cpu (big
/freebsd/sys/contrib/device-tree/Bindings/gpio/
H A Dsgpio-aspeed.txt23 - ngpios : number of *hardware* GPIO lines, see gpio.txt. This will expose
24 2 software GPIOs per hardware GPIO: one for hardware input, one for hardware
/freebsd/sys/dev/bhnd/bhndb/
H A Dbhndb_bus_if.m77 * Return a generic hardware configuration to be used by
105 * Return the hardware specification table to be used when identifying the
106 * bridge's full hardware configuration.
117 * Return the hardware priority table to be used when allocating bridge
129 * Return true if the hardware required by @p core is unpopulated or
132 * In some cases, the core's pins may be left floating, or the hardware
/freebsd/sys/contrib/device-tree/Bindings/dma/
H A Dsnps-dma.txt7 - dma-channels: Number of channels supported by hardware
16 - data-width: Maximum data width supported by hardware per AHB master
21 - data_width: Maximum data width supported by hardware per AHB master
26 - multi-block: Multi block transfers supported by hardware. Array property with
H A Dsnps,dw-axi-dmac.txt8 - dma-channels: Number of channels supported by hardware.
9 - snps,dma-masters: Number of AXI masters supported by the hardware.
10 - snps,data-width: Maximum AXI data width supported by hardware.
/freebsd/sys/dev/bhnd/cores/chipc/
H A Dbhnd_chipc_if.m60 * hardware (e.g. if @p dev is an EXTIF core).
76 * Currently, the only known valid use-case is in implementing a hardware
96 * Enable hardware access to the SPROM/OTP source.
101 * @retval EBUSY If enabling the hardware may conflict with
109 * Release hardware access to the SPROM/OTP source.
/freebsd/sys/contrib/device-tree/Bindings/reset/
H A Dst,sti-softreset.txt9 The actual action taken when softreset is asserted is hardware dependent.
10 However, when asserted it may not be possible to access the hardware's
11 registers and after an assert/deassert sequence the hardware's previous state
H A Dst,sti-picophyreset.txt8 The actual action taken when softreset is asserted is hardware dependent.
9 However, when asserted it may not be possible to access the hardware's
10 registers and after an assert/deassert sequence the hardware's previous state
H A Dst,sti-powerdown.txt10 The actual action taken when powerdown is asserted is hardware dependent.
11 However, when asserted it may not be possible to access the hardware's
12 registers and after an assert/deassert sequence the hardware's previous state
H A Dimg,pistachio-reset.txt8 The actual action taken when soft reset is asserted is hardware dependent.
9 However, when asserted it may not be possible to access the hardware's
10 registers, and following an assert/deassert sequence the hardware's previous
/freebsd/contrib/llvm-project/llvm/lib/Target/MSP430/
H A DMSP430.td26 "Enable 16-bit hardware multiplier">;
30 "Enable 32-bit hardware multiplier">;
34 "Enable F5 series hardware multiplier">;
/freebsd/contrib/llvm-project/lldb/source/Host/common/
H A DNativeWatchpointList.cpp17 bool hardware) { in Add() argument
18 m_watchpoints[addr] = {addr, size, watch_flags, hardware}; in Add()
/freebsd/sys/contrib/device-tree/Bindings/watchdog/
H A Datmel-sama5d4-wdt.txt10 - atmel,watchdog-type: should be "hardware" or "software".
11 "hardware": enable watchdog fault reset. A watchdog fault triggers
31 atmel,watchdog-type = "hardware";
/freebsd/contrib/file/magic/Magdir/
H A Dhardware3 # $File: hardware,v 1.1 2018/08/02 06:32:52 christos Exp $
4 # hardware magic

12345678910>>...30