Documentation/admin-guide/media/i2c-cardlist.rst
Source file repositories/reference/linux-study-clean/Documentation/admin-guide/media/i2c-cardlist.rst
File Facts
- System
- Linux kernel
- Corpus path
Documentation/admin-guide/media/i2c-cardlist.rst- Extension
.rst- Size
- 11228 bytes
- Lines
- 288
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: documentation
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
.. SPDX-License-Identifier: GPL-2.0
I²C drivers
===========
The I²C (Inter-Integrated Circuit) bus is a three-wires bus used internally
at the media cards for communication between different chips. While the bus
is not visible to the Linux Kernel, drivers need to send and receive
commands via the bus. The Linux Kernel driver abstraction has support to
implement different drivers for each component inside an I²C bus, as if
the bus were visible to the main system board.
One of the problems with I²C devices is that sometimes the same device may
work with different I²C hardware. This is common, for example, on devices
that comes with a tuner for North America market, and another one for
Europe. Some drivers have a ``tuner=`` modprobe parameter to allow using a
different tuner number in order to address such issue.
The current supported of I²C drivers (not including staging drivers) are
listed below.
Audio decoders, processors and mixers
-------------------------------------
============ ==========================================================
Driver Name
============ ==========================================================
cs3308 Cirrus Logic CS3308 audio ADC
cs5345 Cirrus Logic CS5345 audio ADC
cs53l32a Cirrus Logic CS53L32A audio ADC
msp3400 Micronas MSP34xx audio decoders
sony-btf-mpx Sony BTF's internal MPX
tda1997x NXP TDA1997x HDMI receiver
tda7432 Philips TDA7432 audio processor
tda9840 Philips TDA9840 audio processor
tea6415c Philips TEA6415C audio processor
tea6420 Philips TEA6420 audio processor
tlv320aic23b Texas Instruments TLV320AIC23B audio codec
tvaudio Simple audio decoder chips
uda1342 Philips UDA1342 audio codec
vp27smpx Panasonic VP27's internal MPX
wm8739 Wolfson Microelectronics WM8739 stereo audio ADC
wm8775 Wolfson Microelectronics WM8775 audio ADC with input mixer
============ ==========================================================
Audio/Video compression chips
-----------------------------
============ ==========================================================
Driver Name
============ ==========================================================
saa6752hs Philips SAA6752HS MPEG-2 Audio/Video Encoder
============ ==========================================================
Camera sensor devices
---------------------
============ ==========================================================
Driver Name
============ ==========================================================
ccs MIPI CCS compliant camera sensors (also SMIA++ and SMIA)
et8ek8 ET8EK8 camera sensor
hi556 Hynix Hi-556 sensor
hi846 Hynix Hi-846 sensor
imx208 Sony IMX208 sensor
imx214 Sony IMX214 sensor
imx219 Sony IMX219 sensor
imx258 Sony IMX258 sensor
imx274 Sony IMX274 sensor
imx290 Sony IMX290 sensor
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.