Searched full:drivers (Results 1 – 25 of 1192) sorted by relevance
12345678910>>...48
| /Documentation/driver-api/media/drivers/ |
| D | frontends.rst | 4 Frontend drivers
12 .. kernel-doc:: drivers/media/dvb-frontends/a8293.h
13 .. kernel-doc:: drivers/media/dvb-frontends/af9013.h
14 .. kernel-doc:: drivers/media/dvb-frontends/ascot2e.h
15 .. kernel-doc:: drivers/media/dvb-frontends/cxd2820r.h
16 .. kernel-doc:: drivers/media/dvb-frontends/drxk.h
17 .. kernel-doc:: drivers/media/dvb-frontends/dvb-pll.h
18 .. kernel-doc:: drivers/media/dvb-frontends/helene.h
19 .. kernel-doc:: drivers/media/dvb-frontends/horus3a.h
20 .. kernel-doc:: drivers/media/dvb-frontends/ix2505v.h
[all …]
|
| D | fimc-devel.rst | 15 drivers/media/platform/samsung/exynos4-is/media-dev.[ch]
19 drivers/media/platform/samsung/exynos4-is/fimc-capture.c
23 drivers/media/platform/samsung/exynos4-is/mipi-csis.[ch]
27 drivers/media/platform/samsung/exynos4-is/fimc-core.c
31 drivers/media/platform/samsung/exynos4-is/fimc-core.h
32 drivers/media/platform/samsung/exynos4-is/fimc-reg.h
33 drivers/media/platform/samsung/exynos4-is/regs-fimc.h
|
| /Documentation/driver-api/pci/ |
| D | pci.rst | 4 .. kernel-doc:: drivers/pci/pci.c
7 .. kernel-doc:: drivers/pci/iomap.c
10 .. kernel-doc:: drivers/pci/devres.c
13 .. kernel-doc:: drivers/pci/pci-driver.c
16 .. kernel-doc:: drivers/pci/remove.c
19 .. kernel-doc:: drivers/pci/search.c
22 .. kernel-doc:: drivers/pci/msi/msi.c
25 .. kernel-doc:: drivers/pci/bus.c
28 .. kernel-doc:: drivers/pci/access.c
31 .. kernel-doc:: drivers/pci/irq.c
[all …]
|
| /Documentation/driver-api/ |
| D | infiniband.rst | 13 .. kernel-doc:: drivers/infiniband/core/iwpm_util.h
16 .. kernel-doc:: drivers/infiniband/core/cq.c
19 .. kernel-doc:: drivers/infiniband/core/cm.c
22 .. kernel-doc:: drivers/infiniband/core/rw.c
25 .. kernel-doc:: drivers/infiniband/core/device.c
28 .. kernel-doc:: drivers/infiniband/core/verbs.c
31 .. kernel-doc:: drivers/infiniband/core/packer.c
34 .. kernel-doc:: drivers/infiniband/core/sa_query.c
37 .. kernel-doc:: drivers/infiniband/core/ud_header.c
40 .. kernel-doc:: drivers/infiniband/core/umem.c
[all …]
|
| D | infrastructure.rst | 1 Device drivers infrastructure
20 Device Drivers Base
23 .. kernel-doc:: drivers/base/init.c
29 .. kernel-doc:: drivers/base/driver.c
32 .. kernel-doc:: drivers/base/core.c
35 .. kernel-doc:: drivers/base/syscore.c
41 .. kernel-doc:: drivers/base/class.c
44 .. kernel-doc:: drivers/base/node.c
47 .. kernel-doc:: drivers/base/transport_class.c
50 .. kernel-doc:: drivers/base/dd.c
[all …]
|
| D | w1.rst | 18 drivers/w1/w1.c
23 .. kernel-doc:: drivers/w1/w1.c
26 drivers/w1/w1_family.c
31 .. kernel-doc:: drivers/w1/w1_family.c
34 drivers/w1/w1_internal.h
39 .. kernel-doc:: drivers/w1/w1_internal.h
42 drivers/w1/w1_int.c
47 .. kernel-doc:: drivers/w1/w1_int.c
50 drivers/w1/w1_netlink.h
55 .. kernel-doc:: drivers/w1/w1_netlink.h
[all …]
|
| D | scsi.rst | 44 The SCSI lower layer contains drivers for specific hardware devices.
96 drivers/scsi/scsi.c
101 .. kernel-doc:: drivers/scsi/scsi.c
104 drivers/scsi/scsicam.c
111 .. kernel-doc:: drivers/scsi/scsicam.c
114 drivers/scsi/scsi_error.c
119 .. kernel-doc:: drivers/scsi/scsi_error.c
122 drivers/scsi/scsi_devinfo.c
128 .. kernel-doc:: drivers/scsi/scsi_devinfo.c
131 drivers/scsi/scsi_ioctl.c
[all …]
|
| /Documentation/gpu/ |
| D | drm-kms-helpers.rst | 13 modesetting code, where there's a shared userspace ABI for all drivers. This is
20 helpers. Old drivers still often use the legacy CRTC helpers. They both share
21 the same set of common helper vtables. For really simple drivers (anything
53 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
59 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
68 .. kernel-doc:: drivers/gpu/drm/drm_atomic_helper.c
74 .. kernel-doc:: drivers/gpu/drm/drm_atomic_state_helper.c
80 .. kernel-doc:: drivers/gpu/drm/drm_atomic_state_helper.c
86 .. kernel-doc:: drivers/gpu/drm/drm_gem_atomic_helper.c
92 .. kernel-doc:: drivers/gpu/drm/drm_gem_atomic_helper.c
[all …]
|
| D | i915.rst | 19 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c
22 .. kernel-doc:: drivers/gpu/drm/i915/intel_runtime_pm.c
25 .. kernel-doc:: drivers/gpu/drm/i915/intel_uncore.c
31 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
34 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
37 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
40 .. kernel-doc:: drivers/gpu/drm/i915/i915_irq.c
46 .. kernel-doc:: drivers/gpu/drm/i915/i915_vgpu.c
49 .. kernel-doc:: drivers/gpu/drm/i915/i915_vgpu.c
55 .. kernel-doc:: drivers/gpu/drm/i915/intel_gvt.c
[all …]
|
| D | drm-mm.rst | 23 identified common code between drivers and created a support library to
31 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_module.c
43 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_device.c
58 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_resource.c
67 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_tt.c
76 .. kernel-doc:: drivers/gpu/drm/ttm/ttm_pool.c
85 operations to userspace and a set of helper functions to drivers, and
86 let drivers implement hardware-specific operations with their own
119 Drivers that use GEM must set the DRIVER_GEM bit in the struct
126 In a KMS configuration, drivers need to allocate and initialize a
[all …]
|
| D | drm-kms.rst | 5 Drivers must initialize the mode setting core by calling
69 drivers. Besides that they make it unnecessarily more complicated for userspace
74 drivers, and in many cases not powerful enough to express the real restrictions.
140 the CRTC and any encoders. Often for drivers with bridges there's no code left
141 at the encoder level. Atomic drivers can leave out all the encoder callbacks to
159 .. kernel-doc:: drivers/gpu/drm/drm_mode_config.c
191 .. kernel-doc:: drivers/gpu/drm/drm_mode_object.c
246 simplifying conversion of existing drivers. But auditing drivers for
262 objects with userspace-visible and settable state. For internal state drivers
276 exposed to drivers, instead the right locks should be automatically acquired by
[all …]
|
| D | vga-switcheroo.rst | 7 .. kernel-doc:: drivers/gpu/vga/vga_switcheroo.c
16 .. kernel-doc:: drivers/gpu/vga/vga_switcheroo.c
22 .. kernel-doc:: drivers/gpu/vga/vga_switcheroo.c
31 .. kernel-doc:: drivers/gpu/vga/vga_switcheroo.c
58 .. kernel-doc:: drivers/gpu/vga/vga_switcheroo.c
61 .. kernel-doc:: drivers/gpu/vga/vga_switcheroo.c
70 .. kernel-doc:: drivers/platform/x86/apple-gmux.c
73 .. kernel-doc:: drivers/platform/x86/apple-gmux.c
79 .. kernel-doc:: drivers/platform/x86/apple-gmux.c
85 .. kernel-doc:: drivers/platform/x86/apple-gmux.c
[all …]
|
| /Documentation/translations/zh_CN/devicetree/ |
| D | kernel-api.rst | 22 drivers/of/base.c
26 drivers/of/property.c
30 drivers/of/address.c
32 drivers/of/irq.c
34 drivers/of/fdt.c
43 drivers/of/device.c
47 drivers/of/platform.c
54 drivers/of/resolver.c
56 drivers/of/dynamic.c
58 drivers/of/overlay.c
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 2 Subsystem drivers using GPIO
5 Note that standard kernel drivers exist for common GPIO tasks and will provide
7 drivers can quite easily interconnect with other kernel subsystems using
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
33 - pwm-gpio: drivers/pwm/pwm-gpio.c is used to toggle a GPIO with a high
[all …]
|
| /Documentation/driver-api/mei/ |
| D | nfc.rst | 18 "drivers/nfc/mei_phy" -> cl_nfc [lhead=bus];
19 "drivers/nfc/microread/mei" -> cl_nfc;
20 "drivers/nfc/microread/mei" -> "drivers/nfc/mei_phy";
21 "drivers/nfc/pn544/mei" -> cl_nfc;
22 "drivers/nfc/pn544/mei" -> "drivers/nfc/mei_phy";
23 "net/nfc" -> "drivers/nfc/microread/mei";
24 "net/nfc" -> "drivers/nfc/pn544/mei";
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal-api.rst | 14 .. kernel-doc:: drivers/platform/surface/aggregator/ssh_parser.h
17 .. kernel-doc:: drivers/platform/surface/aggregator/ssh_parser.c
20 .. kernel-doc:: drivers/platform/surface/aggregator/ssh_msgb.h
23 .. kernel-doc:: drivers/platform/surface/aggregator/ssh_packet_layer.h
26 .. kernel-doc:: drivers/platform/surface/aggregator/ssh_packet_layer.c
33 .. kernel-doc:: drivers/platform/surface/aggregator/ssh_request_layer.h
36 .. kernel-doc:: drivers/platform/surface/aggregator/ssh_request_layer.c
43 .. kernel-doc:: drivers/platform/surface/aggregator/controller.h
46 .. kernel-doc:: drivers/platform/surface/aggregator/controller.c
53 .. kernel-doc:: drivers/platform/surface/aggregator/bus.c
[all …]
|
| /Documentation/driver-api/media/ |
| D | camera-sensor.rst | 5 Writing camera sensor drivers
9 userspace API implementation in camera sensor drivers, please see
60 Camera sensor drivers are responsible for controlling the power state of the
63 time. Drivers should enable runtime PM autosuspend. Also see
67 system resources required to power the sensor up and down. For drivers that
68 don't use any of those resources (such as drivers that support ACPI systems
72 being accessed and when it is streaming. Drivers should use
81 camera sensor and the rest of the camera pipeline. Bridge drivers are
85 sensor drivers shall therefore **not** keep track of the streaming state to
87 Drivers should in general not implement the system PM handlers.
[all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | dcn-blocks.rst | 11 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/dchubbub.h
17 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/hubp.h
23 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/dpp.h
26 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/dpp.h
32 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h
35 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/mpc.h
42 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/opp.h
45 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/inc/hw/opp.h
51 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/link/hwss/link_hwss_dio.c
54 .. kernel-doc:: drivers/gpu/drm/amd/display/dc/link/hwss/link_hwss_dio.c
|
| /Documentation/driver-api/usb/ |
| D | typec_bus.rst | 2 API for USB Type-C Alternate Mode drivers
18 supports. The drivers for the alternate modes are bound to the partner alternate
20 drivers.
28 alternate mode drivers, so the port drivers are only expected to pass the SVID
29 specific commands from the alternate mode drivers to the partner, and from the
30 partners to the alternate mode drivers. No direct SVID specific communication is
31 needed from the port drivers, but the port drivers need to provide the operation
33 drivers need to provide them for the partner alternate mode devices.
41 By default, the alternate mode drivers are responsible for entering the mode.
43 space (See Documentation/ABI/testing/sysfs-class-typec). Port drivers should not
[all …]
|
| /Documentation/admin-guide/media/ |
| D | building.rst | 50 Device Drivers --->
54 [*] HDMI CEC drivers --->
64 The ``HDMI CEC drivers`` option allow selecting platform and USB drivers
84 want to use some TV card drivers that may depend on the remote
87 .. [3] Please notice that the DRM subsystem also have drivers for GPUs
90 Those GPU-specific drivers are selected via the ``Graphics support``
91 menu, under ``Device Drivers``.
122 The remote controller menu allows selecting drivers for specific devices.
148 The ``Remote Controller devices`` allows you to select the drivers
169 that needs it or by one of the existing HDMI drivers.
[all …]
|
| /Documentation/devicetree/ |
| D | kernel-api.rst | 11 .. kernel-doc:: drivers/of/base.c
17 .. kernel-doc:: drivers/of/property.c
23 .. kernel-doc:: drivers/of/address.c
26 .. kernel-doc:: drivers/of/irq.c
29 .. kernel-doc:: drivers/of/fdt.c
38 .. kernel-doc:: drivers/of/device.c
44 .. kernel-doc:: drivers/of/platform.c
50 .. kernel-doc:: drivers/of/resolver.c
53 .. kernel-doc:: drivers/of/dynamic.c
56 .. kernel-doc:: drivers/of/overlay.c
|
| /Documentation/gpu/amdgpu/ |
| D | driver-misc.rst | 14 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_fru_eeprom.c
20 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_fru_eeprom.c
26 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_fru_eeprom.c
32 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_fru_eeprom.c
38 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_fru_eeprom.c
44 .. kernel-doc:: drivers/gpu/drm/amd/pm/amdgpu_pm.c
50 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
78 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c
84 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c
90 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c
[all …]
|
| /Documentation/sound/soc/ |
| D | overview.rst | 11 * Codec drivers were often tightly coupled to the underlying SoC
13 Linux had different wm8731 drivers for 4 different SoC platforms.
21 * Drivers tended to power up the entire codec when playing (or
33 * Codec independence. Allows reuse of codec drivers on other platforms
54 multiple re-usable component drivers :-
56 * Codec class drivers: The codec class driver is platform independent and
59 ICs if required. Codec class drivers should be generic code that can run
62 * Platform class drivers: The platform class driver includes the audio DMA
63 engine driver, digital audio interface (DAI) drivers (e.g. I2S, AC97, PCM)
64 and any audio DSP drivers for that platform.
[all …]
|
| /Documentation/driver-api/tty/ |
| D | tty_struct.rst | 17 .. kernel-doc:: drivers/tty/tty_io.c
23 .. kernel-doc:: drivers/tty/tty_io.c
32 .. kernel-doc:: drivers/tty/tty_io.c
38 .. kernel-doc:: drivers/tty/tty_io.c
44 .. kernel-doc:: drivers/tty/tty_io.c
50 .. kernel-doc:: drivers/tty/tty_io.c
56 .. kernel-doc:: drivers/tty/tty_io.c
62 .. kernel-doc:: drivers/tty/tty_io.c
68 .. kernel-doc:: drivers/tty/tty_io.c
|
| /Documentation/PCI/ |
| D | pciebus-howto.rst | 15 and provides information on how to enable the service drivers to
38 and handled by corresponding service drivers.
48 service drivers will compete for a single PCI-PCI Bridge device.
51 kernel therefore does not load other service drivers for that Root
53 drivers load and run on a PCI-PCI Bridge device simultaneously
56 To enable multiple service drivers running simultaneously requires
59 to the corresponding service drivers as required. Some key
62 - Allow multiple service drivers to run simultaneously on
65 - Allow service drivers implemented in an independent
72 device to requested service drivers.
[all …]
|
12345678910>>...48