All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Shannon Zhao <shannon.zhao@linaro.org>,
	Shannon Zhao <zhaoshenglong@huawei.com>,
	xen-devel@lists.xen.org
Cc: sstabellini@kernel.org
Subject: Re: [for-4.7 1/5] drivers/pl011: ACPI: The interrupt should always be high level triggered
Date: Thu, 7 Apr 2016 14:59:25 +0100	[thread overview]
Message-ID: <570667BD.1040101@arm.com> (raw)
In-Reply-To: <57066758.1080102@linaro.org>



On 07/04/16 14:57, Shannon Zhao wrote:
> On 2016年04月07日 21:41, Julien Grall wrote:
>>
>> On 07/04/16 13:30, Shannon Zhao wrote:
>>>
>>>
>>> On 2016/4/7 18:59, Julien Grall wrote:
>>>> The SPCR does not specify if the interrupt is edge or level triggered.
>>>> So the configuration needs to be hardcoded in the code.
>>>>
>>>> Based on the PL011 TRM (see 2.2.8 in ARM DDI 0183G), the interrupt
>>>> generated
>>>> will be active high. This wording implies the interrupt should be
>>>> high level
>>>> triggered.
>>> I think active high can stand rising edge triggered for edge triggered
>>> interrupt.
>>>
>>> E.g. see "Table 5-118 Flag Definitions: Virtual Timer, EL2 timers, and
>>> Secure & Non-Secure EL1 timers" in ACPI SPEC 6.0.
>>
>> I've spoken with multiple person about the wording and the consensus is
>> "active high" would imply high level triggered. So it's very ambiguous.
>>
>> However, the PL011 is always using a high level triggered. You can look
>> at the device tree bindings such as the one for the foundation model.
>>
>> Also, the SBSA (section 4.3.2 in ARM-DEN-0029 v2.3) states the PL011
>> implemented with a level triggered interrupt.
>>
>> Note, I wasn't able to get the serial console working on my platform
>> with edge triggered interrupt.
>
> So how about IRQ_TYPE_LEVEL_HIGH instead of IRQ_TYPE_LEVEL_MASK?

Good point. I will likely resend only this patch and update the commit 
message too.

Regards,

-- 
Julien Grall

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

  reply	other threads:[~2016-04-07 13:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 10:59 [for-4.7 0/5] xen/arm: acpi: Bunch of fixes to use ACPI with SMP and PL011 Julien Grall
2016-04-07 10:59 ` [for-4.7 1/5] drivers/pl011: ACPI: The interrupt should always be high level triggered Julien Grall
2016-04-07 12:30   ` Shannon Zhao
2016-04-07 13:41     ` Julien Grall
2016-04-07 13:57       ` Shannon Zhao
2016-04-07 13:59         ` Julien Grall [this message]
2016-04-07 10:59 ` [for-4.7 2/5] xen/arm: acpi: The boot CPU does not always match the first entry in the MADT Julien Grall
2016-04-07 12:49   ` Shannon Zhao
2016-04-10 20:16   ` Stefano Stabellini
2016-04-07 10:59 ` [for-4.7 3/5] xen/arm: acpi: Fix SMP support when booting with ACPI Julien Grall
2016-04-07 12:20   ` Shannon Zhao
2016-04-10 20:18   ` Stefano Stabellini
2016-04-07 10:59 ` [for-4.7 4/5] xen/arm: acpi: Remove uncessary check in acpi_map_gic_cpu_interface Julien Grall
2016-04-07 12:23   ` Shannon Zhao
2016-04-10 20:19   ` Stefano Stabellini
2016-04-07 10:59 ` [for-4.7 5/5] xen/arm: acpi: Print more error messages " Julien Grall
2016-04-07 12:22   ` Shannon Zhao
2016-04-10 20:21   ` Stefano Stabellini

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=570667BD.1040101@arm.com \
    --to=julien.grall@arm.com \
    --cc=shannon.zhao@linaro.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xen.org \
    --cc=zhaoshenglong@huawei.com \
    /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.