xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, xen-devel@lists.xen.org
Cc: edgar.iglesias@xilinx.com, sstabellini@kernel.org, wei.liu2@citrix.com
Subject: Re: [PATCH v2 1/1] xen/device-tree: Do not remap IRQs for secondary IRQ controllers
Date: Tue, 17 May 2016 12:20:43 +0100	[thread overview]
Message-ID: <573AFE8B.3020003@arm.com> (raw)
In-Reply-To: <1463411035-13562-2-git-send-email-edgar.iglesias@gmail.com>

Hi Edgar,

On 16/05/16 16:03, Edgar E. Iglesias wrote:
> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
>
> Do not remap IRQs connected to secondary interrupt controllers.
> These IRQs have no meaning to us until they connect to the
> primary controller.
>
> Secondary IRQ controllers will at some point connect to the
> primary controller (possibly via other IRQ controllers). We
> map the IRQs at that last connection point.
>
> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>

With the change mention below:

Reviewed-by:  Julien Grall <julien.grall@linaro.org>

> ---
>   xen/common/device_tree.c | 16 ++++++++++++++++
>   1 file changed, 16 insertions(+)
>
> diff --git a/xen/common/device_tree.c b/xen/common/device_tree.c
> index 0ed86a7..02a7ede 100644
> --- a/xen/common/device_tree.c
> +++ b/xen/common/device_tree.c
> @@ -1176,6 +1176,22 @@ int dt_for_each_irq_map(const struct dt_device_node *dev,
>           for ( i = 0; i < pintsize; i++ )
>               dt_raw_irq.specifier[i] = dt_read_number(imap + i, 1);
>
> +        if ( dt_raw_irq.controller != dt_interrupt_controller )
> +        {
> +            /* We don't map IRQs connected to secondary IRQ controllers as

The comments in Xen looks like:

/*
  * Foo
  * Bart
  */

> +             * these IRQs have no meaning to us until they connect to the
> +             * primary controller.
> +             *
> +             * Secondary IRQ controllers will at some point connect to
> +             * the primary controller (possibly via other IRQ controllers).
> +             * We map the IRQs at that last connection point.
> +             */
> +            imap += pintsize;
> +            imaplen -= pintsize;
> +            dt_dprintk(" -> Skipped IRQ for secondary IRQ controller\n");
> +            continue;
> +        }
> +
>           ret = dt_irq_translate(&dt_raw_irq, &dt_irq);
>           if ( ret )
>           {
>

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-05-17 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 15:03 [PATCH v2 0/1] xen/device-tree: Do not remap IRQs for secondary IRQ controllers Edgar E. Iglesias
2016-05-16 15:03 ` [PATCH v2 1/1] " Edgar E. Iglesias
2016-05-17 11:20   ` Julien Grall [this message]
2016-05-17 12:16     ` Edgar E. Iglesias
2016-05-16 15:47 ` [PATCH v2 0/1] " Wei Liu
2016-05-16 16:30   ` Julien Grall
2016-05-17  9:00     ` Wei Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=573AFE8B.3020003@arm.com \
    --to=julien.grall@arm.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).