drivers/usb/renesas_usbhs/rcar2.c

File Facts

System

Linux kernel

Corpus path

drivers/usb/renesas_usbhs/rcar2.c

Extension

.c

Size

1544 bytes

Lines

76

Domain

Driver Families

Bucket

drivers/usb

Inferred role

Driver Families: implementation source

Status

source implementation candidate

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/phy/phy.h
• common.h
• rcar2.h

Detected Declarations

• function Copyright
• function usbhs_rcar2_hardware_exit
• function usbhs_rcar2_power_ctrl

Annotated Snippet

if (enable) {
			retval = phy_init(priv->phy);

			if (!retval)
				retval = phy_power_on(priv->phy);
		} else {
			phy_power_off(priv->phy);
			phy_exit(priv->phy);
			retval = 0;
		}
	}

	return retval;
}

const struct renesas_usbhs_platform_info usbhs_rcar_gen2_plat_info = {
	.platform_callback = {
		.hardware_init = usbhs_rcar2_hardware_init,
		.hardware_exit = usbhs_rcar2_hardware_exit,
		.power_ctrl = usbhs_rcar2_power_ctrl,
		.get_id = usbhs_get_id_as_gadget,
	},
	.driver_param = {
		.has_usb_dmac = 1,
		.has_new_pipe_configs = 1,
	},
};

Annotation

• Immediate include surface: `linux/phy/phy.h`, `common.h`, `rcar2.h`.
• Detected declarations: `function Copyright`, `function usbhs_rcar2_hardware_exit`, `function usbhs_rcar2_power_ctrl`.
• Atlas domain: Driver Families / drivers/usb.
• Implementation status: source implementation candidate.

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.