Hi Bin,

On 27 April 2015 at 00:16, Bin Meng <bmeng...@gmail.com> wrote:
> Intel Quark SoC has the same interrupt routing mechanism as the
> Queensbay platform, only the difference is that PCI devices'
> INTA/B/C/D are harcoded and cannot be changed freely.
>
> Signed-off-by: Bin Meng <bmeng...@gmail.com>
>
> ---
>
>  arch/x86/cpu/quark/Makefile              |   2 +-
>  arch/x86/cpu/quark/irq.c                 | 173 
> +++++++++++++++++++++++++++++++
>  arch/x86/cpu/quark/quark.c               |   8 ++
>  arch/x86/include/asm/arch-quark/device.h |  70 ++++++++++---
>  arch/x86/include/asm/arch-quark/irq.h    |  55 ++++++++++
>  arch/x86/include/asm/arch-quark/quark.h  |  15 +++
>  configs/galileo_defconfig                |   1 +
>  include/configs/galileo.h                |   1 +
>  8 files changed, 309 insertions(+), 16 deletions(-)
>  create mode 100644 arch/x86/cpu/quark/irq.c
>  create mode 100644 arch/x86/include/asm/arch-quark/irq.h

Before going too far down this path I'd like to see if we can put the
IRQ data in the device tree. What do you think?

Regards,
Simon
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Reply via email to