Skip to content
  • Peter Maydell's avatar
    f37fc537
    hw/arm/exynos4210: Drop Exynos4210Irq struct · f37fc537
    Peter Maydell authored
    
    
    The only time we use the int_combiner_irq[] and ext_combiner_irq[]
    arrays in the Exynos4210Irq struct is during realize of the SoC -- we
    initialize them with the input IRQs of the combiner devices, and then
    connect those to outputs of other devices in
    exynos4210_init_board_irqs().  Now that the combiner objects are
    easily accessible as s->int_combiner and s->ext_combiner we can make
    the connections directly from one device to the other without going
    via these arrays.
    
    Since these are the only two remaining elements of Exynos4210Irq,
    we can remove that struct entirely.
    
    Signed-off-by: default avatarPeter Maydell <peter.maydell@linaro.org>
    Reviewed-by: default avatarRichard Henderson <richard.henderson@linaro.org>
    Message-id: 20220404154658.565020-19-peter.maydell@linaro.org
    f37fc537
    hw/arm/exynos4210: Drop Exynos4210Irq struct
    Peter Maydell authored
    
    
    The only time we use the int_combiner_irq[] and ext_combiner_irq[]
    arrays in the Exynos4210Irq struct is during realize of the SoC -- we
    initialize them with the input IRQs of the combiner devices, and then
    connect those to outputs of other devices in
    exynos4210_init_board_irqs().  Now that the combiner objects are
    easily accessible as s->int_combiner and s->ext_combiner we can make
    the connections directly from one device to the other without going
    via these arrays.
    
    Since these are the only two remaining elements of Exynos4210Irq,
    we can remove that struct entirely.
    
    Signed-off-by: default avatarPeter Maydell <peter.maydell@linaro.org>
    Reviewed-by: default avatarRichard Henderson <richard.henderson@linaro.org>
    Message-id: 20220404154658.565020-19-peter.maydell@linaro.org
Loading