Searched full:drivers (Results 1 – 25 of 1015) sorted by relevance
12345678910>>...41
| /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 | davinci-vpbe-devel.rst | 10 drivers/media/platform/davinci/vpbe_display.c
11 drivers/media/platform/davinci/vpbe_display.h
14 drivers/media/platform/davinci/vpbe.c
15 drivers/media/platform/davinci/vpbe.h
18 drivers/media/platform/davinci/vpbe_venc.c
19 drivers/media/platform/davinci/vpbe_venc.h
20 drivers/media/platform/davinci/vpbe_venc_regs.h
23 drivers/media/platform/davinci/vpbe_osd.c
24 drivers/media/platform/davinci/vpbe_osd.h
25 drivers/media/platform/davinci/vpbe_osd_regs.h
[all …]
|
| D | fimc-devel.rst | 15 drivers/media/platform/exynos4-is/media-dev.[ch]
19 drivers/media/platform/exynos4-is/fimc-capture.c
23 drivers/media/platform/exynos4-is/mipi-csis.[ch]
27 drivers/media/platform/exynos4-is/fimc-core.c
31 drivers/media/platform/exynos4-is/fimc-core.h
32 drivers/media/platform/exynos4-is/fimc-reg.h
33 drivers/media/platform/exynos4-is/regs-fimc.h
|
| /Documentation/driver-api/ |
| D | infrastructure.rst | 1 Device drivers infrastructure
11 Device Drivers Base
14 .. kernel-doc:: drivers/base/init.c
17 .. kernel-doc:: drivers/base/driver.c
20 .. kernel-doc:: drivers/base/core.c
23 .. kernel-doc:: drivers/base/syscore.c
26 .. kernel-doc:: drivers/base/class.c
29 .. kernel-doc:: drivers/base/node.c
32 .. kernel-doc:: drivers/base/transport_class.c
35 .. kernel-doc:: drivers/base/dd.c
[all …]
|
| 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 | 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 | 45 The SCSI lower layer contains drivers for specific hardware devices.
97 drivers/scsi/scsi.c
102 .. kernel-doc:: drivers/scsi/scsi.c
105 drivers/scsi/scsicam.c
112 .. kernel-doc:: drivers/scsi/scsicam.c
115 drivers/scsi/scsi_error.c
120 .. kernel-doc:: drivers/scsi/scsi_error.c
123 drivers/scsi/scsi_devinfo.c
129 .. kernel-doc:: drivers/scsi/scsi_devinfo.c
132 drivers/scsi/scsi_ioctl.c
[all …]
|
| /Documentation/driver-api/pci/ |
| D | pci.rst | 4 .. kernel-doc:: drivers/pci/pci.c
7 .. kernel-doc:: drivers/pci/pci-driver.c
10 .. kernel-doc:: drivers/pci/remove.c
13 .. kernel-doc:: drivers/pci/search.c
16 .. kernel-doc:: drivers/pci/msi.c
19 .. kernel-doc:: drivers/pci/bus.c
22 .. kernel-doc:: drivers/pci/access.c
25 .. kernel-doc:: drivers/pci/irq.c
28 .. kernel-doc:: drivers/pci/probe.c
31 .. kernel-doc:: drivers/pci/slot.c
[all …]
|
| /Documentation/translations/zh_CN/process/ |
| D | magic-number.rst | 62 MKISS_DRIVER_MAGIC 0x04bf mkiss_channel ``drivers/net/mkiss.h``
63 HDLC_MAGIC 0x239e n_hdlc ``drivers/char/n_hdlc.c``
66 DB_MAGIC 0x4442 fc_info ``drivers/net/iph5526_novram.c``
67 DL_MAGIC 0x444d fc_info ``drivers/net/iph5526_novram.c``
69 FF_MAGIC 0x4646 fc_info ``drivers/net/iph5526_novram.c``
71 PTY_MAGIC 0x5001 ``drivers/char/pty.c``
74 SLIP_MAGIC 0x5302 slip ``drivers/net/slip.h``
75 STRIP_MAGIC 0x5303 strip ``drivers/net/strip.c``
76 X25_ASY_MAGIC 0x5303 x25_asy ``drivers/net/x25_asy.h``
77 SIXPACK_MAGIC 0x5304 sixpack ``drivers/net/hamradio/6pack.h``
[all …]
|
| /Documentation/process/ |
| D | magic-number.rst | 73 MKISS_DRIVER_MAGIC 0x04bf mkiss_channel ``drivers/net/mkiss.h``
74 HDLC_MAGIC 0x239e n_hdlc ``drivers/char/n_hdlc.c``
77 DB_MAGIC 0x4442 fc_info ``drivers/net/iph5526_novram.c``
78 DL_MAGIC 0x444d fc_info ``drivers/net/iph5526_novram.c``
80 FF_MAGIC 0x4646 fc_info ``drivers/net/iph5526_novram.c``
82 PTY_MAGIC 0x5001 ``drivers/char/pty.c``
85 SLIP_MAGIC 0x5302 slip ``drivers/net/slip.h``
86 STRIP_MAGIC 0x5303 strip ``drivers/net/strip.c``
87 X25_ASY_MAGIC 0x5303 x25_asy ``drivers/net/x25_asy.h``
88 SIXPACK_MAGIC 0x5304 sixpack ``drivers/net/hamradio/6pack.h``
[all …]
|
| /Documentation/translations/it_IT/process/ |
| D | magic-number.rst | 79 MKISS_DRIVER_MAGIC 0x04bf mkiss_channel ``drivers/net/mkiss.h``
80 HDLC_MAGIC 0x239e n_hdlc ``drivers/char/n_hdlc.c``
83 DB_MAGIC 0x4442 fc_info ``drivers/net/iph5526_novram.c``
84 DL_MAGIC 0x444d fc_info ``drivers/net/iph5526_novram.c``
86 FF_MAGIC 0x4646 fc_info ``drivers/net/iph5526_novram.c``
88 PTY_MAGIC 0x5001 ``drivers/char/pty.c``
91 SLIP_MAGIC 0x5302 slip ``drivers/net/slip.h``
92 STRIP_MAGIC 0x5303 strip ``drivers/net/strip.c``
93 X25_ASY_MAGIC 0x5303 x25_asy ``drivers/net/x25_asy.h``
94 SIXPACK_MAGIC 0x5304 sixpack ``drivers/net/hamradio/6pack.h``
[all …]
|
| /Documentation/gpu/ |
| 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-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_simple_kms_helper.c
92 .. kernel-doc:: drivers/gpu/drm/drm_simple_kms_helper.c
[all …]
|
| D | amdgpu.rst | 13 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
31 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
34 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
40 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
43 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c
49 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
52 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c
58 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
61 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
67 .. kernel-doc:: drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
[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 …]
|
| D | vc4.rst | 5 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_drv.c
18 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_crtc.c
24 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_hvs.c
30 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_plane.c
36 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_hdmi.c
42 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_dsi.c
48 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_dpi.c
54 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_vec.c
65 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_bo.c
71 .. kernel-doc:: drivers/gpu/drm/vc4/vc4_validate.c
[all …]
|
| D | drm-kms.rst | 5 Drivers must initialize the mode setting core by calling
69 drivers. Besides that they make it unecessarily 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
189 .. kernel-doc:: drivers/gpu/drm/drm_mode_object.c
244 simplifying conversion of existing drivers. But auditing drivers for
260 objects with userspace-visible and settable state. For internal state drivers
274 exposed to drivers, instead the right locks should be automatically acquired by
[all …]
|
| /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
32 - extcon-gpio: drivers/extcon/extcon-gpio.c is used when you need to read an
[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/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 …]
|
| D | gadget.rst | 21 just two fixed-function ones. Gadget drivers can be written so
34 side drivers).
43 distinguish drivers running inside such hardware from the more familiar
44 Linux "USB device drivers", which are host side proxies for the real USB
45 devices, a different term is used: the drivers inside the peripherals
46 are "USB gadget drivers". In USB protocol interactions, the device
54 bind and unbind drivers to devices. The APIs differ in detail, since the
62 Structure of Gadget Drivers
79 callbacks that interact with gadget drivers. Since normal USB
81 drivers. The controller driver can support any number of different
[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/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/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 …]
|
| /Documentation/driver-api/driver-model/ |
| D | platform.rst | 2 Platform Devices and Drivers
35 Platform drivers
37 Platform drivers follow the standard driver model convention, where
38 discovery/enumeration is handled outside the drivers, and drivers
57 Platform drivers register themselves the normal way::
68 Kernel modules can be composed of several platform drivers. The platform core
69 provides helpers to register and unregister an array of drivers::
71 int __platform_register_drivers(struct platform_driver * const *drivers,
73 void platform_unregister_drivers(struct platform_driver * const *drivers,
76 If one of the drivers fails to register, all drivers registered up to that
[all …]
|
12345678910>>...41