Searched +full:wi +full:- +full:fi (Results 1 – 14 of 14) sorted by relevance
/Documentation/devicetree/bindings/arm/ti/ |
D | k3.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Nishanth Menon <nm@ti.com> 22 - description: K3 AM62A7 SoC 24 - enum: 25 - ti,am62a7-sk 26 - const: ti,am62a7 28 - description: K3 AM62P5 SoC and Boards 30 - enum: [all …]
|
/Documentation/devicetree/bindings/net/wireless/ |
D | qcom,ath10k.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Kalle Valo <kvalo@kernel.org> 18 - qcom,ath10k # SDIO-based devices 19 - qcom,ipq4019-wifi 20 - qcom,wcn3990-wifi # SNoC-based devices 25 reg-names: 27 - const: membase 33 interrupt-names: [all …]
|
D | brcm,bcm4329-fmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/wireless/brcm,bcm4329-fmac.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Arend van Spriel <arend@broadcom.com> 19 - $ref: ieee80211.yaml# 24 - items: 25 - enum: 26 - brcm,bcm43143-fmac 27 - brcm,bcm4341b0-fmac [all …]
|
/Documentation/hwmon/ |
D | asus_ec_sensors.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later 7 * PRIME X470-PRO 8 * PRIME X570-PRO 9 * Pro WS X570-ACE 10 * ProArt X570-CREATOR WIFI 11 * ProArt B550-CREATOR 13 * ROG CROSSHAIR VIII HERO (WI-FI) 19 * ROG MAXIMUS XI HERO (WI-FI) 20 * ROG STRIX B550-E GAMING 21 * ROG STRIX B550-I GAMING [all …]
|
D | asus_wmi_sensors.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later 7 * PRIME X399-A, 8 * PRIME X470-PRO, 11 * ROG CROSSHAIR VI HERO (WI-FI AC), 13 * ROG CROSSHAIR VII HERO (WI-FI), 14 * ROG STRIX B450-E GAMING, 15 * ROG STRIX B450-F GAMING, 16 * ROG STRIX B450-I GAMING, 17 * ROG STRIX X399-E GAMING, 18 * ROG STRIX X470-F GAMING, [all …]
|
/Documentation/networking/device_drivers/wifi/ |
D | index.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 Wi-Fi Device Drivers
|
/Documentation/devicetree/bindings/arm/bcm/ |
D | brcm,bcm53573.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 Broadcom BCM53573 / BCM47189 Wi-Fi SoCs derived from Northstar. 13 - Rafał Miłecki <rafal@milecki.pl> 20 - description: BCM53573 based boards 22 - enum: 23 - tenda,ac6-v1 24 - tenda,w15e-v1 25 - const: brcm,bcm53573 [all …]
|
D | brcm,bcm4708.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 Broadcom BCM4708/47081/4709/47094/53012 Wi-Fi/network SoCs based 14 - Florian Fainelli <f.fainelli@gmail.com> 15 - Hauke Mehrtens <hauke@hauke-m.de> 16 - Rafal Milecki <zajec5@gmail.com> 23 - description: BCM4708 based boards 25 - enum: 26 - asus,rt-ac56u [all …]
|
/Documentation/devicetree/bindings/arm/ |
D | fsl.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Shawn Guo <shawnguo@kernel.org> 11 - Li Yang <leoyang.li@nxp.com> 18 - description: i.MX1 based Boards 20 - enum: 21 - armadeus,imx1-apf9328 22 - fsl,imx1ads 23 - const: fsl,imx1 [all …]
|
/Documentation/devicetree/bindings/net/bluetooth/ |
D | brcm,bcm4377-bluetooth.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/net/bluetooth/brcm,bcm4377-bluetooth.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Sven Peter <sven@svenpeter.dev> 13 This binding describes Broadcom BCM4377 family PCIe-attached bluetooth chips 14 usually found in Apple machines. The Wi-Fi part of the chip is described in 15 bindings/net/wireless/brcm,bcm4329-fmac.yaml. 18 - $ref: bluetooth-controller.yaml# 23 - pci14e4,5fa0 # BCM4377 [all …]
|
/Documentation/driver-api/thermal/ |
D | intel_dptf.rst | 1 .. SPDX-License-Identifier: GPL-2.0 12 ------------ 31 ---------------------------- 43 "42A441D6-AE6A-462b-A84B-4A8CE79027D3" : Passive 1 45 "3A95C389-E4B8-4629-A526-C52C88626BAE" : Active 47 "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" : Critical 49 "63BE270F-1C11-48FD-A6F7-3AF253FF3E2D" : Adaptive performance 51 "5349962F-71E6-431D-9AE8-0A635B710AEE" : Emergency call 53 "9E04115A-AE87-4D1C-9500-0F3E340BFE75" : Passive 2 55 "F5A35014-C209-46A4-993A-EB56DE7530A1" : Power Boss [all …]
|
/Documentation/input/devices/ |
D | xpad.rst | 2 xpad - Linux USB driver for Xbox compatible controllers 5 This driver exposes all first-party and third-party Xbox compatible 16 the Xbox One's rumble protocol has not been reverse-engineered but in 25 - if you are using a known controller 26 - if you are using a known dance pad 27 - if using an unknown device (one not listed below), what you set in the 28 module configuration for "Map D-PAD to buttons rather than axes for unknown 33 If you said Y it will map the d-pad to buttons, which is needed for dance 43 ------------------ 46 The jstest-program from joystick-1.2.15 (jstest-version 2.1.0) will report 8 [all …]
|
/Documentation/ABI/testing/ |
D | sysfs-bus-usb | 10 This allows to avoid side-effects with drivers 28 drivers, non-authorized one are not. By default, wired 33 Contact: linux-usb@vger.kernel.org 67 What: /sys/bus/usb-serial/drivers/.../new_id 69 Contact: linux-usb@vger.kernel.org 72 extra bus folder "usb-serial" in sysfs; apart from that 97 If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged 113 If CONFIG_PM is set and a USB 3.0 lpm-capable device is plugged 141 attribute allows user-space to know whether the device is 145 an on-screen keyboard if the only wireless keyboard is [all …]
|
/Documentation/firmware-guide/acpi/ |
D | enumeration.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 that are accessed through memory-mapped registers. 15 In order to support this and re-use the existing drivers as much as 18 - Devices that have no bus connector resource are represented as 21 - Devices behind real busses where there is a connector resource 34 This means that when ACPI_HANDLE(dev) returns non-NULL the device was 36 device-specific configuration. There is an example of this below. 43 for the device and add supported ACPI IDs. If this same IP-block is used on 44 some other non-ACPI platform, the driver might work out of the box or needs 151 The interrupt name can be listed in _DSD as 'interrupt-names'. The names [all …]
|