| /hardware/interfaces/uwb/aidl/default/src/ |
| D | uwb.rs | 21 .map(|chip| { in from_chips()
23 chip, in from_chips()
38 self.chips.iter().map(|chip| chip.getName()).collect() in getChips()
43 let chip = self in getChip() localVariable
46 .find(|chip| chip.getName().as_deref() == Ok(name)); in getChip()
47 if let Some(chip) = chip { in getChip()
48 Ok(chip.clone()) in getChip()
|
| /hardware/nxp/uwb/aidl/ |
| D | uwb.cpp | 37 for (const auto& chip : chips_) { in getChips() local
38 names->push_back(chip.first); in getChips()
43 ::ndk::ScopedAStatus Uwb::getChip(const std::string& name, std::shared_ptr<IUwbChip>* chip) { in getChip() argument
49 *chip = chip_found->second; in getChip()
|
| D | uwb.h | 39 ::ndk::ScopedAStatus getChip(const std::string& name, std::shared_ptr<IUwbChip>* chip) override;
|
| /hardware/interfaces/wifi/aidl/default/ |
| D | wifi.cpp | 224 for (std::shared_ptr<WifiChip> chip : chips_) { in dump()
225 if (!chip.get()) continue; in dump()
226 chip->dump(fd, args, numArgs); in dump()
311 for (auto& chip : chips_) { in stopInternal() local
312 if (chip.get()) { in stopInternal()
313 chip->invalidate(); in stopInternal()
314 chip.reset(); in stopInternal()
344 for (auto& chip : chips_) { in getChipIdsInternal() local
345 int32_t chip_id = getChipIdFromWifiChip(chip); in getChipIdsInternal()
352 for (auto& chip : chips_) { in getChipInternal() local
[all …]
|
| D | wifi.h | 75 int32_t getChipIdFromWifiChip(std::shared_ptr<WifiChip>& chip);
|
| /hardware/interfaces/wifi/1.0/ |
| D | IWifiChip.hal | 28 * Interface that represents a chip that must be configured as a single unit.
71 * A mode that the chip can be put in. A mode defines a set of constraints on
75 * multiple modes would be required is if a chip has different firmwares with
80 * ChipIfaceCombinations is satisfied. This means that if a chip has two
95 * For example, a chip with available combinations:
97 * If the chip currently has 3 interfaces STA, STA and NAN and wants to add an
103 * If a chip does not support this kind of reconfiguration in this mode then
110 * Id that can be used to put the chip in this mode.
115 * A list of the possible interface combinations that the chip can have
122 * Information about the version of the driver and firmware running this chip.
[all …]
|
| D | IWifiChipEventCallback.hal | 21 * Callback indicating that the chip has been reconfigured successfully. At
26 * @param modeId The mode that the chip switched to, corresponding to the id
32 * Callback indicating that a chip reconfiguration failed. This is a fatal
35 * chip again using |IWifiChip.configureChip|.
42 * Callback indicating that a new iface has been added to the chip.
50 * Callback indicating that an existing iface has been removed from the chip.
84 * Callback indicating that the chip has encountered a fatal error.
|
| D | IWifi.hal | 91 * Retrieve the list of all chip Id's on the device.
92 * The corresponding |IWifiChip| object for any chip can be
100 * @return chipIds List of all chip Id's on the device.
106 * Gets a HIDL interface object for the chip corresponding to the
114 * @return chip HIDL interface object representing the chip.
117 getChip(ChipId chipId) generates (WifiStatus status, IWifiChip chip);
|
| /hardware/nxp/uwb/ |
| D | Android.bp | 17 name: "chip",
28 variables: ["chip"],
39 chip: {
|
| /hardware/interfaces/wifi/1.1/ |
| D | IWifiChip.hal | 23 * Interface that represents a chip that must be configured as a single unit.
29 * Capabilities exposed by this chip.
50 * is defined by the OEM as a BDF file since it varies for each wifi chip
61 * the wifi chip change it's transmitting power levels.
80 * scenario and let the wifi chip fall back to the default power values.
|
| /hardware/interfaces/wifi/1.2/ |
| D | IWifiChip.hal | 24 * Interface that represents a chip that must be configured as a single unit.
30 * Capabilities exposed by this chip.
43 * is defined by the OEM as a BDF file since it varies for each wifi chip
57 * the wifi chip change it's transmitting power levels.
74 * Requests notifications of significant events on this chip. Multiple calls
|
| D | IWifiChipEventCallback.hal | 23 * Wifi chip event callbacks.
|
| /hardware/interfaces/wifi/1.6/ |
| D | IWifiChip.hal | 28 * Interface that represents a chip that must be configured as a single unit.
144 * A mode that the chip can be put in. A mode defines a set of constraints on
148 * multiple modes would be required is if a chip has different firmwares with
153 * ChipConcurrencyCombinations is satisfied. This means that if a chip has two
168 * For example, a chip with available combinations:
170 * If the chip currently has 3 interfaces STA, STA and NAN and wants to add an
176 * If a chip does not support this kind of reconfiguration in this mode then
183 * Id that can be used to put the chip in this mode.
188 * A list of the possible interface concurrency type combinations that the chip can have
195 * Get the set of operation modes that the chip supports.
[all …]
|
| /hardware/broadcom/wlan/bcmdhd/dhdutil/include/ |
| D | bcmdefs.h | 125 #define CHIPID(chip) (BCMCHIPID) argument
127 #define CHIPID(chip) (chip) argument
|
| /hardware/interfaces/wifi/1.5/ |
| D | IWifiChip.hal | 26 * Interface that represents a chip that must be configured as a single unit.
30 * Capabilities exposed by this chip.
34 * chip can operate in the 60GHz band(WiGig chip)
70 * - Should pick the best BSSID for the secondary STA (disregard the chip mode) independent
96 * Get the capabilities supported by this chip.
113 * - If the wifi firmware/chip cannot support multiple instances of any offload
147 * Depending on the mode the chip is configured in, the interface creation
191 the chip on this channel. A value of PowerCapConstant.NO_POWER_CAP means no limitation
192 on transmitted power is needed by the chip for this channel.
233 * Set country code for this Wifi chip.
[all …]
|
| /hardware/interfaces/wifi/1.3/ |
| D | IWifiChip.hal | 23 * Interface that represents a chip that must be configured as a single unit.
28 * Capabilities exposed by this chip.
43 * Get the capabilities supported by this chip.
|
| /hardware/interfaces/wifi/1.4/ |
| D | IWifiChip.hal | 26 * Interface that represents a chip that must be configured as a single unit.
30 * Requests notifications of significant events on this chip. Multiple calls
|
| D | IWifiChipEventCallback.hal | 23 * Wifi chip event callbacks.
|
| /hardware/interfaces/wifi/aidl/vts/functional/ |
| D | wifi_aidl_test_utils.cpp | 119 std::shared_ptr<IWifiChip> chip; in getWifiChip() local
120 status = wifi->getChip(chip_ids[0], &chip); in getWifiChip()
124 return chip; in getWifiChip()
|
| /hardware/google/interfaces/bluetooth/ccc/1.0/ |
| D | IBluetoothCccCallback.hal | 28 * @param lmpEventId LMP event id that bluetooth chip involked
|
| /hardware/google/interfaces/bluetooth/ccc/1.1/ |
| D | IBluetoothCccCallback.hal | 32 * @param lmpEventId LMP event id that bluetooth chip involked
|
| /hardware/interfaces/bluetooth/1.1/ |
| D | IBluetoothHci.hal | 26 * controller chip. This boundary is the natural choice for a Hardware
|
| /hardware/interfaces/radio/config/1.0/ |
| D | types.hal | 43 * standards, following electrical reset of the card's chip. The ATR conveys information about
|
| /hardware/interfaces/nfc/1.1/ |
| D | INfc.hal | 24 * Clears the NFC chip.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_EXT_shader_tile_image.adoc | 10 `VK_EXT_shader_tile_image` is a device extension that explicitly enables access to on-chip pixel da…
14 …lar tile-based GPUs, want to allow applications to effectively exploit local, e.g. on-chip, memory.
15 …ing G-buffer based deferred shading techniques where the G-buffer is produced and consumed on-chip.
19 …mental model an application developer needs to have to be able to optimize for keeping data on-chip
20 …een as a 'tax' on applications that do not target implementations that benefit from on-chip storage
23 …`, which offers an alternative API without subpasses. But keeping data on-chip is still an importa…
44 1. An explicit API to allow certain tile-based GPUs to expose on-chip memory with fast raster order…
47 * This addresses use cases such as keeping G-buffer data on-chip.
56 …* Attachment data is not guaranteed to be on-chip within a render pass and may spill to DRAM. Impl…
|