/openbmc/linux/arch/arm/boot/dts/ti/omap/ |
H A D | am3874-iceboard.dts | 251 /* EEPROM bank and serial number are treated as separate devices */
|
/openbmc/linux/arch/arm64/boot/dts/marvell/ |
H A D | armada-cp11x.dtsi | 25 * The cooling maps are empty as there are no cooling devices.
|
/openbmc/linux/arch/x86/ |
H A D | Kconfig.debug | 219 of all Punit North Complex devices. The power states of
|
/openbmc/openbmc/poky/documentation/dev-manual/ |
H A D | qemu.rst | 169 It does this since standard mouse devices only provide relative input 277 - Generally, headless embedded devices have a serial port. If so,
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | consumer.rst | 426 free_irq(). They will often be stored into IRQ resources for platform devices, 436 the _CRS configuration objects of devices. Those resources do not provide
|
/openbmc/linux/Documentation/devicetree/bindings/arm/ |
H A D | qcom.yaml | 136 There are many devices in the list below that run the standard ChromeOS 138 OS. These devices do not use the scheme described above. For details, see:
|
/openbmc/linux/drivers/iio/light/ |
H A D | Kconfig | 550 Provides support for the TAOS tsl2580, tsl2581 and tsl2583 devices. 569 tmd2672, tsl2772, tmd2772 devices.
|
/openbmc/linux/drivers/gpu/drm/radeon/ |
H A D | radeon_legacy_encoders.c | 1748 radeon_encoder->devices |= supported_device; in radeon_add_legacy_encoder() 1769 radeon_encoder->devices = supported_device; in radeon_add_legacy_encoder()
|
/openbmc/linux/arch/arm64/boot/dts/nvidia/ |
H A D | tegra132.dtsi | 1187 * because there are no cooling devices. 1244 * because there are no cooling devices.
|
/openbmc/qemu/ |
H A D | meson.build | 407 # virtual-devices. 3015 config_devices_mak = target + '-config-devices.mak' 3017 input: ['configs/devices' / target / config_input + '.mak', 'Kconfig'], 3033 config_devices_h += {target: configure_file(output: target + '-config-devices.h', 3047 # build literally all source files, including devices only used by 3586 '-DCONFIG_DEVICES="@0@-config-devices.h"'.format(target)] 3616 config_devices_mak = target + '-config-devices.mak' 3620 … command: [modinfo_generate, '--devices', config_devices_mak, '@INPUT@'], 3766 '-DCONFIG_DEVICES="@0@-config-devices.h"'.format(target)] 4236 summary_info += {'default devices': get_option('default_devices')}
|
/openbmc/linux/drivers/iio/adc/ |
H A D | Kconfig | 126 tristate "Analog Devices AD7476 1-channel ADCs driver and other similar devices from AD and TI" 303 Typically (for such devices) SPI will be used for configuration only, 353 AXP20X and AXP22X ADC devices. 1439 devices.
|
/openbmc/linux/drivers/iommu/arm/arm-smmu-v3/ |
H A D | arm-smmu-v3.c | 993 list_for_each_entry(master, &smmu_domain->devices, domain_head) { in arm_smmu_sync_cd() 1843 list_for_each_entry(master, &smmu_domain->devices, domain_head) { in arm_smmu_atc_inv_domain() 2056 INIT_LIST_HEAD(&smmu_domain->devices); in arm_smmu_domain_alloc() 2472 list_add(&master->domain_head, &smmu_domain->devices); in arm_smmu_attach_dev()
|
/openbmc/linux/Documentation/driver-api/ |
H A D | mtdnand.rst | 15 board drivers or filesystem drivers suitable for NAND devices. 453 (device). This applies to various DiskOnChip devices. 940 /* bbt is stored per chip on multichip devices */
|
/openbmc/linux/fs/btrfs/ |
H A D | check-integrity.c | 576 struct list_head *dev_head = &fs_devices->devices; in btrfsic_process_superblock() 2737 struct list_head *dev_head = &fs_devices->devices; in btrfsic_mount() 2808 struct list_head *dev_head = &fs_devices->devices; in btrfsic_unmount()
|
/openbmc/linux/Documentation/ |
H A D | memory-barriers.txt | 82 - Accessing devices. 205 Some devices present their control interfaces as collections of memory 367 Such enforcement is important because the CPUs and other devices in a system 372 interaction of multiple CPUs and/or devices. 2352 (*) Accessing devices. 2472 Many devices can be memory mapped, and so appear to the CPU as if they're just 2742 the properties of the memory window through which devices are accessed and/or 2749 Not all systems maintain cache coherency with respect to devices doing DMA. In 2822 thus cutting down on transaction setup costs (memory and PCI devices may
|
/openbmc/linux/arch/mips/boot/dts/cavium-octeon/ |
H A D | octeon_68xx.dts | 8 * devices and properties.
|
/openbmc/linux/Documentation/power/ |
H A D | pm_qos_interface.rst | 218 latency tolerance requirements for devices.
|
H A D | suspend-and-cpuhotplug.rst | 121 /sys/devices/system/cpu/cpu*/online
|
/openbmc/linux/tools/testing/selftests/tc-testing/ |
H A D | README | 234 while also setting up dummy devices to be used in testing.
|
/openbmc/linux/Documentation/devicetree/bindings/cpu/ |
H A D | cpu-topology.txt | 32 The cpu nodes, as per bindings defined in [4], represent the devices that
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | rk3399-puma.dtsi | 552 /* Pins that are not explicitely used by any devices */
|
H A D | kirkwood-synology.dtsi | 3 * Nodes for Marvell 628x Synology devices
|
/openbmc/u-boot/board/freescale/t208xqds/ |
H A D | README | 54 - Single memory controller capable of supporting DDR3 and DDR3-LV devices
|
/openbmc/linux/Documentation/admin-guide/nfs/ |
H A D | nfs-rdma.rst | 118 InfiniBand support is required for all RDMA devices (IB, iWARP, etc.)].
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | colorspaces.rst | 74 Different display devices will have different primaries and some
|