Documentation/i2c/busses/i2c-diolan-u2c.rst

Source file repositories/reference/linux-study-clean/Documentation/i2c/busses/i2c-diolan-u2c.rst

File Facts

System: Linux kernel
Corpus path: Documentation/i2c/busses/i2c-diolan-u2c.rst
Extension: .rst
Size: 666 bytes
Lines: 30
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

============================
Kernel driver i2c-diolan-u2c
============================

Supported adapters:
  * Diolan U2C-12 I2C-USB adapter

    Documentation:
	http://www.diolan.com/i2c/u2c12.html

Author: Guenter Roeck <linux@roeck-us.net>

Description
-----------

This is the driver for the Diolan U2C-12 USB-I2C adapter.

The Diolan U2C-12 I2C-USB Adapter provides a low cost solution to connect
a computer to I2C slave devices using a USB interface. It also supports
connectivity to SPI devices.

This driver only supports the I2C interface of U2C-12. The driver does not use
interrupts.


Module parameters
-----------------

* frequency: I2C bus frequency

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.