| /openbmc/linux/drivers/gpu/drm/msm/ |
| H A D | Kconfig | 35 DRM/KMS driver for MSM/snapdragon.
52 Only use this if you are a driver developer. This should *not*
61 bool "Enable MDP4 support in MSM DRM driver"
66 the MSM DRM driver. It is the older display controller found in
70 bool "Enable MDP5 support in MSM DRM driver"
76 the MSM DRM driver. It is the display controller found in devices
80 bool "Enable DPU support in MSM DRM driver"
86 the MSM DRM driver. It is the display controller found in devices
90 bool "Enable DisplayPort support in MSM DRM driver"
95 Compile in support for DP driver in MSM DRM driver. DP external
[all …]
|
| /openbmc/linux/drivers/vdpa/ |
| H A D | Kconfig | 47 tristate "Intel IFC VF vDPA driver"
52 To compile this driver as a module, choose M here: the module will
64 tristate "vDPA driver for ConnectX devices"
69 VDPA network driver for ConnectX6 and newer. Provides offloading
87 tristate "Virtio PCI bridge vDPA driver"
94 tristate "vDPA driver for Alibaba ENI"
98 VDPA driver for Alibaba ENI (Elastic Network Interface) which is built upon
102 tristate "SolidRun's vDPA driver for SolidNET"
105 # This driver MAY create a HWMON device.
107 # If HWMON=n the driver can be compiled either as a module or built-in.
[all …]
|
| /openbmc/u-boot/drivers/core/ |
| H A D | device-remove.c | 20 int device_chld_unbind(struct udevice *dev, struct driver *drv) in device_chld_unbind()
28 if (drv && (pos->driver != drv)) in device_chld_unbind()
39 int device_chld_remove(struct udevice *dev, struct driver *drv, in device_chld_remove()
48 if (drv && (pos->driver != drv)) in device_chld_remove()
61 const struct driver *drv; in device_unbind()
73 drv = dev->driver; in device_unbind()
122 if (dev->driver->priv_auto_alloc_size) { in device_free()
132 size = dev->parent->driver->per_child_auto_alloc_size; in device_free()
157 const struct driver *drv; in device_remove()
166 drv = dev->driver; in device_remove()
[all …]
|
| /openbmc/u-boot/drivers/clk/renesas/ |
| H A D | Kconfig | 8 bool "Renesas RCar Gen2 clock driver"
15 bool "Renesas R8A7790 clock driver"
21 bool "Renesas R8A7791 clock driver"
27 bool "Renesas R8A7792 clock driver"
33 bool "Renesas R8A7793 clock driver"
39 bool "Renesas R8A7794 clock driver"
45 bool "Renesas RCar Gen3 clock driver"
52 bool "Renesas R8A7795 clock driver"
58 bool "Renesas R8A7796 clock driver"
64 bool "Renesas R8A77970 clock driver"
[all …]
|
| /openbmc/linux/drivers/staging/media/atomisp/include/mmu/ |
| H A D | isp_mmu.h | 111 struct isp_mmu_client *driver; member
121 ((mmu)->driver->pte_valid_mask)
132 int isp_mmu_init(struct isp_mmu *mmu, struct isp_mmu_client *driver);
156 if (mmu->driver && mmu->driver->tlb_flush_all) in isp_mmu_flush_tlb_all()
157 mmu->driver->tlb_flush_all(mmu); in isp_mmu_flush_tlb_all()
165 if (mmu->driver && mmu->driver->tlb_flush_range) in isp_mmu_flush_tlb_range()
166 mmu->driver->tlb_flush_range(mmu, start, size); in isp_mmu_flush_tlb_range()
|
| /openbmc/linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.debug | 15 Recommended for driver developers only.
20 bool "Enable additional driver debugging"
45 Choose this option to turn on extra driver debugging that may affect
48 Recommended for driver developers only.
61 Recommended for driver developers only.
70 Enable extra sanity checks (including BUGs) along the GEM driver
73 Recommended for driver developers only.
88 Recommended for driver developers only.
100 Recommended for driver developers only.
114 Recommended for driver developers only.
[all …]
|
| /openbmc/u-boot/drivers/rtc/ |
| H A D | Kconfig | 35 bool "Enable PCF2127 driver"
45 bool "Enable DS1307 driver"
52 bool "Enable ISL1208 driver"
60 This driver supports reading and writing the RTC/calendar and detects
64 bool "Enable RV3029 driver"
70 This driver supports reading and writing the RTC/calendar and the
74 bool "Enable RX8010SJ driver"
80 bool "Enable ARM AMBA PL031 RTC driver"
87 bool "Enable Marvell RTC driver"
90 Enable Marvell RTC driver. This driver supports the rtc that is present
[all …]
|
| /openbmc/openbmc/meta-ufispace/meta-ncplite/recipes-kernel/linux/linux-aspeed/ |
| H A D | ncplite.cfg | 4 #EEPROM driver
7 #Sensors driver
11 #Watchdog driver
14 #NCSI driver
17 #I2C driver
33 #AST2600 TACH & PWM driver config
40 #AST2600 UDC driver
|
| /openbmc/linux/drivers/vfio/mdev/ |
| H A D | mdev_driver.c | 18 container_of(dev->driver, struct mdev_driver, driver); in mdev_probe()
28 container_of(dev->driver, struct mdev_driver, driver); in mdev_remove()
62 drv->driver.bus = &mdev_bus_type; in mdev_register_driver()
63 return driver_register(&drv->driver); in mdev_register_driver()
73 driver_unregister(&drv->driver); in mdev_unregister_driver()
|
| /openbmc/linux/drivers/pinctrl/actions/ |
| H A D | Kconfig | 3 bool "Actions Semi OWL pinctrl driver"
11 Say Y here to enable Actions Semi OWL pinctrl driver
14 bool "Actions Semi S500 pinctrl driver"
18 Say Y here to enable Actions Semi S500 pinctrl driver
21 bool "Actions Semi S700 pinctrl driver"
25 Say Y here to enable Actions Semi S700 pinctrl driver
28 bool "Actions Semi S900 pinctrl driver"
32 Say Y here to enable Actions Semi S900 pinctrl driver
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | hpsa.rst | 4 HPSA - Hewlett Packard Smart Array driver
7 This file describes the hpsa SCSI driver for HP Smart Array controllers.
8 The hpsa driver is intended to supplant the cciss driver for newer
9 Smart Array controllers. The hpsa driver is a SCSI driver, while the
10 cciss driver is a "block" driver. Actually cciss is both a block
11 driver (for logical drives) AND a SCSI driver (for tape drives). This
12 "split-brained" design of the cciss driver is a source of excess
28 Additionally, older Smart Arrays may work with the hpsa driver if the kernel
30 nor supported by HP with this driver. For older Smart Arrays, the cciss
31 driver should still be used.
[all …]
|
| /openbmc/linux/drivers/input/serio/ |
| H A D | Kconfig | 17 To compile this driver as a module, choose M here: the
40 To compile this driver as a module, choose M here: the
55 To compile this driver as a module, choose M here: the
68 To compile this driver as a module, choose M here: the
86 To compile this driver as a module, choose M here: the
97 To compile this driver as a module, choose M here: the
113 This driver provides support for the PS/2 ports on PA-RISC machines
117 It's safe to enable this driver, so if unsure, say Y.
119 To compile this driver as a module, choose M here: the
139 driver, and the new HIL driver is experimental, so if you plan
[all …]
|
| /openbmc/linux/fs/proc/ |
| H A D | proc_tty.c | 131 void proc_tty_register_driver(struct tty_driver *driver) in proc_tty_register_driver() argument
135 if (!driver->driver_name || driver->proc_entry || in proc_tty_register_driver()
136 !driver->ops->proc_show) in proc_tty_register_driver()
139 ent = proc_create_single_data(driver->driver_name, 0, proc_tty_driver, in proc_tty_register_driver()
140 driver->ops->proc_show, driver); in proc_tty_register_driver()
141 driver->proc_entry = ent; in proc_tty_register_driver()
147 void proc_tty_unregister_driver(struct tty_driver *driver) in proc_tty_unregister_driver() argument
151 ent = driver->proc_entry; in proc_tty_unregister_driver()
157 driver->proc_entry = NULL; in proc_tty_unregister_driver()
|
| /openbmc/linux/drivers/watchdog/ |
| H A D | Kconfig | 18 reboot the machine) and a driver for hardware watchdog boards, which
36 Say Y here if you want to use the new watchdog timer driver core.
37 This driver provides a framework for all watchdog timer drivers
55 to ping watchdog devices that were enabled before the driver has
160 To compile this driver as a module, choose M here: the
181 watchdog. Alternatively say M to compile the driver as a module,
193 Alternatively say M to compile the driver as a module,
204 This driver can also be built as a module. If so, the module
215 This driver can be built as a module. The module name is da9063_wdt.
225 This driver can be built as a module. The module name is da9062_wdt.
[all …]
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 237.out | 3 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
8 {"execute": "blockdev-add", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vmdk", "nod…
10 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vmdk", "file"…
32 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
37 …ob-id": "job0", "options": {"adapter-type": "ide", "driver": "vmdk", "extents": [], "file": {"driv…
59 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
64 …": "job0", "options": {"adapter-type": "buslogic", "driver": "vmdk", "extents": [], "file": {"driv…
86 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vmdk", "file"…
96 …te", "arguments": {"job-id": "job0", "options": {"adapter-type": "ide", "driver": "vmdk", "file": …
101 …"arguments": {"job-id": "job0", "options": {"adapter-type": "buslogic", "driver": "vmdk", "file": …
[all …]
|
| H A D | 211.out | 3 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
8 {"execute": "blockdev-add", "arguments": {"driver": "file", "filename": "TEST_DIR/PID-t.vdi", "node…
10 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vdi", "file":…
23 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
28 …ckdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vdi", "file": {"driver": "fi…
41 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "file", "filen…
46 …ckdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vdi", "file": {"driver": "fi…
59 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vdi", "file":…
67 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vdi", "file":…
79 {"execute": "blockdev-create", "arguments": {"job-id": "job0", "options": {"driver": "vdi", "file":…
[all …]
|
| /openbmc/linux/Documentation/staging/ |
| H A D | tee.rst | 9 secure co-processor etc. A TEE driver handles the details needed to
25 User space (the client) connects to the driver by opening /dev/tee[0-9]* or
34 - TEE_IOC_VERSION lets user space know which TEE this driver handles and
51 driver. The main job for the driver is to receive requests from the
66 iterates over the client driver UUID table to find a corresponding
68 probed via corresponding probe API registered by the client driver. This
69 process happens whenever a device or a client driver is registered with TEE
79 Then TEE client driver can talk to a matched Trusted Application using APIs
82 TEE client driver example
85 Suppose a TEE client driver needs to communicate with a Trusted Application
[all …]
|
| /openbmc/linux/drivers/net/ethernet/marvell/ |
| H A D | Kconfig | 27 This driver supports the gigabit ethernet MACs in the
40 This driver supports the MDIO interface found in the network
44 This driver is used by the MV643XX_ETH and MVNETA drivers.
51 This driver supports auxiliary block of the network
55 This driver, when enabled, strictly cooperates with mvneta
56 driver and is common for all network ports of the devices,
68 This driver supports the network interface units in the
72 Note that this driver is distinct from the mv643xx_eth
73 driver, which should be used for the older Marvell SoCs
94 This driver supports the network interface units in the
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | dell_rbu.rst | 2 Dell Remote BIOS Update driver (dell_rbu)
8 Document demonstrating the use of the Dell Remote BIOS Update driver
14 This document discusses the functionality of the rbu driver only.
21 This driver works with Dell OpenManage or Dell Update Packages for updating
31 Dell_RBU driver supports BIOS update using the monolithic image and packetized
32 image methods. In case of monolithic the driver allocates a contiguous chunk
34 using the driver breaks the image in to packets of fixed sizes and the driver
35 would place each packet in contiguous physical memory. The driver also
38 If the dell_rbu driver is unloaded all the allocated memory is freed.
40 The rbu driver needs to have an application (as mentioned above) which will
[all …]
|
| /openbmc/linux/drivers/input/touchscreen/ |
| H A D | Kconfig | 3 # Touchscreen driver configuration
24 To compile this driver as a module, choose M here: the
37 If HWMON is selected, and the driver is told the reference voltage
43 To compile this driver as a module, choose M here: the
56 To compile this driver as a module, choose M here: the
67 To compile this driver as a module, choose M here: the
77 To compile this driver as a module, choose M here: the
89 To compile this driver as a module, choose M here: the
99 resistive touchscreen driver.
103 To compile this driver as a module, choose M here: the
[all …]
|
| /openbmc/linux/Documentation/power/ |
| H A D | drivers-testing.rst | 11 resume transitions in a driver, it is necessary to suspend and resume a fully
12 functional system with this driver loaded. Moreover, that should be done
19 resume without the driver being tested. Thus, if possible, you should first
21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
24 2. Testing the driver
28 without the new driver, you are ready to test it:
30 a) Build the driver as a module, load it and try the test modes of hibernation
33 b) Load the driver and attempt to hibernate in the "reboot", "shutdown" and
36 c) Compile the driver directly into the kernel and try the test modes of
39 d) Attempt to hibernate with the driver compiled directly into the kernel
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-vdpa | 6 to a driver after the creation. It initially contains 1, which
8 driver immediately after they are created.
18 devices to a compatible driver.
27 Writing a device name to this file will cause the driver to
35 Writing a device name to this file will cause the driver to
43 This file allows the driver for a device to be specified.
44 When specified, only a driver with a name matching the value
51 device from its current driver or make any attempt to
52 automatically load the specified driver. If no driver with a
54 not bind to any driver. This also allows devices to opt-out of
[all …]
|
| /openbmc/linux/drivers/iio/gyro/ |
| H A D | Kconfig | 10 tristate "Analog Devices ADIS16080/100 Yaw Rate Gyroscope with SPI driver"
17 tristate "Analog Devices ADIS16130 High Precision Angular Rate Sensor driver"
21 Angular Rate Sensor driver.
24 tristate "Analog devices ADIS16136 and similar gyroscopes driver"
33 tristate "Analog Devices ADIS16260 Digital Gyroscope Sensor SPI driver"
41 This driver can also be built as a module. If so, the module
45 tristate "Analog Devices ADXRS290 Dual-Axis MEMS Gyroscope SPI driver"
53 This driver can also be built as a module. If so, the module will be
57 tristate "Analog Devices ADXRS450/3 Digital Output Gyroscope SPI driver"
63 This driver can also be built as a module. If so, the module
[all …]
|
| /openbmc/linux/drivers/pinctrl/meson/ |
| H A D | Kconfig | 17 bool "Meson 8 SoC pinctrl driver"
23 bool "Meson 8b SoC pinctrl driver"
29 tristate "Meson gxbb SoC pinctrl driver"
35 tristate "Meson gxl SoC pinctrl driver"
44 tristate "Meson axg Soc pinctrl driver"
53 tristate "Meson g12a Soc pinctrl driver"
59 tristate "Meson a1 Soc pinctrl driver"
65 tristate "Meson s4 Soc pinctrl driver"
71 tristate "Amlogic C3 SoC pinctrl driver"
|
| /openbmc/linux/Documentation/gpu/dp-mst/ |
| H A D | topology-figure-3.dot | 2 /* Make sure our payloads are always drawn below the driver node */
7 driver -> payload1;
8 driver -> payload2 [penwidth=3];
14 driver -> port1;
15 driver -> port2;
16 driver -> port3:e;
17 driver -> port4 [color=grey];
55 driver [label="DRM driver";style=filled;shape=box;fillcolor=lightblue];
|