Scribd Logo
Upload

Welcome to Scribd!

  • 123 views

    Irq Domain

    Uploaded by

    Rajesh ravi
    The document discusses the irq_domain interrupt number mapping library in Linux. It explains that as more interrupt controllers are used in systems, a mechanism is needed to separate local interrupt numbers from Linux IRQ numbers. The irq_domain library provides mapping between hardware interrupt numbers and Linux IRQ numbers, managing this mapping instead of individual interrupt controller drivers coding their own reverse mapping. Interrupt controller drivers can create and register irq_domains to manage the mapping for their interrupts.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd

    Irq Domain

    Uploaded by

    Rajesh ravi
    123 views1 page
    The document discusses the irq_domain interrupt number mapping library in Linux. It explains that as more interrupt controllers are used in systems, a mechanism is needed to separate local interrupt numbers from Linux IRQ numbers. The irq_domain library provides mapping between hardware interrupt numbers and Linux IRQ numbers, managing this mapping instead of individual interrupt controller drivers coding their own reverse mapping. Interrupt controller drivers can create and register irq_domains to manage the mapping for their interrupts.

    Original Description:

    Irq Domain description

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the irq_domain interrupt number mapping library in Linux. It explains that as more interrupt controllers are used in systems, a mechanism is needed to separate local interrupt numbers from Linux IRQ numbers. The irq_domain library provides mapping between hardware interrupt numbers and Linux IRQ numbers, managing this mapping instead of individual interrupt controller drivers coding their own reverse mapping. Interrupt controller drivers can create and register irq_domains to manage the mapping for their interrupts.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    123 views1 page

    Irq Domain

    Uploaded by

    Rajesh ravi
    The document discusses the irq_domain interrupt number mapping library in Linux. It explains that as more interrupt controllers are used in systems, a mechanism is needed to separate local interrupt numbers from Linux IRQ numbers. The irq_domain library provides mapping between hardware interrupt numbers and Linux IRQ numbers, managing this mapping instead of individual interrupt controller drivers coding their own reverse mapping. Interrupt controller drivers can create and register irq_domains to manage the mapping for their interrupts.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Download as txt, pdf, or txt
    You are on page 1of 1

    ===============================================

    The irq_domain interrupt number mapping library


    ===============================================

    The current design of the Linux kernel uses a single large number
    space where each separate IRQ source is assigned a different number.
    This is simple when there is only one interrupt controller, but in
    systems with multiple interrupt controllers the kernel must ensure
    that each one gets assigned non-overlapping allocations of Linux
    IRQ numbers.

    The number of interrupt controllers registered as unique irqchips


    show a rising tendency: for example subdrivers of different kinds
    such as GPIO controllers avoid reimplementing identical callback
    mechanisms as the IRQ core system by modelling their interrupt
    handlers as irqchips, i.e. in effect cascading interrupt controllers.

    Here the interrupt number loose all kind of correspondence to


    hardware interrupt numbers: whereas in the past, IRQ numbers could
    be chosen so they matched the hardware IRQ line into the root
    interrupt controller (i.e. the component actually fireing the
    interrupt line to the CPU) nowadays this number is just a number.

    For this reason we need a mechanism to separate controller-local


    interrupt numbers, called hardware irq's, from Linux IRQ numbers.

    The irq_alloc_desc*() and irq_free_desc*() APIs provide allocation of


    irq numbers, but they don't provide any support for reverse mapping of
    the controller-local IRQ (hwirq) number into the Linux IRQ number
    space.

    The irq_domain library adds mapping between hwirq and IRQ numbers on
    top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
    preferred over interrupt controller drivers open coding their own
    reverse mapping scheme.

    irq_domain also implements translation from an abstract irq_fwspec


    structure to hwirq numbers (Device Tree and ACPI GSI so far), and can
    be easily extended to support other IRQ topology data sources.

    irq_domain usage
    ================

    An interrupt controller driver creates and registers an irq_domain by


    calling one of the irq_domain_add_*() functions (each mapping method
    has a different allocator function, more on that later). The function
    will return a pointer to the irq_domain on success. The caller must
    provide the allocator function with an irq_domain_ops structure.

    In most cases, the irq_domain will begin empty without any mappings
    between hwirq and IRQ numbers. Mappings are added to the irq_domain
    by calling irq_create_mapping() which accepts the irq_domain and a

    You might also like