drivers/pinctrl/intel/pinctrl-cherryview.c

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/intel/pinctrl-cherryview.c

Extension

.c

Size

51570 bytes

Lines

1788

Domain

Driver Families

Bucket

drivers/pinctrl

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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/acpi.h
• linux/array_size.h
• linux/cleanup.h
• linux/dmi.h
• linux/gpio/driver.h
• linux/module.h
• linux/platform_device.h
• linux/seq_file.h
• linux/types.h
• linux/pinctrl/consumer.h
• linux/pinctrl/pinconf-generic.h
• linux/pinctrl/pinconf.h
• linux/pinctrl/pinctrl.h
• linux/pinctrl/pinmux.h
• pinctrl-intel.h

Detected Declarations

• struct intel_pad_context
• struct intel_community_context
• function chv_pctrl_readl
• function chv_pctrl_writel
• function chv_readl
• function chv_writel
• function chv_pad_is_locked
• function chv_pad_locked
• function chv_pin_dbg_show
• function scoped_guard
• function chv_pinmux_set_mux
• function chv_gpio_clear_triggering
• function chv_gpio_request_enable
• function mode
• function chv_gpio_disable_free
• function chv_gpio_set_direction
• function chv_config_get
• function scoped_guard
• function chv_config_set_pull
• function chv_config_set_oden
• function chv_config_set
• function chv_config_group_get
• function chv_config_group_set
• function chv_gpio_get
• function chv_gpio_set
• function chv_gpio_get_direction
• function chv_gpio_direction_input
• function chv_gpio_direction_output
• function chv_gpio_irq_ack
• function chv_gpio_irq_mask_unmask
• function chv_gpio_irq_mask
• function chv_gpio_irq_unmask
• function chv_gpio_irq_startup
• function used
• function chv_gpio_set_intr_line
• function chv_gpio_irq_type
• function chv_gpio_irq_handler
• function for_each_set_bit
• function chv_init_irq_valid_mask
• function chv_gpio_irq_init_hw
• function chv_gpio_probe
• function chv_pinctrl_mmio_access_handler
• function chv_pinctrl_probe
• function chv_pinctrl_remove
• function chv_pinctrl_suspend_noirq
• function chv_pinctrl_resume_noirq
• function chv_pinctrl_init
• function chv_pinctrl_exit

Annotated Snippet

subsys_initcall(chv_pinctrl_init);

static void __exit chv_pinctrl_exit(void)
{
	platform_driver_unregister(&chv_pinctrl_driver);
}
module_exit(chv_pinctrl_exit);

MODULE_AUTHOR("Mika Westerberg <mika.westerberg@linux.intel.com>");
MODULE_DESCRIPTION("Intel Cherryview/Braswell pinctrl driver");
MODULE_LICENSE("GPL v2");
MODULE_IMPORT_NS("PINCTRL_INTEL");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/array_size.h`, `linux/cleanup.h`, `linux/dmi.h`, `linux/gpio/driver.h`, `linux/module.h`, `linux/platform_device.h`, `linux/seq_file.h`.
• Detected declarations: `struct intel_pad_context`, `struct intel_community_context`, `function chv_pctrl_readl`, `function chv_pctrl_writel`, `function chv_readl`, `function chv_writel`, `function chv_pad_is_locked`, `function chv_pad_locked`, `function chv_pin_dbg_show`, `function scoped_guard`.
• Atlas domain: Driver Families / drivers/pinctrl.
• Implementation status: integration 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.