Renesas R-Car V4H Image Signal Processor
The image signal processor and channel selector block found inside Renesas R-Car V4H automotive system-on-chips, which feed camera data into ADAS (advanced driver-assistance) workloads such as automated lane keeping and parking. It is the on-chip plumbing that routes and processes video from the car's cameras before machine-vision and deep-learning stages consume it.
recommendation
It should stay because the hardware is brand new and still being designed into shipping cars: Renesas continues to sell the V4H chip and its White Hawk evaluation board, and the part was picked up for a Toyota RAV4 ADAS module. Upstream activity in April 2025 was expansion work, moving the code into its own directory and laying groundwork for full ISP-core support, which is the opposite of a sunset.
repository signals
sources
- lore.kernel.org
The driver directory was actively reworked upstream in April/May 2025, including a move into its own directory in preparation for adding more ISP-core functionality.
- lore.kernel.org
A companion 2025 patch explicitly says the driver is being extended beyond the channel selector toward core ISP support, indicating active maintenance rather than retirement.
- lore.kernel.org
Another 2025 patch adds parsing for a named CS memory region while preserving backward compatibility, which is consistent with ongoing enablement work.
- renesas.com
Renesas lists the R-Car V4H product as Active and describes an integrated ISP for machine and human vision, showing the underlying hardware family is current rather than obsolete.
- renesas.com
Renesas still offers the White Hawk R-Car V4H evaluation board, evidence of ongoing new-development availability.
- renesas.com
Renesas announced in February 2026 that R-Car V4H was selected for a Toyota RAV4 ADAS control unit, indicating present-day production deployment.
codex reasoning notes (technical)
This is a real platform driver (`csisp.c`, module/Kconfig/Makefile present), not a helper-only directory. Local `git log`/`git show` established that the directory is new in 2025 and all three substantive touches are part of one upstream enablement series; those `git show` outputs exposed the three cited lore URLs. A `web.search_query` over lore for `rcar-isp` removal/deprecate terms surfaced no removal discussion. Separate `web.search_query` results provided the Renesas product, eval-board, and 2026 design-win URLs. Because the hardware is still active and seeing new deployments, and because upstream work is recent enablement rather than sunset maintenance, the right call is `keep`, with no natural replacement driver.