mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: fangxiang <fangxiang3@huawei.com>,
	tglx@linutronix.de, ljason@lakedaemon.net
Cc: linux-kernel@vger.kernel.org, gengyanping@hisilicon.com
Subject: Re: [PATCH] irqchip/gic-v3: Fix gic_chip specific flag
Date: Tue, 30 Jan 2018 17:01:36 +0000	[thread overview]
Message-ID: <e1e4f8de-e59b-0459-cc32-bed7181f8872@arm.com> (raw)
In-Reply-To: <1517281005-18993-1-git-send-email-fangxiang3@huawei.com>

On 30/01/18 02:56, fangxiang wrote:
> Both IRQCHIP_SKIP_SET_WAKE and .irq_set_wake() is
> not set in gic_chip V3. This causes
> set_irq_wake_real() return -ENXIO and a
> WARN(Unbalanced IRQ ... wake disable ...) in
> irq_set_irq_wake().
> 
> Signed-off-by: fangxiang <fangxiang3@huawei.com>
> ---
>  drivers/irqchip/irq-gic-v3.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
> index b56c3e2..e8104b8 100644
> --- a/drivers/irqchip/irq-gic-v3.c
> +++ b/drivers/irqchip/irq-gic-v3.c
> @@ -800,7 +800,8 @@ static inline void gic_cpu_pm_init(void) { }
>  	.irq_set_affinity	= gic_set_affinity,
>  	.irq_get_irqchip_state	= gic_irq_get_irqchip_state,
>  	.irq_set_irqchip_state	= gic_irq_set_irqchip_state,
> -	.flags			= IRQCHIP_SET_TYPE_MASKED,
> +	.flags			= IRQCHIP_SET_TYPE_MASKED |
> +				  IRQCHIP_SKIP_SET_WAKE,
>  };
>  
>  static struct irq_chip gic_eoimode1_chip = {
> 

That's sort of expected (the GIC itself doesn't implement any wake-up
mechanism), *unless* you have have a separate, stacked irqchip
implementing irq_set_wake. From your commit message, I cannot deduce
whether that's the case or not.

Please describe what you are fixing, and to what context this applies to.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

      reply	other threads:[~2018-01-30 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  2:56 fangxiang
2018-01-30 17:01 ` Marc Zyngier [this message]

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=e1e4f8de-e59b-0459-cc32-bed7181f8872@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=fangxiang3@huawei.com \
    --cc=gengyanping@hisilicon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ljason@lakedaemon.net \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome