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: Mon, 02 Mar 2015 13:48:55 +0000 [thread overview]
Message-ID: <54F46A47.1040906@linaro.org> (raw)
In-Reply-To: <1425303755.21151.20.camel@citrix.com>
On 02/03/15 13:42, Ian Campbell wrote:
>>> I even reread the spec before sending and reached the same conclusion,
>>> but apparently managed to fail to change the actual code!
>>>
>>> Question is -- what to do about PPIs, since the CFG register cannot
>>> express the polarity of the edge or level. I suppose we may as well just
>>> assume the one that is compatible with SPIs, since we have nothing
>>> better to go on.
>>
>> Linux seems to set edge (resp. level) bit for any edge (resp. level)
>> type interrupts.
>
> Right, sorry I wasn't clear. We should obviously do this too when
> writing to ICFG (I believe we do), the case I was talking about was the
> one relating to the quoted code above: when we read back ICFG and find
> that the setting hasn't taken. In that case we want to update
> desc->arch.type to somehow reflect "reality", which requires us to
> fabricate a polarity for the interrupt (rising/falling or low/high).
desc->arch.type is only used in Xen for IRQ configuration.
Given that, I was wondering if it would be useful to only store
EDGE/LEVEL in the desc->arch.type and, therefore, ignoring
rising/falling and low/high.
That would make the code simpler.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-03-02 13:48 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 [this message]
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
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=54F46A47.1040906@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.