drivers/greybus/control.c

File Facts

System

Linux kernel

Corpus path

drivers/greybus/control.c

Extension

.c

Size

14205 bytes

Lines

585

Domain

Driver Families

Bucket

drivers/greybus

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/module.h
• linux/slab.h
• linux/greybus.h

Detected Declarations

• function gb_control_get_version
• function gb_control_get_bundle_version
• function gb_control_get_bundle_versions
• function list_for_each_entry
• function gb_control_get_manifest_size_operation
• function gb_control_get_manifest_operation
• function gb_control_connected_operation
• function gb_control_disconnected_operation
• function gb_control_disconnecting_operation
• function gb_control_mode_switch_operation
• function gb_control_bundle_pm_status_map
• function gb_control_bundle_suspend
• function gb_control_bundle_resume
• function gb_control_bundle_deactivate
• function gb_control_bundle_activate
• function gb_control_interface_pm_status_map
• function gb_control_interface_suspend_prepare
• function gb_control_interface_deactivate_prepare
• function gb_control_interface_hibernate_abort
• function vendor_string_show
• function product_string_show
• function gb_control_release
• function gb_control_enable
• function gb_control_disable
• function gb_control_suspend
• function gb_control_resume
• function gb_control_add
• function gb_control_del
• function gb_control_put
• function gb_control_mode_switch_prepare
• function gb_control_mode_switch_complete

Annotated Snippet

ret = device_add(&control->dev);
	if (ret) {
		dev_err(&control->dev,
			"failed to register control device: %d\n",
			ret);
		return ret;
	}

	return 0;
}

void gb_control_del(struct gb_control *control)
{
	if (device_is_registered(&control->dev))
		device_del(&control->dev);
}

struct gb_control *gb_control_get(struct gb_control *control)
{
	get_device(&control->dev);

	return control;
}

void gb_control_put(struct gb_control *control)
{
	put_device(&control->dev);
}

void gb_control_mode_switch_prepare(struct gb_control *control)
{
	gb_connection_mode_switch_prepare(control->connection);
}

void gb_control_mode_switch_complete(struct gb_control *control)
{
	gb_connection_mode_switch_complete(control->connection);
}

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/slab.h`, `linux/greybus.h`.
• Detected declarations: `function gb_control_get_version`, `function gb_control_get_bundle_version`, `function gb_control_get_bundle_versions`, `function list_for_each_entry`, `function gb_control_get_manifest_size_operation`, `function gb_control_get_manifest_operation`, `function gb_control_connected_operation`, `function gb_control_disconnected_operation`, `function gb_control_disconnecting_operation`, `function gb_control_mode_switch_operation`.
• Atlas domain: Driver Families / drivers/greybus.
• 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.