| /linux/Documentation/translations/zh_CN/networking/ |
| H A D | timestamping.rst | 554 3.2.1 DSA(分布式交换架构)交换机 558 执行端口多路复用或可选转发加速功能。每个 DSA 交换机端口在用户看来都是独立的 562 当 DSA 交换机连接到主机端口时,PTP 同步必须受到限制,因为交换机的可变排队 563 延迟引入了主机端口与其 PTP 伙伴之间的路径延迟抖动。因此,一些 DSA 交换机 565 仅测量线缆和 PHY 传播延迟。支持 Linux 的 DSA 交换机暴露了与任何其他网络 566 接口相同的 ABI(除了 DSA 接口在网络 I/O 方面实际上是虚拟的,它们确实有自 567 己的PHC)。典型地,但不是强制性地,所有DSA 交换机接口共享相同的 PHC。 569 通过设计,DSA 交换机对连接到其主机端口的 PTP 时间戳不需要任何特殊的驱动程 570 序处理。然而,当主机端口也支持 PTP 时间戳时,DSA 将负责拦截 572 SO_TIMESTAMPING API 不允许为同一数据包传递多个硬件时间戳,因此除了 DSA [all …]
|
| /linux/Documentation/networking/dsa/ |
| H A D | configuration.rst | 4 DSA switch configuration from userspace 7 The DSA switch configuration is not integrated into the main userspace 15 To configure a DSA switch a couple of commands need to be executed. In this 32 Through DSA every port of a switch is handled like a normal linux Ethernet 42 - when a DSA user interface is brought up, the conduit interface is 44 - when the conduit interface is brought down, all DSA user interfaces are 88 DSA switches. These switches are capable to tag incoming and outgoing traffic 302 The existing DSA switches do not have the necessary hardware support to keep 308 Up until kernel v4.14, DSA only supported user space management of bridge FDB 319 Due to a bug, the bridge bypass FDB implementation provided by DSA did not [all …]
|
| H A D | bcm_sf2.rst | 41 The driver is located in ``drivers/net/dsa/bcm_sf2.c`` and is implemented as a DSA 51 Overall, the SF2 driver is a fairly regular DSA driver; there are a few 57 The DSA platform device driver is probed using a specific compatible string 58 provided in ``net/dsa/dsa.c``. The reason for that is because the DSA subsystem gets 59 registered as a platform device driver currently. DSA will provide the needed 70 Broadcom switches connected to a SF2 require the use of the DSA user MDIO bus 74 "double" programming. Using DSA, and setting ``ds->phys_mii_mask`` accordingly, we
|
| H A D | lan9303.rst | 13 The driver is implemented as a DSA driver, see ``Documentation/networking/dsa/dsa.rst``. 21 interfaces (which is the default state of a DSA device). Due to HW limitations,
|
| H A D | b53.rst | 17 DSA driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the 36 DSA driver and will work like all DSA drivers which supports tagging.
|
| H A D | sja1105.rst | 120 done by the DSA net devices, which populate the PCP field of the tagging header 122 offloaded flows can be steered to TX queues based on the VLAN PCP, but the DSA 125 sub-interface on the DSA conduit port, and send normal (0x8100) VLAN-tagged 392 MDIO bus available to Linux within the system (e.g. to the DSA conduit's MDIO
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-dsa | 7 tagging protocol used by the DSA network devices that are 10 attached DSA switches, if this operation is supported by the 11 driver. Changing the tagging protocol must be done with the DSA
|
| H A D | sysfs-bus-event_source-devices-dsa | 7 perf_event_attr.config1 for the IDXD DSA pmu. (See also 13 IDXD DSA Spec for possible attribute values):: 29 IDXD DSA pmu is bound for access to all dsa pmu
|
| /linux/crypto/asymmetric_keys/ |
| H A D | Kconfig | 58 bool "Waive rejection of authenticatedAttributes for ML-DSA" 62 Due to use of CMS_NOATTR with ML-DSA not being supported in 64 allows authenticatedAttributes to be used with ML-DSA for
|
| /linux/drivers/net/dsa/sja1105/ |
| H A D | Kconfig | 32 the SJA1105 DSA driver. 41 engine in the SJA1105 DSA driver, which is controlled using a
|
| /linux/net/dsa/ |
| H A D | Kconfig | 88 tristate "Tag driver for Marvell switches using DSA headers" 92 Marvell switches which use DSA headers. 95 tristate "Tag driver for Marvell switches using EtherType DSA headers" 99 Marvell switches which use EtherType DSA headers.
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | hisilicon-hns-dsaf.txt | 1 Hisilicon DSA Fabric device controller 12 - interrupts: should contain the DSA Fabric and rcb interrupt.
|
| /linux/lib/crypto/tests/ |
| H A D | Kconfig | 39 tristate "KUnit tests for ML-DSA" if !KUNIT_ALL_TESTS 44 KUnit tests for the ML-DSA digital signature algorithm.
|
| /linux/drivers/net/ethernet/mscc/ |
| H A D | Kconfig | 24 used by switchdev as well as by DSA drivers.
|
| /linux/Documentation/devicetree/bindings/net/dsa/ |
| H A D | lan9303.txt | 21 Note: always use 'reg = <0/1/2>;' for the three DSA ports, even if the device is
|
| /linux/arch/arm/boot/dts/intel/ixp/ |
| H A D | intel-ixp42x-ixdpg425.dts | 93 * of Realtek DSA switch on the board.
|
| H A D | intel-ixp42x-usrobotics-usr8200.dts | 239 /* EthC LAN connected to the Marvell DSA Switch */
|
| /linux/arch/arm64/boot/dts/marvell/ |
| H A D | armada-3720-espressobin.dtsi | 16 /* for DSA user port device */
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-linksys-viper.dts | 226 /* eth1 is connected to the switch at port 6. However DSA only supports a
|
| H A D | orion5x-netgear-wnr854t.dts | 212 /* Hardwired to DSA switch */
|
| H A D | kirkwood-dir665.dts | 256 /* eth1 is connected to the switch as well. However DSA only supports a
|
| /linux/drivers/video/fbdev/ |
| H A D | imsttfb.c | 48 DSA = 3, /* 0x0C */ enumerator 1010 write_reg_le32(par->dc_regs, DSA, dy + dx); in imsttfb_fillrect() 1021 write_reg_le32(par->dc_regs, DSA, dy + dx); in imsttfb_fillrect() 1078 write_reg_le32(par->dc_regs, DSA, fb_offset_new); in imsttfb_copyarea()
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx_2 | 135 - Allocate separately from the HCB the array for CCBs hashed by DSA.
|
| /linux/Documentation/arch/x86/ |
| H A D | sva.rst | 73 For example, the Intel Data Streaming Accelerator (DSA) uses 285 DSA spec:
|
| /linux/Documentation/crypto/ |
| H A D | asymmetric-keys.rst | 80 1a39e171 I----- 1 perm 3f010000 0 0 asymmetric modsign.0: DSA 5acc2142 [] 317 public-key algorithm such as RSA and DSA this will likely be a printable
|