| /openbmc/linux/drivers/net/wireless/intersil/hostap/ |
| H A D | Kconfig | 3 tristate "IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)"
17 Host AP mode that allows the card to act as an IEEE 802.11
21 Host AP driver configuration and tools. This site includes
25 This option includes the base Host AP driver code that is shared by
33 bool "Support downloading firmware images with Host AP driver"
36 Configure Host AP driver to include support for firmware image
49 Allow Host AP driver to write firmware images to the non-volatile
58 tristate "Host AP driver for Prism2/2.5/3 in PLX9052 PCI adaptors"
61 Host AP driver's version for Prism2/2.5/3 PC Cards in PLX9052 based
64 "Host AP support for Prism2/2.5/3 IEEE 802.11b" is required for this
[all …]
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | vfio-ap.rst | 1 Adjunct Processor (AP) Device
9 The IBM Adjunct Processor (AP) Cryptographic Facility is comprised
10 of three AP instructions and from 1 to 256 PCIe cryptographic adapter cards.
11 These AP devices provide cryptographic functions to all CPUs assigned to a
14 On s390x, AP adapter cards are exposed via the AP bus. This document
18 AP Architectural Overview
24 * AP adapter
26 An AP adapter is an IBM Z adapter card that can perform cryptographic
31 determined by machine model. When installed, an AP adapter is accessed by
32 AP instructions executed by any CPU.
[all …]
|
| /openbmc/linux/Documentation/arch/s390/ |
| H A D | vfio-ap.rst | 2 Adjunct Processor (AP) facility
8 The Adjunct Processor (AP) facility is an IBM Z cryptographic facility comprised
9 of three AP instructions and from 1 up to 256 PCIe cryptographic adapter cards.
10 The AP devices provide cryptographic functions to all CPUs assigned to a
13 The AP adapter cards are exposed via the AP bus. The motivation for vfio-ap
14 is to make AP cards available to KVM guests using the VFIO mediated device
16 facilities which do most of the hard work of providing direct access to AP
19 AP Architectural Overview
24 * AP adapter
26 An AP adapter is an IBM Z adapter card that can perform cryptographic
[all …]
|
| H A D | vfio-ap-locking.rst | 4 VFIO AP Locks Overview
47 lock must be held by the vfio_ap device driver while one or more AP adapters,
72 device driver is using it to plug/unplug AP devices passed through to the KVM
78 AP devices passed through to a KVM guest.
|
| /openbmc/linux/Documentation/networking/ |
| H A D | mac80211-auth-assoc-deauth.txt | 17 mac80211->driver: sta_state(AP, not-exists)
28 mac80211->driver: sta_state(AP, exists)
43 mac80211->driver: sta_state(AP, authenticated)
56 mac80211->driver: sta_state(AP, exists)
57 mac80211->driver: sta_state(AP, authenticated)
62 mac80211->driver: sta_state(AP, associated)
65 mac80211->driver: sta_state(AP, authorized)
81 mac80211->driver: sta_state(AP, authorized)
88 mac80211->driver: sta_state(AP,associated)
89 mac80211->driver: sta_state(AP,authenticated)
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.i2c | 12 AP (Application Processor, meaning the main CPU) and one driven by the EC
18 Since U-Boot runs on the AP, the terminology used is 'our' claim GPIO,
19 meaning the AP's, and 'their' claim GPIO, meaning the EC's. This terminology
25 GPIO lines are shared between the AP and EC to manage the bus. The AP and EC
28 - AP_CLAIM: output from AP, signalling to the EC that the AP wants the bus
29 - EC_CLAIM: output from EC, signalling to the AP that the EC wants the bus
35 Let's say the AP wants to claim the bus. It:
39 3. Checks EC_CLAIM. If this is not asserted, then the AP has the bus, and we
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | marvell,sei.txt | 10 AP and is wired while a second set comes from the CPs by the mean of
20 coming from the AP, should be 1. The cell is the IRQ
23 for AP interrupts.
|
| /openbmc/linux/Documentation/devicetree/bindings/serio/ |
| H A D | olpc,ap-sp.txt | 1 OLPC AP-SP serio interface
6 - interrupts : SP-AP interrupt
|
| /openbmc/linux/arch/sh/boards/ |
| H A D | Kconfig | 242 bool "AP-325RXA"
247 Renesas "AP-325RXA" support.
248 Compatible with ALGO SYSTEM CO.,LTD. "AP-320A"
363 bool "AP-SH4A-3A"
368 Select AP-SH4A-3A if configuring for an ALPHAPROJECT AP-SH4A-3A.
371 bool "AP-SH4AD-0A"
377 Select AP-SH4AD-0A if configuring for an ALPHAPROJECT AP-SH4AD-0A.
|
| /openbmc/linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3399pro.dtsi | 10 /* Default to enabled since AP talk to NPU part over pcie */
15 /* Default to enabled since AP talk to NPU part over pcie */
|
| H A D | rk3399-gru.dtsi | 27 * the AP. AKA:
30 * - Rails _are_ included if the rails go to the AP even if the AP
35 * If two rails are substantially the same from the AP's point of
38 * look the same to the AP because one of these is true:
40 * long as the AP is running.
57 /* EC turns on w/ lpddr_pwr_en; always on for AP */
96 /* EC turns on w/ pp5000_en; always on for AP */
114 /* EC turns on w/ ap_core_en; always on for AP */
143 /* EC turns on w/ ap_core_en; always on for AP */
172 /* EC turns on w/ ap_core_en; always on for AP */
[all …]
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | rk3399-gru.dtsi | 28 * the AP. AKA:
31 * - Rails _are_ included if the rails go to the AP even if the AP
36 * If two rails are substantially the same from the AP's point of
39 * look the same to the AP because one of these is true:
41 * long as the AP is running.
58 /* EC turns on w/ lpddr_pwr_en; always on for AP */
97 /* EC turns on w/ pp5000_en; always on for AP */
115 /* EC turns on w/ ap_core_en; always on for AP */
144 /* EC turns on w/ ap_core_en; always on for AP */
173 /* EC turns on w/ ap_core_en; always on for AP */
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-platform-soc-ipa | 57 from the perspective of the AP. An endpoint ID is a
66 the ID of the AP endpoint on which packets originating
75 the ID of the AP endpoint on which packets destined
84 the ID of the AP endpoint on which IPA "monitor" data is
|
| /openbmc/linux/arch/arm/boot/dts/broadcom/ |
| H A D | bcm4709-buffalo-wxr-1900dhp.dts | 106 /* Switch: AP mode */
108 label = "AP";
|
| H A D | bcm4708-buffalo-wzr-1750dhp.dts | 122 /* Switch: AP mode */
124 label = "AP";
|
| H A D | bcm4708-buffalo-wzr-1166dhp-common.dtsi | 126 /* Switch: AP mode */
128 label = "AP";
|
| /openbmc/linux/arch/arm/boot/dts/intel/ixp/ |
| H A D | intel-ixp42x-gateway-7001.dts | 3 * Device Tree file for Gateway 7001 AP based on IXP422
13 model = "Gateway 7001 AP";
|
| /openbmc/linux/arch/arm/boot/dts/arm/ |
| H A D | integratorap.dts | 3 * Device Tree for the ARM Integrator/AP platform
12 model = "ARM Integrator/AP";
59 /* 24 MHz chrystal on the Integrator/AP development board */
210 * The Integator/AP predates the idea to have magic numbers
|
| /openbmc/linux/arch/arm/boot/dts/qcom/ |
| H A D | qcom-ipq4019-ap.dk04.1-c3.dts | 7 model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK04.1-C3";
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | ipq8074-hk10-c2.dts | 9 model = "Qualcomm Technologies, Inc. IPQ8074/AP-HK10-C2";
|
| H A D | ipq8074-hk10-c1.dts | 10 model = "Qualcomm Technologies, Inc. IPQ8074/AP-HK10-C1";
|
| /openbmc/u-boot/arch/sh/ |
| H A D | Kconfig | 71 bool "ALPHAPROJECT AP-SH4A-4A"
75 bool "Renesas AP-325RXA"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/hostapd/hostapd/ |
| H A D | hostapd.service | 2 Description=Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
|
| /openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | sprd,pinctrl.txt | 13 have several systems (AP/CP/CM4) on one SoC.).
32 Now we have 4 systems for sleep mode on SC9860 SoC: AP system,
51 PUBCP system) do not run linux kernel OS (only AP system run linux
|
| /openbmc/linux/arch/arm/boot/dts/allwinner/ |
| H A D | sun8i-h2-plus-bananapi-m2-zero.dts | 243 "BT-UART-RTS", "BT-UART-CTS", "WL-WAKE-AP", "BT-WAKE-AP",
244 "BT-RST-N", "AP-WAKE-BT", "", "",
|