NXP ISP1760/1761/1763 embedded USB 2.0 controllers
A family of standalone USB 2.0 host, peripheral, and OTG controller chips originally designed by Philips and later sold by NXP, dating from the mid-2000s. They were typically soldered onto embedded and industrial boards that needed USB connectivity without a built-in SoC USB controller, and they connect over a simple parallel bus rather than PCI.
recommendation
Worth keeping but documenting as niche: the silicon is old and not used in mainstream 2025 hardware, but the code is still actively maintained, with a fix landing on the linux-usb list as recently as April 2025. Real-world users are likely limited to long-lived embedded and industrial boards, so the driver should stay while its legacy status is made explicit.
repository signals
sources
- lore.kernel.org
Upstream still sees driver-specific fixes in 2025, indicating active maintenance rather than abandonment.
- alldatasheet.com
ISP1761 is an old Philips/NXP USB OTG controller product, with publicly mirrored datasheet revisions dating back to the mid-2000s.
- alldatasheet.com
A later public datasheet mirror still describes the same legacy ISP1761 part rather than a current-generation replacement family.
codex reasoning notes (technical)
Real driver directory: Kconfig names module support for NXP ISP 1760/1761/1763, with host, gadget, and dual-role modes. Lore evidence came from `mcp__lore_http__.lore_file_timeline` and `mcp__lore_http__.lore_activity` on `drivers/usb/isp1760/isp1760-core.c`; newest touch is a 2025-04-24 linux-usb fix patch, so removal/deprecation is not supported by current upstream activity. An attempted lore removal-subject scan timed out, and a `lei` fallback was blocked by the sandbox, so absence of removal discussion is inferred only from the successful lore activity results. Deployment looks niche: these are older external embedded USB controller chips used on non-DMA-master style buses and eval/industrial designs, not mainstream 2025 platforms. Datasheet URLs were obtained via `web.search_query`; they support that the silicon family is old, but they do not prove formal EOL, so `last_widely_available_year` is left null. Recommendation is `keep-annotate`: active maintenance exists, but current use is likely limited to legacy/industrial embedded boards with low new deployment volume.