Searched full:discoverable (Results 1 – 25 of 32) sorted by relevance
12
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-firmware-qemu_fw_cfg | 21 intended to display discoverable blobs (i.e., those registered
34 **Discoverable fw_cfg blobs by selector key**
36 All discoverable blobs listed in the fw_cfg file directory are
|
| /linux-5.10/arch/x86/kernel/ |
| D | i8253.c | 25 * specific and not discoverable. Avoid the whack a mole game.
27 * These platforms have discoverable TSC/CPU frequencies but this also
|
| /linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | gpmi-nand.yaml | 82 The required ECC strength is automatically discoverable for some
84 if this strength is not discoverable or this property is not enabled,
|
| /linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | khadas,mcu.yaml | 20 - khadas,mcu # MCU revision is discoverable
|
| /linux-5.10/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm963xx-imagetag.txt | 4 Some Broadcom BCM63XX SoC based devices contain additional, non discoverable
|
| /linux-5.10/drivers/mtd/devices/ |
| D | serial_flash_cmds.h | 15 /* JEDEC Standard - Serial Flash Discoverable Parmeters (SFDP) Commands */
|
| /linux-5.10/Documentation/hwmon/ |
| D | vexpress.rst | 39 As these devices are non-discoverable, they must be described in a Device
|
| /linux-5.10/Documentation/virt/kvm/ |
| D | review-checklist.rst | 14 - the API must be discoverable using KVM_CHECK_EXTENSION
|
| /linux-5.10/Documentation/devicetree/bindings/gpu/ |
| D | arm,mali-bifrost.yaml | 22 - const: arm,mali-bifrost # Mali Bifrost GPU model/revision is fully discoverable
|
| /linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 41 discoverable by probing, it might be necessary to describe properties that
|
| /linux-5.10/Documentation/driver-api/ |
| D | isa.rst | 16 The attached does this. For this old non (generically) discoverable ISA
|
| /linux-5.10/arch/mips/loongson64/ |
| D | cpucfg-emul.c | 138 /* Add CPUCFG features non-discoverable otherwise. */ in loongson3_cpucfg_synthesize_data()
|
| /linux-5.10/net/bluetooth/ |
| D | hci_request.c | 1379 * both discoverable and bondable. in adv_use_rpa()
1385 /* We're neither bondable nor discoverable in the limited in adv_use_rpa()
1665 * and limited discoverable flags. in create_instance_adv_data()
2593 /* Limited discoverable mode */ in write_iac()
2602 /* General discoverable mode */ in write_iac()
2625 /* Advertising instances don't use the global discoverable setting, so in discoverable_update()
2631 /* Discoverable mode affects the local advertising in discoverable_update()
3166 /* When discoverable timeout triggers, then just make sure in discov_off()
3167 * the limited discoverable flag is cleared. Even in the case in discov_off()
3168 * of a timeout triggered from general discoverable, it is in discov_off()
|
| /linux-5.10/Documentation/devicetree/bindings/i3c/ |
| D | i3c.txt | 72 are thus discoverable. So, by default, I3C devices do not have to be described
|
| /linux-5.10/drivers/mtd/spi-nor/ |
| D | sfdp.c | 159 * spi_nor_read_sfdp() - read Serial Flash Discoverable Parameters.
195 * spi_nor_read_sfdp_dma_unsafe() - read Serial Flash Discoverable Parameters.
1087 * spi_nor_parse_sfdp() - parse the Serial Flash Discoverable Parameters.
1092 * The Serial Flash Discoverable Parameters are described by the JEDEC JESD216
|
| D | core.h | 189 * Serial Flash Discoverable Parameters (SFDP) tables.
|
| /linux-5.10/arch/x86/include/uapi/asm/ |
| D | bootparam.h | 246 * are not easily enumerated or discoverable. You should not ever use
|
| /linux-5.10/Documentation/driver-api/i3c/ |
| D | protocol.rst | 63 regard I3C is closer to a discoverable bus like USB than it is to I2C or SPI.
|
| /linux-5.10/Documentation/PCI/ |
| D | acpi-info.rst | 39 If the OS is expected to manage a non-discoverable device described via
|
| /linux-5.10/Documentation/security/ |
| D | self-protection.rst | 210 and such values may become discoverable through an information exposure
|
| /linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-subdev.rst | 21 In addition to make sub-devices discoverable, drivers can also choose to
|
| /linux-5.10/Documentation/s390/ |
| D | vfio-ccw.rst | 48 (virtio-ccw)" transport. This makes virtio devices discoverable via
|
| /linux-5.10/include/net/bluetooth/ |
| D | hci.h | 593 #define LE_AD_LIMITED 0x01 /* Limited Discoverable */
594 #define LE_AD_GENERAL 0x02 /* General Discoverable */
|
| /linux-5.10/drivers/net/wireless/intel/iwlwifi/fw/api/ |
| D | mac.h | 265 * device is discoverable and there is an active GO. Note that setting this
|
| /linux-5.10/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | mac-ctxt.c | 800 * discoverable and there is at least another active P2P GO. Settings in iwl_mvm_mac_ctxt_cmd_p2p_device()
801 * this flag will allow the P2P Device to be discoverable on other in iwl_mvm_mac_ctxt_cmd_p2p_device()
|
12