drivers/staging/media/ipu7/TODO
Source file repositories/reference/linux-study-clean/drivers/staging/media/ipu7/TODO
File Facts
- System
- Linux kernel
- Corpus path
drivers/staging/media/ipu7/TODO- Extension
[no extension]- Size
- 1035 bytes
- Lines
- 27
- Domain
- Driver Families
- Bucket
- drivers/staging
- Inferred role
- Driver Families: drivers/staging
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
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
This is a list of things that need to be done to get this driver out of the
staging directory.
- ABI headers cleanup
Cleanup the firmware ABI headers
- Add metadata capture support
The IPU7 hardware should support metadata capture, but it is not
fully verified with IPU7 firmware ABI so far, need to add the metadata
capture support.
- Refine CSI2 PHY code
Refine the ipu7-isys-csi2-phy.c, move the hardware specific variant
into structure, clarify and explain the PHY registers to make it more
readable.
- Work with the common IPU module
Sakari commented much of the driver code is the same than the IPU6 driver.
IPU7 driver is expected to work with the common IPU module in future.
- Register definition cleanup
Add IPU7 prefix for IPU7 specific registers and related macros. Some
ISYS IO sub-blocks register definitions are offset values from specific
sub-block base, but it is not clear and well suited for driver to use,
need to update the register definitions to make it more clear and
readable.
Annotation
- Atlas domain: Driver Families / drivers/staging.
- 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.