drivers/mfd/mt6358-irq.c
Source file repositories/reference/linux-study-clean/drivers/mfd/mt6358-irq.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mfd/mt6358-irq.c- Extension
.c- Size
- 7263 bytes
- Lines
- 295
- Domain
- Driver Families
- Bucket
- drivers/mfd
- 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/interrupt.hlinux/irq.hlinux/irqdomain.hlinux/mfd/mt6357/core.hlinux/mfd/mt6357/registers.hlinux/mfd/mt6358/core.hlinux/mfd/mt6358/registers.hlinux/mfd/mt6359/core.hlinux/mfd/mt6359/registers.hlinux/mfd/mt6397/core.hlinux/module.hlinux/platform_device.hlinux/regmap.h
Detected Declarations
function pmic_irq_enablefunction pmic_irq_disablefunction pmic_irq_lockfunction pmic_irq_sync_unlockfunction mt6358_irq_sp_handlerfunction mt6358_irq_handlerfunction pmic_irq_domain_mapfunction mt6358_irq_init
Annotated Snippet
if (ret) {
dev_err(chip->dev,
"Failed to read IRQ status, ret=%d\n", ret);
return;
}
if (!irq_status)
continue;
status = irq_status;
do {
j = __ffs(status);
hwirq = irqd->pmic_ints[top_gp].hwirq_base +
MTK_PMIC_REG_WIDTH * i + j;
virq = irq_find_mapping(chip->irq_domain, hwirq);
if (virq)
handle_nested_irq(virq);
status &= ~BIT(j);
} while (status);
regmap_write(chip->regmap, sta_reg, irq_status);
}
}
static irqreturn_t mt6358_irq_handler(int irq, void *data)
{
struct mt6397_chip *chip = data;
struct pmic_irq_data *irqd = chip->irq_data;
unsigned int bit, i, top_irq_status = 0;
int ret;
ret = regmap_read(chip->regmap,
irqd->top_int_status_reg,
&top_irq_status);
if (ret) {
dev_err(chip->dev,
"Failed to read status from the device, ret=%d\n", ret);
return IRQ_NONE;
}
for (i = 0; i < irqd->num_top; i++) {
bit = BIT(irqd->pmic_ints[i].top_offset);
if (top_irq_status & bit) {
mt6358_irq_sp_handler(chip, i);
top_irq_status &= ~bit;
if (!top_irq_status)
break;
}
}
return IRQ_HANDLED;
}
static int pmic_irq_domain_map(struct irq_domain *d, unsigned int irq,
irq_hw_number_t hw)
{
struct mt6397_chip *mt6397 = d->host_data;
irq_set_chip_data(irq, mt6397);
irq_set_chip_and_handler(irq, &mt6358_irq_chip, handle_level_irq);
irq_set_nested_thread(irq, 1);
irq_set_noprobe(irq);
return 0;
}
static const struct irq_domain_ops mt6358_irq_domain_ops = {
.map = pmic_irq_domain_map,
.xlate = irq_domain_xlate_twocell,
};
int mt6358_irq_init(struct mt6397_chip *chip)
{
int i, j, ret;
struct pmic_irq_data *irqd;
switch (chip->chip_id) {
case MT6357_CHIP_ID:
chip->irq_data = &mt6357_irqd;
break;
case MT6358_CHIP_ID:
case MT6366_CHIP_ID:
chip->irq_data = &mt6358_irqd;
break;
case MT6359_CHIP_ID:
Annotation
- Immediate include surface: `linux/interrupt.h`, `linux/irq.h`, `linux/irqdomain.h`, `linux/mfd/mt6357/core.h`, `linux/mfd/mt6357/registers.h`, `linux/mfd/mt6358/core.h`, `linux/mfd/mt6358/registers.h`, `linux/mfd/mt6359/core.h`.
- Detected declarations: `function pmic_irq_enable`, `function pmic_irq_disable`, `function pmic_irq_lock`, `function pmic_irq_sync_unlock`, `function mt6358_irq_sp_handler`, `function mt6358_irq_handler`, `function pmic_irq_domain_map`, `function mt6358_irq_init`.
- Atlas domain: Driver Families / drivers/mfd.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
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.