Home
last modified time | relevance | path

Searched +full:wifi +full:- +full:firmware (Results 1 – 16 of 16) sorted by relevance

/Documentation/devicetree/bindings/net/wireless/
Dqcom,ath10k.yaml1 # 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>
11 - Jeff Johnson <jjohnson@kernel.org>
19 - qcom,ath10k # SDIO-based devices
20 - qcom,ipq4019-wifi
21 - qcom,wcn3990-wifi # SNoC-based devices
26 reg-names:
28 - const: membase
[all …]
Dqcom,ath11k.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (c) 2018-2019 The Linux Foundation. All rights reserved.
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Kalle Valo <kvalo@kernel.org>
12 - Jeff Johnson <jjohnson@kernel.org>
21 - qcom,ipq8074-wifi
22 - qcom,ipq6018-wifi
23 - qcom,wcn6750-wifi
24 - qcom,ipq5018-wifi
[all …]
Dbrcm,bcm4329-fmac.yaml1 # 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 …]
Desp,esp8089.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hans de Goede <hdegoede@redhat.com>
19 esp,crystal-26M-en:
22 Value for the crystal_26M_en firmware parameter
25 - compatible
26 - reg
31 - |
33 #address-cells = <1>;
[all …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,wcnss.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andy Gross <agross@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
14 The Qualcomm WCNSS hardware consists of control block and a BT, WiFi and FM
21 firmware-name:
25 Relative firmware image path for the WLAN NV blob.
32 - qcom,riva"
33 - qcom,pronto"
[all …]
/Documentation/hwmon/
Dasus_ec_sensors.rst1 .. 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 X670E-CREATOR WIFI
12 * ProArt B550-CREATOR
14 * ROG CROSSHAIR VIII HERO (WI-FI)
21 * ROG MAXIMUS XI HERO (WI-FI)
22 * ROG STRIX B550-E GAMING
[all …]
/Documentation/driver-api/firmware/
Dbuilt-in-fw.rst2 Built-in firmware
5 Firmware can be built-in to the kernel, this means building the firmware
6 into vmlinux directly, to enable avoiding having to look for firmware from
7 the filesystem. Instead, firmware can be looked for inside the kernel
8 directly. You can enable built-in firmware using the kernel configuration
14 There are a few reasons why you might want to consider building your firmware
18 * Firmware is needed for accessing the boot device, and the user doesn't
19 want to stuff the firmware into the boot initramfs.
22 able to make use of built-in firmware:
24 * Legalese - firmware is non-GPL compatible
[all …]
Dfallback-mechanisms.rst6 filesystem lookup on the root filesystem or when the firmware simply cannot be
8 configuration options related to supporting the firmware fallback mechanism are:
10 * CONFIG_FW_LOADER_USER_HELPER: enables building the firmware fallback
15 enable the kobject uevent fallback mechanism on all firmware API calls
21 manually load the firmware. Read below for more details.
31 Justifying the firmware fallback mechanism
40 * Races upon resume from suspend. This is resolved by the firmware cache, but
41 the firmware cache is only supported if you use uevents, and its not
44 * Firmware is not accessible through typical means:
47 * The firmware provides very unique device specific data tailored for
[all …]
/Documentation/devicetree/bindings/net/bluetooth/
Drealtek,bluetooth.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vasily Khoruzhick <anarsoul@gmail.com>
11 - Alistair Francis <alistair@alistair23.me>
14 RTL8723BS/RTL8723CS/RTL8821CS/RTL8822CS is a WiFi + BT chip. WiFi part
16 H5 protocol with few extra commands to upload firmware and change
22 - enum:
23 - realtek,rtl8723bs-bt
24 - realtek,rtl8723cs-bt
[all …]
Dnxp,88w8987-bt.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/bluetooth/nxp,88w8987-bt.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 This binding describes UART-attached NXP bluetooth chips. These chips
11 are dual-radio chips supporting WiFi and Bluetooth. The bluetooth
12 works on standard H4 protocol over 4-wire UART. The RTS and CTS lines
14 asserts break signal over UART-TX line to put the chip into power save
15 state. De-asserting break wakes up the BT chip.
18 - Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
[all …]
/Documentation/devicetree/bindings/mtd/partitions/
Dtplink,safeloader-partitions.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/tplink,safeloader-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TP-Link SafeLoader partitions
10 TP-Link home routers store various data on flash (e.g. bootloader,
11 flash layout, firmware, product info, configuration, calibration
14 Flash space layout of TP-Link devices is stored on flash itself using
15 a custom ASCII-based format. That format was first found in TP-Link
17 CFE and U-Boot bootloaders.
[all …]
/Documentation/devicetree/bindings/remoteproc/
Dqcom,wcnss-pil.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/qcom,wcnss-pil.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bjorn Andersson <andersson@kernel.org>
14 firmware on the Qualcomm WCNSS core.
21 - items:
22 - enum:
23 - qcom,pronto-v1-pil
24 - qcom,pronto-v2-pil
[all …]
/Documentation/driver-api/thermal/
Dintel_dptf.rst1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
22 Some parts of the technology is implemented in the firmware and uses
31 ----------------------------
38 which should be notified to the firmware when the
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
[all …]
/Documentation/admin-guide/
Dreporting-regressions.rst1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
13 for kernel developers are left to Documentation/process/handling-regressions.rst.
24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
34 #regzbot introduced: v5.13..v5.14-rc1
42 --------------------
54 It thus is a regression when a WiFi driver from Linux 5.13 works fine, but with
69 provides to the userland. It thus does not apply to kernel-internal interfaces
77 Documentation/admin-guide/reporting-issues.rst, it already describes the
83 `regzbot's web-interface <https://linux-regtracking.leemhuis.info/regzbot/>`_.
105 culprit's commit message mentions in lines starting with "Signed-off-by:".
[all …]
Dkernel-parameters.txt16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
50 64 bit X_* addresses. Some firmware have broken 64
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-iio3 Contact: linux-iio@vger.kernel.org
11 Contact: linux-iio@vger.kernel.org
25 Contact: linux-iio@vger.kernel.org
31 Contact: linux-iio@vger.kernel.org
38 Contact: linux-iio@vger.kernel.org
44 The contents of the label are free-form, but there are some
51 * "proximity-wifi"
52 * "proximity-lte"
53 * "proximity-wifi-lte"
54 * "proximity-wifi-left"
[all …]