| /openbmc/linux/drivers/virtio/ |
| H A D | Kconfig | 9 This option is selected by any driver which implements the virtio
51 tristate "PCI driver for virtio devices"
56 This driver provides support for virtio based paravirtual device
71 This option enables building a transitional driver, supporting
73 If disabled, you get a slightly smaller, non-transitional driver,
84 tristate "vDPA driver for virtio devices"
88 This driver provides support for virtio based paravirtual
89 device driver over vDPA bus. For this to be useful, you need
97 tristate "Support for virtio pmem driver"
101 This driver provides access to virtio-pmem devices, storage devices
[all …]
|
| /openbmc/linux/include/drm/ |
| H A D | drm_kunit_helpers.h | 22 const struct drm_driver *driver);
56 struct drm_driver *driver; in __drm_kunit_helper_alloc_drm_device() local
58 driver = devm_kzalloc(dev, sizeof(*driver), GFP_KERNEL); in __drm_kunit_helper_alloc_drm_device()
59 KUNIT_ASSERT_NOT_NULL(test, driver); in __drm_kunit_helper_alloc_drm_device()
61 driver->driver_features = features; in __drm_kunit_helper_alloc_drm_device()
65 driver); in __drm_kunit_helper_alloc_drm_device()
|
| /openbmc/linux/drivers/iio/dummy/ |
| H A D | Kconfig | 5 menu "IIO dummy driver"
13 tristate "An example driver with no hardware requirements"
17 a driver. May also be useful for testing userspace code
26 Add some dummy events to the simple dummy driver.
29 allowing that driver's code to be as close as possible to that
30 a normal driver talking to hardware.
39 Add buffered data capture to the simple dummy driver.
41 Buffer handling elements of industrial I/O reference driver.
|
| /openbmc/linux/include/linux/ |
| H A D | greybus.h | 65 struct device_driver driver; member
67 #define to_greybus_driver(d) container_of(d, struct greybus_driver, driver)
80 int greybus_register_driver(struct greybus_driver *driver,
82 void greybus_deregister_driver(struct greybus_driver *driver);
85 #define greybus_register(driver) \ argument
86 greybus_register_driver(driver, THIS_MODULE, KBUILD_MODNAME)
87 #define greybus_deregister(driver) \ argument
88 greybus_deregister_driver(driver)
|
| /openbmc/linux/drivers/power/supply/ |
| H A D | Kconfig | 42 Say Y here to enable support for the generic battery driver
46 tristate "Injoinic IP5xxx power bank IC driver"
82 tristate "Test power driver"
84 This driver is used for testing. It's safe to say M here.
87 tristate "Marvell 88PM860x battery driver"
93 tristate "ADP5061 battery charger driver"
100 This driver can be built as a module. If so, the module will be
104 tristate "Active-semi ACT8945A charger driver"
111 tristate "Motorola CPCAP PMIC battery driver"
119 tristate "CW2015 Battery driver"
[all …]
|
| /openbmc/linux/Documentation/driver-api/mei/ |
| H A D | mei-client-bus.rst | 16 In order to plug seamlessly into the kernel device driver model we add kernel virtual
17 bus abstraction on top of the MEI driver. This allows implementing Linux kernel drivers
26 A driver implementation for an MEI Client is very similar to any other existing bus
27 based device drivers. The driver registers itself as an MEI CL bus driver through
33 struct device_driver driver;
45 driver to bind itself against a device name.
56 To actually register a driver on the ME Client bus one must call the :c:func:`mei_cl_add_driver`
59 Once the driver is registered and bound to the device, a driver will typically
63 In order for a driver to be notified about pending traffic or event, the driver
80 The driver init and exit routines for this device would look like:
[all …]
|
| /openbmc/linux/drivers/tty/serial/ |
| H A D | tegra-tcu.c | 23 struct uart_driver driver; member
205 tcu->console.data = &tcu->driver; in tegra_tcu_probe()
209 tcu->driver.owner = THIS_MODULE; in tegra_tcu_probe()
210 tcu->driver.driver_name = "tegra-tcu"; in tegra_tcu_probe()
211 tcu->driver.dev_name = "ttyTCU"; in tegra_tcu_probe()
213 tcu->driver.cons = &tcu->console; in tegra_tcu_probe()
215 tcu->driver.nr = 1; in tegra_tcu_probe()
217 err = uart_register_driver(&tcu->driver); in tegra_tcu_probe()
235 err = uart_add_one_port(&tcu->driver, port); in tegra_tcu_probe()
260 uart_remove_one_port(&tcu->driver, &tcu->port); in tegra_tcu_probe()
[all …]
|
| /openbmc/linux/drivers/media/pci/ivtv/ |
| H A D | Kconfig | 23 This is a video4linux driver for Conexant cx23416 or cx23415 based
29 To compile this driver as a module, choose M here: the
37 This driver provides an ALSA interface as another method for user
39 based PCI TV cards supported by the ivtv driver.
43 provided by the main ivtv driver.
45 To compile this driver as a module, choose M here: the
55 This is a framebuffer driver for the Conexant cx23415 MPEG
60 To compile this driver as a module, choose M here: the
67 With PAT enabled, the cx23415 framebuffer driver does not
69 For this reason, the driver will by default disable itself
[all …]
|
| /openbmc/linux/drivers/soundwire/ |
| H A D | bus_type.c | 84 struct sdw_driver *drv = drv_to_sdw_driver(dev->driver); in sdw_drv_probe()
113 name = drv->driver.name; in sdw_drv_probe()
169 struct sdw_driver *drv = drv_to_sdw_driver(dev->driver); in sdw_drv_remove()
192 struct sdw_driver *drv = drv_to_sdw_driver(dev->driver); in sdw_drv_shutdown()
209 drv->driver.bus = &sdw_bus_type; in __sdw_register_driver()
214 name = drv->driver.name; in __sdw_register_driver()
220 drv->driver.owner = owner; in __sdw_register_driver()
221 drv->driver.probe = sdw_drv_probe; in __sdw_register_driver()
222 drv->driver.remove = sdw_drv_remove; in __sdw_register_driver()
223 drv->driver.shutdown = sdw_drv_shutdown; in __sdw_register_driver()
[all …]
|
| /openbmc/linux/drivers/i3c/master/ |
| H A D | Kconfig | 3 tristate "Cadence I3C master driver"
8 Enable this driver if you want to support Cadence I3C master block.
11 tristate "Synospsys DesignWare I3C master driver"
22 This driver can also be built as a module. If so, the module
26 tristate "ASPEED AST2600 I3C master driver"
34 driver adds platform- specific support for AST2600 hardware.
36 This driver can also be built as a module. If so, the module
40 tristate "Silvaco I3C Dual-Role Master driver"
48 tristate "MIPI I3C Host Controller Interface driver (EXPERIMENTAL)"
58 This driver can also be built as a module. If so, the module will be
|
| /openbmc/linux/arch/um/drivers/ |
| H A D | line.c | 259 const struct line_driver *driver = line->driver; in line_setup_irq() local
265 driver->read_irq_name, data); in line_setup_irq()
275 driver->write_irq_name, data); in line_setup_irq()
330 int line_install(struct tty_driver *driver, struct tty_struct *tty, in line_install() argument
335 ret = tty_standard_install(driver, tty); in line_install()
370 struct tty_driver *driver = line->driver->driver; in setup_one_line() local
382 tty_unregister_device(driver, n); in setup_one_line()
394 tty_unregister_device(driver, n); in setup_one_line()
402 driver, n, NULL); in setup_one_line()
547 struct tty_driver *driver; in register_lines() local
[all …]
|
| /openbmc/linux/drivers/platform/x86/intel/pmt/ |
| H A D | Kconfig | 9 The Intel Platform Monitoring Technology (PMT) class driver provides
15 To compile this driver as a module, choose M here: the module
19 tristate "Intel Platform Monitoring Technology (PMT) Telemetry driver"
23 The Intel Platform Monitory Technology (PMT) Telemetry driver provides
27 To compile this driver as a module, choose M here: the module
31 tristate "Intel Platform Monitoring Technology (PMT) Crashlog driver"
35 The Intel Platform Monitoring Technology (PMT) crashlog driver provides
39 To compile this driver as a module, choose M here: the module
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 226.out | 3 === Testing with driver:file ===
6 qemu-io: can't open: 'file' driver requires 'TEST_DIR/t.IMGFMT' to be a regular file
7 qemu-io: can't open: 'file' driver requires '/dev/null' to be a regular file
10 qemu-io: can't open: 'file' driver requires '/dev/null' to be a regular file
12 === Testing with driver:host_device ===
15 qemu-io: can't open: 'host_device' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or …
19 === Testing with driver:host_cdrom ===
22 qemu-io: can't open: 'host_cdrom' driver requires 'TEST_DIR/t.IMGFMT' to be either a character or b…
|
| /openbmc/u-boot/drivers/demo/ |
| H A D | Kconfig | 1 menu "Demo for driver model"
7 This uclass allows you to play around with driver model. It provides
13 bool "Enable simple demo device for driver model"
16 This device allows you to play around with driver model. It prints
18 this device. It can be used to help understand how driver model
22 bool "Enable shape demo device for driver model"
25 This device allows you to play around with driver model. It prints
27 this device. It can be used to help understand how driver model
|
| /openbmc/linux/drivers/ptp/ |
| H A D | Kconfig | 23 This driver adds support for PTP clocks as character
25 also enable at least one clock driver as well.
27 To compile this driver as a module, choose M here: the module
49 This driver adds support for using the Digital timing engine
55 To compile this driver as a module, choose M here: the module
64 This driver adds support for using the Freescale QorIQ 1588
69 To compile this driver as a module, choose M here: the module
84 This driver adds support for using the DP83640 as a PTP
89 In order for this to work, your MAC driver must also
99 This driver adds support for using the ZHAW InES 1588 IP
[all …]
|
| /openbmc/linux/drivers/media/tuners/ |
| H A D | Kconfig | 32 Elonics E4000 silicon tuner driver.
39 Fitipower FC0011 silicon tuner driver.
46 Fitipower FC0012 silicon tuner driver.
53 Fitipower FC0013 silicon tuner driver.
61 FCI FC2580 silicon tuner driver.
69 ITE Tech IT913x silicon tuner driver.
84 A driver for the silicon tuner MAX2165 from Maxim.
98 Mirics MSi001 silicon tuner driver.
105 A driver for the silicon IF tuner MT2060 from Microtune.
112 A driver for the silicon IF tuner MT2063 from Microtune.
[all …]
|
| /openbmc/linux/sound/isa/ |
| H A D | Kconfig | 39 To compile this driver as a module, choose M here: the module
54 To compile this driver as a module, choose M here: the module
58 tristate "Generic AD1848/CS4248 driver"
67 To compile this driver as a module, choose M here: the module
82 To compile this driver as a module, choose M here: the module
95 To compile this driver as a module, choose M here: the module
108 To compile this driver as a module, choose M here: the module
122 To compile this driver as a module, choose M here: the module
134 To compile this driver as a module, choose M here: the module
147 To compile this driver as a module, choose M here: the module
[all …]
|
| /openbmc/linux/drivers/hwmon/pmbus/ |
| H A D | Kconfig | 12 This driver can also be built as a module. If so, the module will
27 This driver can also be built as a module. If so, the module will
36 This driver can also be built as a module. If so, the module will
47 This driver can also be built as a module. If so, the module will
57 This driver can also be built as a module. If so, the module will
66 This driver can also be built as a module. If so, the module will
75 This driver can also be built as a module. If so, the module will
84 This driver can also be built as a module. If so, the module will
94 This driver can also be built as a module. If so, the module
104 This driver can also be built as a module. If so, the module will
[all …]
|
| /openbmc/linux/drivers/net/wwan/ |
| H A D | Kconfig | 11 Say Y here if you want to use the WWAN driver core. This driver
14 To compile this driver as a module, choose M here: the module will be
33 This driver is a developer testing tool that can be used to test WWAN
36 To compile this driver as a module, choose M here: the module will be
40 tristate "MHI WWAN control driver for QCOM-based PCIe modems"
49 To compile this driver as a module, choose M here: the module will be
53 tristate "MHI WWAN MBIM network driver for QCOM-based PCIe modems"
56 MHI WWAN MBIM is a WWAN network driver for QCOM-based PCIe modems.
61 To compile this driver as a module, choose M here: the module will be
65 tristate "Qualcomm BAM-DMUX WWAN network driver"
[all …]
|
| /openbmc/qemu/tests/unit/ |
| H A D | test-qgraph.c | 73 static void check_contains(const char *machine, const char *driver) in check_contains() argument
76 qos_node_contains(machine, driver, NULL); in check_contains()
78 edge = qos_graph_get_edge(machine, driver); in check_contains()
81 g_assert_cmpint(qos_graph_has_edge(machine, driver), ==, TRUE); in check_contains()
97 static void check_consumes(const char *driver, const char *interface) in check_consumes() argument
101 qos_node_consumes(driver, interface, NULL); in check_consumes()
103 edge = qos_graph_get_edge(interface, driver); in check_consumes()
106 g_assert_cmpint(qos_graph_has_edge(interface, driver), ==, TRUE); in check_consumes()
109 static void check_driver(const char *driver) in check_driver() argument
111 qos_node_create_driver(driver, driverfunct); in check_driver()
[all …]
|
| /openbmc/u-boot/drivers/pinctrl/ |
| H A D | Kconfig | 27 It is totally up to the implementation of each low-level driver.
51 a single pin can be used for several functions. An SoC pinctrl driver
53 The driver is typically controlled by the device tree.
95 driver or in the device tree. If this is acceptable and you need
110 bool "QCA/Athores ar933x pin control driver"
114 The driver is controlled by a device tree node which contains
119 bool "AT91 pinctrl driver"
122 This option is to enable the AT91 pinctrl driver for AT91 PIO
131 can also control the multi-driver capability, pull-up and pull-down
135 bool "AT91 PIO4 pinctrl driver"
[all …]
|
| /openbmc/linux/drivers/soc/qcom/ |
| H A D | Kconfig | 14 This driver provides the means of communicating with and controlling
38 This driver populates CPU OPPs tables and makes adjustments to the
42 To compile this driver as a module, choose M here: the module will
49 This driver is used to manage Generic Interface (GENI) firmware based
51 driver is also used to manage the common aspects of multiple Serial
64 tristate "Qualcomm Technologies, Inc. LLCC driver"
69 Last Level Cache Controller(LLCC) driver for platforms such as,
71 Say yes here to enable LLCC slice driver.
82 tristate "Qualcomm On Chip Memory (OCMEM) driver"
97 tristate "Qualcomm PMIC GLINK driver"
[all …]
|
| /openbmc/linux/drivers/cpufreq/ |
| H A D | Kconfig | 11 Note that this driver doesn't automatically change the CPU
80 loading your cpufreq low-level hardware driver.
83 driver. Fallback governor will be the performance governor.
93 loading your cpufreq low-level hardware driver.
96 driver. Fallback governor will be the performance governor.
116 To compile this driver as a module, choose M here: the
127 To compile this driver as a module, choose M here: the
140 To compile this driver as a module, choose M here: the
149 'ondemand' - This driver adds a dynamic cpufreq policy governor.
156 To compile this driver as a module, choose M here: the
[all …]
|
| /openbmc/linux/Documentation/networking/device_drivers/appletalk/ |
| H A D | cops.rst | 4 The COPS LocalTalk Linux driver (cops.c)
9 This driver has two modes and they are: Dayna mode and Tangent mode.
13 such as more IO ports. As this driver is tested it will
16 Right now these cards are known to work with the COPS driver. The
20 TANGENT driver mode:
23 DAYNA driver mode:
30 The COPS driver defaults to using Dayna mode. To change the driver's
31 mode if you built a driver with dual support use board_type=1 or
34 Operation/loading of the driver
38 If you do not specify any options the driver will try and use the IO = 0x240,
[all …]
|
| /openbmc/linux/net/wireless/ |
| H A D | ethtool.c | 12 if (pdev->driver) in cfg80211_get_drvinfo()
13 strscpy(info->driver, pdev->driver->name, in cfg80211_get_drvinfo()
14 sizeof(info->driver)); in cfg80211_get_drvinfo()
16 strscpy(info->driver, "N/A", sizeof(info->driver)); in cfg80211_get_drvinfo()
|