| /openbmc/openbmc/meta-security/docs/ |
| H A D | overview.txt | 81 …- selinux-check-devices.sh : This script checks the /dev directory to see if there are any devices…
|
| /openbmc/linux/Documentation/driver-api/media/drivers/ |
| H A D | pvrusb2.rst | 39 interfaces appropriately as devices are hotplugged in the
127 (Policy, instantiation, and arbitration of pvrusb2 devices fall
|
| /openbmc/linux/Documentation/devicetree/bindings/net/wireless/ |
| H A D | qcom,ath11k.yaml | 8 title: Qualcomm Technologies ath11k wireless devices
15 devices, for example like AHB based IPQ8074.
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | simple-card.yaml | 68 List of phandles pointing to auxiliary devices, such
154 Additional devices used by the simple audio card.
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | clk.rst | 16 available on various devices today. This may come in the form of clock
65 Platforms and devices utilizing the common struct clk_core use the struct
|
| H A D | pin-control.rst | 464 abstract and provide pinmux settings to the devices you choose to instantiate
466 subsystems, so devices will request their mux setting, but it's also possible
509 mechanism, similar to how regulators are connected to devices, usually by
818 simultaneous activation by GPIO and other muxed in devices.
949 together, including how GPIOs and devices are muxed, how regulators are
1037 Finally, some devices expect the mapping table to contain certain specific
1166 attempt to issue ``pinctrl_get_select_default()`` on these devices.
1248 registers on a slow/IRQ-based bus, so client devices should not assume they
1423 - ``pinctrl-devices``: prints each pin controller device along with columns to
|
| /openbmc/linux/Documentation/networking/ |
| H A D | napi.rst | 154 Modern devices have multiple NAPI instances (struct napi_struct) per
158 devices end up using NAPI in fairly similar ways.
|
| H A D | ethtool-netlink.rst | 67 all devices providing it (each device in a separate message).
277 the information for all devices supporting the request.
355 - ``NLM_F_DUMP``, no device: get device related string sets for all devices
391 devices supporting the request).
445 devices supporting the request).
512 devices supporting the request).
672 devices supporting the request).
731 ``ETHTOOL_A_WOL_SOPASS`` is only allowed for devices supporting
1056 This feature is mainly of interest for specific USB devices which does not cope
1592 Because RFC does not specify the ranges beyond the standard 1518 MTU devices
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-dqevent.rst | 359 Video Capture devices have to query the new timings using
368 that many Video Capture devices are not able to recover from a temporary
|
| /openbmc/linux/Documentation/virt/kvm/ |
| H A D | locking.rst | 287 devices, we put the blocked vCPU on the list blocked_vcpu_on_cpu
290 assigned devices happens, we will find the vCPU on the list to
|
| /openbmc/linux/drivers/parisc/ |
| H A D | dino.c | 535 list_for_each_entry_safe(dev, tmp, &bus->devices, bus_list) { in dino_card_setup()
644 list_for_each_entry(dev, &bus->devices, bus_list) { in dino_fixup_bus()
|
| /openbmc/linux/drivers/gpio/ |
| H A D | TODO | 55 driver infrastructure for doing simpler MMIO GPIO devices and there was
101 in drivers/gpio/gpio-*. Augment platforms to create platform devices or
|
| /openbmc/linux/drivers/rapidio/ |
| H A D | rio-scan.c | 208 list_for_each_entry(rdev, &net->devices, net_list) { in rio_clear_locks()
895 list_for_each_entry(rdev, &net->devices, net_list) { in rio_update_route_tables()
|
| /openbmc/linux/drivers/regulator/ |
| H A D | Kconfig | 53 There are some classes of devices that are controlled entirely
55 control power supplies for such devices.
133 tristate "Cirrus Madera and Wolfson Arizona class devices LDO1"
141 tristate "Cirrus Madera and Wolfson Arizona class devices MICSUPP"
147 devices.
1028 8660, 8960 and 8064 based devices.
1050 8974 based devices.
1375 peripherals such as DDR, Flash memories and system devices.
1633 of PMIC devices.
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | runtime-testing.rst | 47 should generate a list of tap devices. This is the option
72 192.168.7.0/24, which is the default IP range used for tap devices by
115 certain devices it can also deploy the image to be tested onto the
306 devices where the serial port device disappears when the device reboots,
|
| /openbmc/linux/sound/drivers/ |
| H A D | aloop.c | 163 static struct platform_device *devices[SNDRV_CARDS]; variable
1791 for (i = 0; i < ARRAY_SIZE(devices); ++i) in loopback_unregister_all()
1792 platform_device_unregister(devices[i]); in loopback_unregister_all()
1818 devices[i] = device; in alsa_card_loopback_init()
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | ubifs-authentication.rst | 47 interface to access raw flash devices. One of the more prominent subsystems that
49 for flash devices and is thus somewhat similar to LVM for block devices. In
277 devices).
|
| H A D | cramfs.rst | 73 (Flash device in physical memory map). MTD partitions based on such devices
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | ipu3.rst | 101 # Establish the link for the media devices using media-ctl [#f3]_
104 # Set the format for the media devices
207 The driver supports V4L2 Video Capture Interface as defined at :ref:`devices`.
404 where /dev/video4, /dev/video5, /dev/video6 and /dev/video7 devices point to
|
| /openbmc/linux/Documentation/admin-guide/kdump/ |
| H A D | kdump.rst | 498 * For s390x systems with many attached devices the "cio_ignore" kernel
500 of kernel memory for devices that are not relevant for kdump. The same
501 applies to systems that use SCSI/FCP devices. In that case the
503 setting FCP devices online.
|
| /openbmc/ipmitool/control/ |
| H A D | ipmitool.spec.in | 12 This package contains a utility for interfacing with devices that support
16 This utility can communicate with IPMI-enabled devices through either a
269 - Add support for PICMG devices
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/stmicro/ |
| H A D | stmmac.rst | 306 the PHY devices MCD registers.
325 New GMAC devices provide own way to manage RGMII/SGMII. This information is
336 PHY and GPHY devices.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | sysfs-interface.rst | 33 Each chip gets its own directory in the sysfs /sys/devices tree. To
430 a forced powerdown of some devices.
599 | temp_samples | Note that on some devices it won't be possible to set all of |
|
| H A D | adm1021.rst | 145 method 4 in Documentation/i2c/instantiating-devices.rst. Possible slave
|
| /openbmc/linux/Documentation/userspace-api/ioctl/ |
| H A D | ioctl-number.rst | 43 Some devices use their major number as the identifier; this is OK, as
44 long as it is unique. Some devices are irregular and don't follow any
348 0xB0 all RATIO devices in development:
|