Home
last modified time | relevance | path

Searched refs:HW (Results 1 – 25 of 338) sorted by relevance

12345678910>>...14

/linux-6.15/Documentation/scsi/
H A Dscsi-parameters.rst19 advansys= [HW,SCSI]
22 aha152x= [HW,SCSI]
25 aha1542= [HW,SCSI]
28 aic7xxx= [HW,SCSI]
31 aic79xx= [HW,SCSI]
34 atascsi= [HW,SCSI]
37 BusLogic= [HW,SCSI]
41 gvp11= [HW,SCSI]
46 mac5380= [HW,SCSI]
57 NCR_D700= [HW,SCSI]
[all …]
/linux-6.15/Documentation/networking/device_drivers/ethernet/huawei/
H A Dhinic.rst35 specific HW details about HW data structure formats.
43 HW Interface:
49 Configuration Status Registers Area that describes the HW Registers on the
63 card by AEQs. Also set the addresses of the IO CMDQs in HW.
78 used to set the QPs addresses in HW. The commands completion events are
87 HW device:
90 HW device - de/constructs the HW Interface, the MGMT components on the
101 Port Commands - Send commands to the HW device for port management
104 Tx Queues - Logical Tx Queues that use the HW Send Queues for transmit.
105 The Logical Tx queue is not dependent on the format of the HW Send Queue.
[all …]
/linux-6.15/Documentation/watchdog/
H A Dmlx-wdt.rst13 There are 2 types of HW watchdog implementations.
16 Actual HW timeout can be defined as a power of 2 msec.
22 Actual HW timeout is defined in sec. and it's the same as
31 Type 1 HW watchdog implementation exist in old systems and
32 all new systems have type 2 HW watchdog.
33 Two types of HW implementation have also different register map.
35 Type 3 HW watchdog implementation can exist on all Mellanox systems
54 This mlx-wdt driver supports both HW watchdog implementations.
65 Access to HW registers is performed through a generic regmap interface.
/linux-6.15/Documentation/networking/dsa/
H A Dlan9303.rst21 interfaces (which is the default state of a DSA device). Due to HW limitations,
22 no HW MAC learning takes place in this mode.
24 When both user ports are joined to the same bridge, the normal HW MAC learning
25 is enabled. This means that unicast traffic is forwarded in HW. Broadcast and
26 multicast is flooded in HW. STP is also supported in this mode. The driver
37 - The HW does not support VLAN-specific fdb entries
/linux-6.15/Documentation/translations/zh_CN/infiniband/
H A Dopa_vnic.rst117 依赖于HW的VNIC功能是HFI1驱动的一部分。它实现了分配和释放OPA_VNIC RDMA
118 netdev的动作。它涉及VNIC功能的HW资源分配/管理。它与网络堆栈接口并实现所
120 并提供对它们的HW访问。在将数据包向上传递到网络堆栈之前，它把Omni-Path头
126 RDMA netdev设备。它在需要时覆盖由依赖HW的VNIC驱动设置的net_device_ops函数，
129 RDMA netdev控制操作将任何控制信息传递给依赖于HW的驱动程序::
/linux-6.15/Documentation/ABI/testing/
H A Dsysfs-bus-coresight-devices-etb1027 2. The value is read directly from HW register RDP, 0x004.
34 is read directly from HW register STS, 0x00C.
42 interface. The value is read directly from HW register RRP,
52 from HW register RWP, 0x018.
59 read directly from HW register TRG, 0x01C.
66 is read directly from HW register CTL, 0x020.
73 register. The value is read directly from HW register FFSR,
81 register. The value is read directly from HW register FFCR,
H A Dsysfs-bus-coresight-devices-tmc15 The value is read directly from HW register RSZ, 0x004.
22 is read directly from HW register STS, 0x00C.
30 interface. The value is read directly from HW register RRP,
40 from HW register RWP, 0x018.
47 read directly from HW register TRG, 0x01C.
54 is read directly from HW register CTL, 0x020.
61 register. The value is read directly from HW register FFSR,
69 register. The value is read directly from HW register FFCR,
H A Dsysfs-bus-coresight-devices-etm4x337 The value it taken directly from the HW.
344 (0x310). The value is taken directly from the HW.
380 from the HW.
435 The value is taken directly from the HW.
442 The value is taken directly from the HW.
459 The value is taken directly from the HW.
466 The value is taken directly from the HW.
473 The value is taken directly from the HW.
502 the HW.
510 from the HW.
[all …]
/linux-6.15/Documentation/devicetree/bindings/clock/ti/
H A Dti,interface-clock.yaml26 - ti,omap3-hsotgusb-interface-clock # interface clock with USB specific HW handling
27 - ti,omap3-dss-interface-clock # interface clock with DSS specific HW handling
28 - ti,omap3-ssi-interface-clock # interface clock with SSI specific HW handling
29 - ti,am35xx-interface-clock # interface clock with AM35xx specific HW handling
30 - ti,omap2430-interface-clock # interface clock with OMAP2430 specific HW handling
/linux-6.15/Documentation/devicetree/bindings/regulator/
H A Drohm,bd71815-regulator.yaml56 PMIC "RUN" state voltage in uV when PMIC HW states are used. See
76 PMIC "SUSPEND" state voltage in uV when PMIC HW states are used. See
85 PMIC "LPSR" state voltage in uV when PMIC HW states are used. See
94 # (LPSR/SUSPEND). The voltage is automatically changed when HW
96 # buck voltages to not be toggled by HW state. Enable status may still
97 # be toggled by state changes depending on HW default settings.
106 # for each of the HW states (RUN/SNVS/SUSPEND/LPSR). HW defaults can
/linux-6.15/Documentation/driver-api/iio/
H A Dhw-consumer.rst2 HW consumer
6 The Industrial I/O HW consumer offers a way to bond these IIO devices without
18 HW consumer setup
22 A typical IIO HW consumer setup looks like this::
/linux-6.15/drivers/crypto/intel/keembay/
H A DKconfig2 tristate "Support for Intel Keem Bay OCS AES/SM4 HW acceleration"
12 Provides HW acceleration for the following transformations:
20 bool "Support for Intel Keem Bay OCS AES/SM4 ECB HW acceleration"
31 bool "Support for Intel Keem Bay OCS AES/SM4 CTS HW acceleration"
43 tristate "Support for Intel Keem Bay OCS ECC HW acceleration"
62 tristate "Support for Intel Keem Bay OCS HCU HW acceleration"
/linux-6.15/Documentation/infiniband/
H A Dopa_vnic.rst104 OPA VNIC functionality has a HW dependent component and a HW
112 The HW dependent VNIC functionality is part of the HFI1 driver. It
114 It involves HW resource allocation/management for VNIC functionality.
117 packets in the transmit path and provides HW access to them. It strips
121 The OPA VNIC module implements the HW independent VNIC functionality.
127 set by HW dependent VNIC driver where required to accommodate any control
131 interface. It also passes any control information to the HW dependent driver
/linux-6.15/net/tls/
H A DKconfig21 bool "Transport Layer Security HW offload"
28 Enable kernel support for HW offload of the TLS protocol.
37 Enable kernel support for legacy HW offload of the TLS protocol,
/linux-6.15/Documentation/networking/
H A Diou-zcrx.rst17 NIC HW Requirements
20 Several NIC HW features are required for io_uring ZC Rx to work. For now the
33 Specific HW Rx queues are configured for this feature, but modern NICs
34 typically distribute flows across all HW Rx queues. Flow steering is required
35 to ensure that only desired flows are directed towards HW queues that are
60 Carve out half of the HW Rx queues for zero copy using RSS::
127 /* this is the HW queue with desired flow steered into it */
H A Dxfrm_device.rst108 - enable the HW offload of the SA
139 set up HW for send
146 When a packet is received and the HW has indicated that it offloaded a
175 Driver will check packet seq number and update HW ESN state machine if needed.
178 HW adds and deletes XFRM headers. So in RX path, XFRM stack is bypassed if HW
180 and not encrypted, the HW is responsible to perform it.
194 Outcome of HW handling packets, the XFRM core can't count hard, soft limits.
195 The HW/driver are responsible to perform it and provide accurate data when
/linux-6.15/drivers/gpu/drm/sti/
H A DNOTES3 The STMicroelectronics stiH SoCs use a common chain of HW display IP blocks:
19 - The VTG (Video Timing Generators) build Vsync signals used by the other HW IP
20 Note that some stiH drivers support only a subset of thee HW IP.
37 2. DRM / HW mapping
/linux-6.15/drivers/cpufreq/
H A DKconfig.arm134 tristate "MediaTek CPUFreq HW driver"
138 Support for the CPUFreq HW driver.
139 Some MediaTek chipsets have a HW engine to offload the steps
142 The driver implements the cpufreq interface for this HW engine.
143 Say Y if you want to support CPUFreq HW.
162 tristate "QCOM CPUFreq HW driver"
166 Support for the CPUFreq HW driver.
167 Some QCOM chipsets have a HW engine to offload the steps
170 The driver implements the cpufreq interface for this HW engine.
171 Say Y if you want to support CPUFreq HW.
/linux-6.15/Documentation/arch/powerpc/
H A Dcpu_families.rst168 - e6500 adds HW loaded indirect TLB entries.
201 | e6500 (HW TLB) (Multithreaded) |
208 - Book3E, software loaded TLB + HW loaded indirect TLB entries.
/linux-6.15/Documentation/networking/device_drivers/ethernet/stmicro/
H A Dstmmac.rst159 This parameter changes the default HW FIFO Threshold control value.
263 checks to the HW using MAC and PHY loopback mechanisms::
328 PHYLIB stuff. In fact, the HW provides a subset of extended registers to
372 7) HW uses the GMAC core::
380 9) Core is able to perform TX Checksum and/or RX Checksum in HW::
470 30) HW uses GMAC>4 cores::
474 31) HW is sun8i based::
494 36) HW uses XGMAC>2.10 cores::
664 HW Capabilities
669 understand if EEE, HW csum, PTP, enhanced descriptor etc are actually
[all …]
/linux-6.15/Documentation/virt/kvm/devices/
H A Dxive.rst21 The KVM device exposes different MMIO ranges of the XIVE HW which
52 interrupts are from a different HW controller (PHB4) and the ESB
56 kvmppc_xive_clr_mapped() are called when the device HW irqs are
60 The handler will insert the ESB page corresponding to the HW
119 -ENXIO Could not allocate underlying HW interrupt
147 underlying HW interrupt failed
192 -EIO Configuration of the underlying HW failed
211 called the NVT. When a VP is not dispatched on a HW processor
212 thread, this structure can be updated by HW if the VP is the target
/linux-6.15/Documentation/arch/x86/
H A Dtsx_async_abort.rst69 …0 0 0 HW default Yes Same as MDS Same as MDS
71 …0 1 0 HW default No Need ucode update Need ucode up…
84 … 0 0 0 HW default Yes Same as MDS Same as MDS
86 …0 1 0 HW default No Need ucode update Need ucode up…
99 …0 0 0 HW default Yes Same as MDS Same as MDS
101 …0 1 0 HW default No Need ucode update Need ucode up…
/linux-6.15/Documentation/devicetree/bindings/reset/
H A Dreset.txt21 in hardware for a reset signal to affect multiple logically separate HW blocks
23 the DT node of each affected HW block, since if activated, an unrelated block
26 children of the bus are affected by the reset signal, or an individual HW
28 appropriate software access to the reset signals in order to manage the HW,
29 rather than to slavishly enumerate the reset signal that affects each HW
/linux-6.15/arch/arm64/boot/dts/rockchip/
H A Drk3588-jaguar-pre-ict-tester.dtso79 * but GPIO3_C6 would catch this HW soldering issue.
92 * the loop doesn't exist on HW (soldering issue on
101 * but GPIO3_C6 would catch this HW soldering issue.
135 * the loop doesn't exist on HW (soldering issue on
145 * the loop doesn't exist on HW (soldering issue on
155 * the loop doesn't exist on HW (soldering issue on
165 * the loop doesn't exist on HW (soldering issue on
/linux-6.15/Documentation/devicetree/bindings/iommu/
H A Dmediatek,iommu.yaml14 this M4U have two generations of HW architecture. Generation one uses flat
52 As above, The Multimedia HW will go through SMI and M4U while it
53 access EMI. SMI is a bridge between m4u and the Multimedia HW. It contain
55 HW should go though the m4u for translation or bypass it and talk
59 Normally we specify a local arbiter(larb) for each multimedia HW
62 video decode local arbiter, all these ports are according to the video HW.
127 This is the mtk_m4u_id according to the HW. Specifies the mtk_m4u_id as

12345678910>>...14