All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org,
	Pranavkumar Sawargaonkar <psawargaonkar@apm.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] xen: arm: log warning for interrupt configuration mismatch
Date: Tue, 03 Mar 2015 12:20:50 +0000	[thread overview]
Message-ID: <54F5A722.5060102@linaro.org> (raw)
In-Reply-To: <1425315713.24959.17.camel@citrix.com>

Hi Ian,

On 02/03/2015 17:01, Ian Campbell wrote:
> On Mon, 2015-03-02 at 12:56 +0000, Julien Grall wrote:
>
>>>  From 852f6e3fe49f7fab801f2857b8b505922556d746 Mon Sep 17 00:00:00 2001
>>> From: Ian Campbell <ian.campbell@citrix.com>
>>> Date: Mon, 2 Mar 2015 11:09:35 +0000
>>> Subject: [PATCH] xen: arm: Assume level triggered means high, not low.
>>>
>>> When reading back the ICFG register we cannot know the polarity of the
>>> configuration, just that it is level or edge.
>>>
>>> Since falling edge and low level are invalid for SPIs we should assume
>>> rising edge and high level (we have no better information for PPIs, so
>>> it'll have to do).
>>>
>>> We already assumed rising edge, switch to high level as well.
>>>
>>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>>
>> Given the usage of desc->arch.type in Xen, I think this is the right
>> solution:
>>
>> Reviewed-by: Julien Grall <julien.grall@linaro.org>
>
> Applied, thanks.
>
> With your "don't warn if high-level" patch[*] is that all of the fallout
> from this series, other than making desc->arch.type just track level vs
> edge without polarity?

Yes.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-03-03 12:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19 15:39 [PATCH 0/2] xen: arm: warn for gic and arch timer misconfiguration Ian Campbell
2015-02-19 15:24 ` [PATCH 1/2] xen: arm: log warning for interrupt configuration mismatch Ian Campbell
2015-02-19 15:45   ` Julien Grall
2015-02-28 22:12   ` Julien Grall
2015-03-02 11:12     ` Ian Campbell
2015-03-02 12:56       ` Julien Grall
2015-03-02 13:42         ` Ian Campbell
2015-03-02 13:48           ` Julien Grall
2015-03-02 13:53             ` Ian Campbell
2015-03-02 14:02               ` Julien Grall
2015-03-02 14:41                 ` Ian Campbell
2015-03-02 17:01         ` Ian Campbell
2015-03-03 12:20           ` Julien Grall [this message]
2015-02-19 15:24 ` [PATCH 2/2] xen: arm: Warn if timer interrupts are not level triggered Ian Campbell
2015-02-19 15:41   ` Julien Grall
2015-02-19 16:10     ` Ian Campbell
2015-02-19 16:20       ` Julien Grall
2015-02-25 14:36         ` Ian Campbell
2015-02-28 22:20   ` Julien Grall
2015-03-02 11:13     ` Ian Campbell

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=54F5A722.5060102@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=psawargaonkar@apm.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.