data_type large_stringclasses 3
values | source large_stringclasses 29
values | code large_stringlengths 98 49.4M | filepath large_stringlengths 5 161 ⌀ | message large_stringclasses 234
values | commit large_stringclasses 234
values | subject large_stringclasses 418
values | critique large_stringlengths 101 1.26M ⌀ | metadata dict |
|---|---|---|---|---|---|---|---|---|
source | linux | .. SPDX-License-Identifier: GPL-2.0+
============================================
The Linux Hardware Timestamping Engine (HTE)
============================================
:Author: Dipen Patel
Introduction
------------
Certain devices have built in hardware timestamping engines which can
monitor sets of system sign... | Documentation/driver-api/hte/hte.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
============================================
The Linux Hardware Timestamping Engine (HTE)
============================================
The HTE Subsystem
=================
.. toctree::
:maxdepth: 1
hte
HTE Tegra Provider
==================
.. toctree::
:maxdepth: 1
... | Documentation/driver-api/hte/index.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0+
HTE Kernel provider driver
==========================
Description
-----------
The Nvidia tegra HTE provider also known as GTE (Generic Timestamping Engine)
driver implements two GTE instances: 1) GPIO GTE and 2) LIC
(Legacy Interrupt Controller) IRQ GTE. Both GTE instances get the... | Documentation/driver-api/hte/tegra-hte.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
=====================
I3C device driver API
=====================
.. kernel-doc:: include/linux/i3c/device.h
.. kernel-doc:: drivers/i3c/device.c | Documentation/driver-api/i3c/device-driver-api.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
=============
I3C subsystem
=============
.. toctree::
protocol
device-driver-api
master-driver-api | Documentation/driver-api/i3c/index.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
================================
I3C master controller driver API
================================
.. kernel-doc:: drivers/i3c/master.c
.. kernel-doc:: include/linux/i3c/master.h | Documentation/driver-api/i3c/master-driver-api.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
============
I3C protocol
============
Disclaimer
==========
This chapter will focus on aspects that matter to software developers. For
everything hardware related (like how things are transmitted on the bus, how
collisions are prevented, ...) please have a look at the I3C specifi... | Documentation/driver-api/i3c/protocol.rst | null | null | null | null | null |
source | linux | =======
Buffers
=======
* struct iio_buffer — general buffer structure
* :c:func:`iio_validate_scan_mask_onehot` — Validates that exactly one channel
is selected
* :c:func:`iio_buffer_get` — Grab a reference to the buffer
* :c:func:`iio_buffer_put` — Release the reference to the buffer
The Industrial I/O core offer... | Documentation/driver-api/iio/buffers.rst | null | null | null | null | null |
source | linux | =============
Core elements
=============
The Industrial I/O core offers both a unified framework for writing drivers for
many different types of embedded sensors and a standard interface to user space
applications manipulating sensors. The implementation can be found under
:file:`drivers/iio/industrialio-*`
Industri... | Documentation/driver-api/iio/core.rst | null | null | null | null | null |
source | linux | ===========
HW consumer
===========
An IIO device can be directly connected to another device in hardware. In this
case the buffers between IIO provider and IIO consumer are handled by hardware.
The Industrial I/O HW consumer offers a way to bond these IIO devices without
software buffer for data. The implementation ca... | Documentation/driver-api/iio/hw-consumer.rst | null | null | null | null | null |
source | linux | .. include:: <isonum.txt>
Industrial I/O
==============
**Copyright** |copy| 2015 Intel Corporation
Contents:
.. toctree::
:maxdepth: 2
intro
core
buffers
triggers
triggered-buffers
hw-consumer | Documentation/driver-api/iio/index.rst | null | null | null | null | null |
source | linux | .. include:: <isonum.txt>
============
Introduction
============
The main purpose of the Industrial I/O subsystem (IIO) is to provide support
for devices that in some sense perform either
analog-to-digital conversion (ADC) or digital-to-analog conversion (DAC)
or both. The aim is to fill the gap between the somewhat ... | Documentation/driver-api/iio/intro.rst | null | null | null | null | null |
source | linux | =================
Triggered Buffers
=================
Now that we know what buffers and triggers are let's see how they work together.
IIO triggered buffer setup
==========================
* :c:func:`iio_triggered_buffer_setup` — Setup triggered buffer and pollfunc
* :c:func:`iio_triggered_buffer_cleanup` — Free res... | Documentation/driver-api/iio/triggered-buffers.rst | null | null | null | null | null |
source | linux | ========
Triggers
========
* struct iio_trigger — industrial I/O trigger device
* :c:func:`devm_iio_trigger_alloc` — Resource-managed iio_trigger_alloc
* :c:func:`devm_iio_trigger_register` — Resource-managed iio_trigger_register
iio_trigger_unregister
* :c:func:`iio_trigger_validate_own_device` — Check if a trigger... | Documentation/driver-api/iio/triggers.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
====
RAID
====
.. toctree::
:maxdepth: 1
md-cluster
raid5-cache
raid5-ppl | Documentation/driver-api/md/index.rst | null | null | null | null | null |
source | linux | ==========
MD Cluster
==========
The cluster MD is a shared-device RAID for a cluster, it supports
two levels: raid1 and raid10 (limited support).
1. On-disk format
=================
Separate write-intent-bitmaps are used for each cluster node.
The bitmaps record all writes that may have been started on that node,
... | Documentation/driver-api/md/md-cluster.rst | null | null | null | null | null |
source | linux | ================
RAID 4/5/6 cache
================
Raid 4/5/6 could include an extra disk for data cache besides normal RAID
disks. The role of RAID disks isn't changed with the cache disk. The cache disk
caches data to the RAID disks. The cache can be in write-through (supported
since 4.4) or write-back mode (support... | Documentation/driver-api/md/raid5-cache.rst | null | null | null | null | null |
source | linux | ==================
Partial Parity Log
==================
Partial Parity Log (PPL) is a feature available for RAID5 arrays. The issue
addressed by PPL is that after a dirty shutdown, parity of a particular stripe
may become inconsistent with data on other member disks. If the array is also
in degraded state, there is n... | Documentation/driver-api/md/raid5-ppl.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
.. _media_writing_camera_sensor_drivers:
Writing camera sensor drivers
=============================
This document covers the in-kernel APIs only. For the best practices on
userspace API implementation in camera sensor drivers, please see
:ref:`media_using_camera_sensor_drivers`.
... | Documentation/driver-api/media/camera-sensor.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
CEC Kernel Support
==================
The CEC framework provides a unified kernel interface for use with HDMI CEC
hardware. It is designed to handle a multiple types of hardware (receivers,
transmitters, USB dongles). The framework also gives the option to decide
what to do in the ... | Documentation/driver-api/media/cec-core.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Digital TV Conditional Access kABI
----------------------------------
.. kernel-doc:: include/media/dvb_ca_en50221.h | Documentation/driver-api/media/dtv-ca.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Digital TV Common functions
---------------------------
DVB devices
~~~~~~~~~~~
Those functions are responsible for handling the DVB device nodes.
.. kernel-doc:: include/media/dvbdev.h
Digital TV Ring buffer
~~~~~~~~~~~~~~~~~~~~~~
Those routines implement ring buffers used to ... | Documentation/driver-api/media/dtv-common.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Digital TV (DVB) devices
------------------------
Digital TV devices are implemented by several different drivers:
- A bridge driver that is responsible to talk with the bus where the other
devices are connected (PCI, USB, SPI), bind to the other drivers and
implement the digi... | Documentation/driver-api/media/dtv-core.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Digital TV Demux kABI
---------------------
Digital TV Demux
~~~~~~~~~~~~~~~~
The Kernel Digital TV Demux kABI defines a driver-internal interface for
registering low-level, hardware specific driver to a hardware independent
demux layer. It is only of interest for Digital TV devic... | Documentation/driver-api/media/dtv-demux.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Digital TV Frontend kABI
------------------------
Digital TV Frontend
~~~~~~~~~~~~~~~~~~~
The Digital TV Frontend kABI defines a driver-internal interface for
registering low-level, hardware specific driver to a hardware independent
frontend layer. It is only of interest for Digit... | Documentation/driver-api/media/dtv-frontend.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Digital TV Network kABI
-----------------------
.. kernel-doc:: include/media/dvb_net.h | Documentation/driver-api/media/dtv-net.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
.. include:: <isonum.txt>
===================================
Media subsystem kernel internal API
===================================
This section contains usage information about media subsystem and
its supported drivers.
Please see:
Documentation/admin-guide/media/index.rst
... | Documentation/driver-api/media/index.rst | null | null | null | null | null |
source | linux | Media Subsystem Profile
=======================
Overview
--------
The media subsystem covers support for a variety of devices: stream
capture, analog and digital TV streams, cameras, remote controllers, HDMI CEC
and media pipeline control.
It covers, mainly, the contents of those directories:
- drivers/media
- ... | Documentation/driver-api/media/maintainer-entry-profile.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Media Controller devices
------------------------
Media Controller
~~~~~~~~~~~~~~~~
The media controller userspace API is documented in
:ref:`the Media Controller uAPI book <media_controller>`. This document focus
on the kernel-side implementation of the media framework.
Abstract... | Documentation/driver-api/media/mc-core.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Remote Controller devices
-------------------------
Remote Controller core
~~~~~~~~~~~~~~~~~~~~~~
The remote controller core implements infrastructure to receive and send
remote controller keyboard keystrokes and mouse events.
Every time a key is pressed on a remote controller, a... | Documentation/driver-api/media/rc-core.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
.. _transmitter-receiver:
Pixel data transmitter and receiver drivers
===========================================
V4L2 supports various devices that transmit and receive pixel data. Examples of
these devices include a camera sensor, a TV tuner and a parallel, a BT.656 or a
CSI-2 r... | Documentation/driver-api/media/tx-rx.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 async kAPI
^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-async.h | Documentation/driver-api/media/v4l2-async.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 CCI kAPI
^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-cci.h | Documentation/driver-api/media/v4l2-cci.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 common functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-common.h
.. kernel-doc:: include/media/v4l2-ioctl.h | Documentation/driver-api/media/v4l2-common.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 Controls
=============
Introduction
------------
The V4L2 control API seems simple enough, but quickly becomes very hard to
implement correctly in drivers. But much of the code needed to handle controls
is actually not driver specific and can be moved to the V4L core framewor... | Documentation/driver-api/media/v4l2-controls.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Video4Linux devices
-------------------
.. toctree::
:maxdepth: 1
v4l2-intro
v4l2-dev
v4l2-device
v4l2-fh
v4l2-subdev
v4l2-event
v4l2-controls
v4l2-videobuf2
v4l2-dv-timings
v4l2-flash-led-class
v4l2-mc
v4l2-mediabus
v4l2-mem... | Documentation/driver-api/media/v4l2-core.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Video device' s internal representation
=======================================
The actual device nodes in the ``/dev`` directory are created using the
:c:type:`video_device` struct (``v4l2-dev.h``). This struct can either be
allocated dynamically or embedded in a larger struct.
T... | Documentation/driver-api/media/v4l2-dev.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 device instance
--------------------
Each device instance is represented by a struct v4l2_device.
Very simple devices can just allocate this struct, but most of the time you
would embed this struct inside a larger struct.
You must register the device instance by calling:
:c... | Documentation/driver-api/media/v4l2-device.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 DV Timings functions
^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-dv-timings.h | Documentation/driver-api/media/v4l2-dv-timings.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 events
-----------
The V4L2 events provide a generic way to pass events to user space.
The driver must use :c:type:`v4l2_fh` to be able to support V4L2 events.
Events are subscribed per-filehandle. An event specification consists of a
``type`` and is optionally associated wit... | Documentation/driver-api/media/v4l2-event.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 File handles
-----------------
struct v4l2_fh provides a way to easily keep file handle specific data that is
used by the V4L2 framework. Its usage is mandatory in all drivers.
struct v4l2_fh is allocated in the driver's ``open()`` file operation handler.
It is typically embe... | Documentation/driver-api/media/v4l2-fh.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 flash functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-flash-led-class.h | Documentation/driver-api/media/v4l2-flash-led-class.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 fwnode kAPI
^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-fwnode.h | Documentation/driver-api/media/v4l2-fwnode.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Introduction
------------
The V4L2 drivers tend to be very complex due to the complexity of the
hardware: most devices have multiple ICs, export multiple device nodes in
/dev, and create also non-V4L2 devices such as DVB, ALSA, FB, I2C and input
(IR) devices.
Especially the fact t... | Documentation/driver-api/media/v4l2-intro.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 generic ISP parameters and statistics support
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Design rationale
================
ISP configuration parameters and statistics are processed and collected by
drivers and exchanged with userspace through data types that usually
r... | Documentation/driver-api/media/v4l2-isp.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 JPEG header related functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-jpeg.h
:internal:
.. kernel-doc:: drivers/media/v4l2-core/v4l2-jpeg.c
:export: | Documentation/driver-api/media/v4l2-jpeg.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 Media Controller functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-mc.h | Documentation/driver-api/media/v4l2-mc.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 Media Bus functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-mediabus.h | Documentation/driver-api/media/v4l2-mediabus.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 Memory to Memory functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-mem2mem.h | Documentation/driver-api/media/v4l2-mem2mem.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 rect helper functions
^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/v4l2-rect.h | Documentation/driver-api/media/v4l2-rect.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
V4L2 sub-devices
----------------
Many drivers need to communicate with sub-devices. These devices can do all
sort of tasks, but most commonly they handle audio and/or video muxing,
encoding or decoding. For webcams common sub-devices are sensors and camera
controllers.
Usually th... | Documentation/driver-api/media/v4l2-subdev.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Tuner functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/tuner.h
.. kernel-doc:: include/media/tuner-types.h | Documentation/driver-api/media/v4l2-tuner.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Hauppauge TV EEPROM functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/tveeprom.h | Documentation/driver-api/media/v4l2-tveeprom.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
.. _vb2_framework:
V4L2 videobuf2 functions and data structures
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.. kernel-doc:: include/media/videobuf2-core.h
.. kernel-doc:: include/media/videobuf2-v4l2.h
.. kernel-doc:: include/media/videobuf2-memops.h | Documentation/driver-api/media/v4l2-videobuf2.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The bttv driver
===============
bttv and sound mini howto
-------------------------
There are a lot of different bt848/849/878/879 based boards available.
Making video work often is not a big deal, because this is handled
completely by the bt8xx chip, which is common on all boards... | Documentation/driver-api/media/drivers/bttv-devel.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Contributors
============
.. note::
This documentation is outdated. There are several other DVB contributors
that aren't listed below.
Thanks go to the following people for patches and contributions:
- Michael Hunold <m.hunold@gmx.de>
- for the initial saa7146 driver an... | Documentation/driver-api/media/drivers/contributors.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The cx2341x driver
==================
Memory at cx2341x chips
-----------------------
This section describes the cx2341x memory map and documents some of the
register space.
.. note:: the memory long words are little-endian ('intel format').
.. warning::
This information was f... | Documentation/driver-api/media/drivers/cx2341x-devel.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The cx88 driver
===============
Author: Gerd Hoffmann
Documentation missing at the cx88 datasheet
-------------------------------------------
MO_OUTPUT_FORMAT (0x310164)
.. code-block:: none
Previous default from DScaler: 0x1c1f0008
Digit 8: 31-28
28: PREVREMOD = 1
Di... | Documentation/driver-api/media/drivers/cx88-devel.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Idea behind the dvb-usb-framework
=================================
.. note::
#) This documentation is outdated. Please check at the DVB wiki
at https://linuxtv.org/wiki for more updated info.
#) **deprecated:** Newer DVB USB drivers should use the dvb-usb-v2 framewor... | Documentation/driver-api/media/drivers/dvb-usb.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
.. include:: <isonum.txt>
The Samsung S5P/EXYNOS4 FIMC driver
===================================
Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd.
Files partitioning
------------------
- media device driver
drivers/media/platform/samsung/exynos4-is/media-dev.[ch]
-... | Documentation/driver-api/media/drivers/fimc-devel.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
****************
Frontend drivers
****************
Frontend attach headers
***********************
.. Keep it on alphabetic order
.. kernel-doc:: drivers/media/dvb-frontends/a8293.h
.. kernel-doc:: drivers/media/dvb-frontends/af9013.h
.. kernel-doc:: drivers/media/dvb-frontends/a... | Documentation/driver-api/media/drivers/frontends.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
.. include:: <isonum.txt>
===================================
Media driver-specific documentation
===================================
Video4Linux (V4L) drivers
=========================
.. toctree::
:maxdepth: 5
bttv-devel
cx2341x-devel
cx88-devel
fimc-devel
pvrusb2
pxa_c... | Documentation/driver-api/media/drivers/index.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
==================
Intel IPU6 Driver
==================
Author: Bingbu Cao <bingbu.cao@intel.com>
Overview
=========
Intel IPU6 is the sixth generation of Intel Image Processing Unit used in some
Intel Chipsets such as Tiger Lake, Jasper Lake, Alder Lake, Raptor Lake and
Meteor L... | Documentation/driver-api/media/drivers/ipu6.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The pvrusb2 driver
==================
Author: Mike Isely <isely@pobox.com>
Background
----------
This driver is intended for the "Hauppauge WinTV PVR USB 2.0", which
is a USB 2.0 hosted TV Tuner. This driver is a work in progress.
Its history started with the reverse-engineering... | Documentation/driver-api/media/drivers/pvrusb2.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
PXA-Camera Host Driver
======================
Author: Robert Jarzmik <robert.jarzmik@free.fr>
Constraints
-----------
a) Image size for YUV422P format
All YUV422P images are enforced to have width x height % 16 = 0.
This is due to DMA constraints, which transfers only plane... | Documentation/driver-api/media/drivers/pxa_camera.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The Radiotrack radio driver
===========================
Author: Stephen M. Benoit <benoits@servicepro.com>
Date: Dec 14, 1996
ACKNOWLEDGMENTS
----------------
This document was made based on 'C' code for Linux from Gideon le Grange
(legrang@active.co.za or legrang@cs.sun.ac.za)... | Documentation/driver-api/media/drivers/radiotrack.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The Rockchip Image Signal Processor Driver (rkisp1)
===================================================
Versions and their differences
------------------------------
The rkisp1 block underwent some changes between SoC implementations.
The vendor designates them as:
- V10: used at... | Documentation/driver-api/media/drivers/rkisp1.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The saa7134 driver
==================
Author Gerd Hoffmann
Card Variations:
----------------
Cards can use either of these two crystals (xtal):
- 32.11 MHz -> .audio_clock=0x187de7
- 24.576MHz -> .audio_clock=0x200000 (xtal * .audio_clock = 51539600)
Some details about 30/34/3... | Documentation/driver-api/media/drivers/saa7134-devel.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Cropping and Scaling algorithm, used in the sh_mobile_ceu_camera driver
=======================================================================
Author: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Terminology
-----------
sensor scales: horizontal and vertical scales, configured ... | Documentation/driver-api/media/drivers/sh_mobile_ceu_camera.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Tuner drivers
=============
Simple tuner Programming
------------------------
There are some flavors of Tuner programming APIs.
These differ mainly by the bandswitch byte.
- L= LG_API (VHF_LO=0x01, VHF_HI=0x02, UHF=0x08, radio=0x04)
- P= PHILIPS_API (VHF_LO=0xA0, VHF_HI=0x... | Documentation/driver-api/media/drivers/tuners.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
================================
vidtv: Virtual Digital TV driver
================================
Author: Daniel W. S. Almeida <dwlsalmeida@gmail.com>, June 2020.
Background
----------
Vidtv is a virtual DVB driver that aims to serve as a reference for driver
writers by serving ... | Documentation/driver-api/media/drivers/vidtv.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The Virtual Media Controller Driver (vimc)
==========================================
Source code documentation
-------------------------
vimc-streamer
~~~~~~~~~~~~~
.. kernel-doc:: drivers/media/test-drivers/vimc/vimc-streamer.h
:internal:
.. kernel-doc:: drivers/media/test-... | Documentation/driver-api/media/drivers/vimc-devel.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
The Zoran driver
================
unified zoran driver (zr360x7, zoran, buz, dc10(+), dc30(+), lml33)
website: http://mjpeg.sourceforge.net/driver-zoran/
Frequently Asked Questions
--------------------------
What cards are supported
------------------------
Iomega Buz, Linux M... | Documentation/driver-api/media/drivers/zoran.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause
.. include:: <isonum.txt>
.. _media-ccs-driver:
MIPI CCS camera sensor driver
=============================
The MIPI CCS camera sensor driver is a generic driver for `MIPI CCS
<https://www.mipi.org/specifications/camera-command-set>`_ compliant
camera sensors... | Documentation/driver-api/media/drivers/ccs/ccs.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
HDCP:
=====
ME FW as a security engine provides the capability for setting up
HDCP2.2 protocol negotiation between the Intel graphics device and
an HDC2.2 sink.
ME FW prepares HDCP2.2 negotiation parameters, signs and encrypts them
according the HDCP 2.2 spec. The Intel graphics s... | Documentation/driver-api/mei/hdcp.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Intel(R) Active Management Technology (Intel AMT)
=================================================
Prominent usage of the Intel ME Interface is to communicate with Intel(R)
Active Management Technology (Intel AMT) implemented in firmware running on
the Intel ME.
Intel AMT provide... | Documentation/driver-api/mei/iamt.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
.. include:: <isonum.txt>
===================================================
Intel(R) Management Engine Interface (Intel(R) MEI)
===================================================
**Copyright** |copy| 2019 Intel Corporation
.. toctree::
:caption: Table of Contents
:maxde... | Documentation/driver-api/mei/index.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
==============================================
Intel(R) Management Engine (ME) Client bus API
==============================================
Rationale
=========
The MEI character device is useful for dedicated applications to send and receive
data to the many FW appliance found i... | Documentation/driver-api/mei/mei-client-bus.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
Introduction
============
The Intel Management Engine (Intel ME) is an isolated and protected computing
resource (Co-processor) residing inside certain Intel chipsets. The Intel ME
provides support for computer/IT management and security features.
The actual feature set depends on ... | Documentation/driver-api/mei/mei.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
MEI NFC
-------
Some Intel 8 and 9 Series chipsets support NFC devices connected behind
the Intel Management Engine controller.
MEI client bus exposes the NFC chips as NFC phy devices and enables
binding with Microread and NXP PN544 NFC device driver from the Linux NFC
subsystem.
... | Documentation/driver-api/mei/nfc.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
=========================
Memory Controller drivers
=========================
.. toctree::
:maxdepth: 1
ti-emif
ti-gpmc | Documentation/driver-api/memory-devices/index.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
===============================
TI EMIF SDRAM Controller Driver
===============================
Author
======
Aneesh V <aneesh@ti.com>
Location
========
driver/memory/emif.c
Supported SoCs:
===============
TI OMAP44xx
TI OMAP54xx
Menuconfig option:
==================
Device Driv... | Documentation/driver-api/memory-devices/ti-emif.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
========================================
GPMC (General Purpose Memory Controller)
========================================
GPMC is an unified memory controller dedicated to interfacing external
memory devices like
* Asynchronous SRAM like memories and application specific integra... | Documentation/driver-api/memory-devices/ti-gpmc.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
========================
MMC/SD/SDIO card support
========================
.. toctree::
:maxdepth: 1
mmc-dev-attrs
mmc-dev-parts
mmc-async-req
mmc-test
mmc-tools | Documentation/driver-api/mmc/index.rst | null | null | null | null | null |
source | linux | ========================
MMC Asynchronous Request
========================
Rationale
=========
How significant is the cache maintenance overhead?
It depends. Fast eMMC and multiple cache levels with speculative cache
pre-fetch makes the cache overhead relatively significant. If the DMA
preparations for the next requ... | Documentation/driver-api/mmc/mmc-async-req.rst | null | null | null | null | null |
source | linux | ==================================
SD and MMC Block Device Attributes
==================================
These attributes are defined for the block devices associated with the
SD or MMC device.
The following attributes are read/write.
======== ===============================================
force_ro Enforce read... | Documentation/driver-api/mmc/mmc-dev-attrs.rst | null | null | null | null | null |
source | linux | ============================
SD and MMC Device Partitions
============================
Device partitions are additional logical block devices present on the
SD/MMC device.
As of this writing, MMC boot partitions as supported and exposed as
/dev/mmcblkXboot0 and /dev/mmcblkXboot1, where X is the index of the
parent /d... | Documentation/driver-api/mmc/mmc-dev-parts.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
========================
MMC Test Framework
========================
Overview
========
The `mmc_test` framework is designed to test the performance and reliability of host controller drivers and all devices handled by the MMC subsystem. This includes not only MMC devices but also ... | Documentation/driver-api/mmc/mmc-test.rst | null | null | null | null | null |
source | linux | ======================
MMC tools introduction
======================
There is one MMC test tools called mmc-utils, which is maintained by Ulf Hansson,
you can find it at the below public git repository:
https://git.kernel.org/pub/scm/utils/mmc/mmc-utils.git
Functions
=========
The mmc-utils tools can do the follow... | Documentation/driver-api/mmc/mmc-tools.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
==============================
Memory Technology Device (MTD)
==============================
.. toctree::
:maxdepth: 1
spi-intel
nand_ecc
spi-nor | Documentation/driver-api/mtd/index.rst | null | null | null | null | null |
source | linux | ==========================
NAND Error-correction Code
==========================
Introduction
============
Having looked at the linux mtd/nand Hamming software ECC engine driver
I felt there was room for optimisation. I bashed the code for a few hours
performing tricks like table lookup removing superfluous code etc.... | Documentation/driver-api/mtd/nand_ecc.rst | null | null | null | null | null |
source | linux | ==============================
Upgrading BIOS using spi-intel
==============================
Many Intel CPUs like Baytrail and Braswell include SPI serial flash host
controller which is used to hold BIOS and other platform specific data.
Since contents of the SPI serial flash is crucial for machine to function,
it is ... | Documentation/driver-api/mtd/spi-intel.rst | null | null | null | null | null |
source | linux | =================
SPI NOR framework
=================
How to propose a new flash addition
-----------------------------------
Most SPI NOR flashes comply with the JEDEC JESD216
Serial Flash Discoverable Parameter (SFDP) standard. SFDP describes
the functional and feature capabilities of serial flash devices in a
stan... | Documentation/driver-api/mtd/spi-nor.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
========================
Near Field Communication
========================
.. toctree::
:maxdepth: 1
nfc-hci
nfc-pn544 | Documentation/driver-api/nfc/index.rst | null | null | null | null | null |
source | linux | ========================
HCI backend for NFC Core
========================
- Author: Eric Lapuyade, Samuel Ortiz
- Contact: eric.lapuyade@intel.com, samuel.ortiz@intel.com
General
-------
The HCI layer implements much of the ETSI TS 102 622 V10.2.0 specification. It
enables easy writing of HCI-based NFC drivers. The... | Documentation/driver-api/nfc/nfc-hci.rst | null | null | null | null | null |
source | linux | ============================================================================
Kernel driver for the NXP Semiconductors PN544 Near Field Communication chip
============================================================================
General
-------
The PN544 is an integrated transmission module for contactless
communi... | Documentation/driver-api/nfc/nfc-pn544.rst | null | null | null | null | null |
source | linux | =============================
BTT - Block Translation Table
=============================
1. Introduction
===============
Persistent memory based storage is able to perform IO at byte (or more
accurately, cache line) granularity. However, we often want to expose such
storage as traditional block devices. The block d... | Documentation/driver-api/nvdimm/btt.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
==================================
NVDIMM Runtime Firmware Activation
==================================
Some persistent memory devices run a firmware locally on the device /
"DIMM" to perform tasks like media management, capacity provisioning,
and health monitoring. The process of... | Documentation/driver-api/nvdimm/firmware-activate.rst | null | null | null | null | null |
source | linux | .. SPDX-License-Identifier: GPL-2.0
===================================
Non-Volatile Memory Device (NVDIMM)
===================================
.. toctree::
:maxdepth: 1
nvdimm
btt
security
firmware-activate | Documentation/driver-api/nvdimm/index.rst | null | null | null | null | null |
source | linux | ===============================
LIBNVDIMM: Non-Volatile Devices
===============================
libnvdimm - kernel / libndctl - userspace helper library
nvdimm@lists.linux.dev
Version 13
.. contents:
Glossary
Overview
Supporting Documents
Git Trees
LIBNVDIMM PMEM
PMEM-REGIONs, Atomic Sectors, and... | Documentation/driver-api/nvdimm/nvdimm.rst | null | null | null | null | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.