All of lore.kernel.org
 help / color / mirror / Atom feed
From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] ARM: sun7i: irqchip: Update the documentation
Date: Wed, 08 Jan 2014 14:03:05 +0100	[thread overview]
Message-ID: <52CD4C89.1040604@redhat.com> (raw)
In-Reply-To: <CAOQ7t2bg7qmwnQ-7iqbKCqK8fNS5GC=G0BN2188FQhPLN3v9VQ@mail.gmail.com>

Hi,

On 01/08/2014 12:49 PM, Carlo Caione wrote:
> On Wed, Jan 8, 2014 at 12:29 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Monday 06 January 2014, Carlo Caione wrote:
>>> +Allwinner Sunxi NMI Controller
>>> +==============================
>>> +
>>> +Required properties:
>>> +
>>> +- compatible : should be "allwinner,sun7i-sc-nmi"
>>> +- reg : Specifies base physical address and size of the registers.
>>> +- interrupt-controller : Identifies the node as an interrupt controller
>>> +- #interrupt-cells : Specifies the number of cells needed to encode an
>>> +  interrupt source. The value shall be 2.
>>
>> I think you should list what the two cells are so users know what to
>> put in the irq specifier.
>
> Agree, I'll fix in v3
>
>>> +sc-nmi-intc at 01c00030 {
>>> +       compatible = "allwinner,sun7i-sc-nmi";
>>> +       interrupt-controller;
>>> +       #interrupt-cells = <2>;
>>> +       reg = <0x01c00030 0x0c>;
>>> +       interrupt-parent = <&gic>;
>>> +       interrupts = <0 0 1>;
>>> +};
>>
>> Is <0 0 1> the correct representation of the NMI? This question has recently
>> come up on IRC and I didn't know the answer at the time.
>
> Why shouldn't it be a correct representation? I think I missed the
> discussion on IRC.

I did not see the discussion on irc either, but this almost certainly
should be <0 0 4>, as all interrupts on sun7i are level sensitive, not
edge sensitive, making it <0 0 1> and thus edge sensitive can cause
lost interrupts if an interrupt fires between the handler has reading
the interrupt status register, and it writing it to clear the bits it
has seen. In this case the interrupt line stays high, but the interrupt
handler won't get re-run when configured for level interrupts.

Regards,

Hans

  reply	other threads:[~2014-01-08 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 17:41 [PATCH v2 0/3] ARM: sun7i: irqchip: Irqchip driver for NMI Carlo Caione
2014-01-06 17:41 ` [PATCH v2 1/3] ARM: sun7i: irqchip: Add irqchip driver for NMI controller Carlo Caione
2014-01-06 17:41 ` [PATCH v2 2/3] ARM: sun7i: dts: Add NMI irqchip support Carlo Caione
2014-01-06 17:41 ` [PATCH v2 3/3] ARM: sun7i: irqchip: Update the documentation Carlo Caione
2014-01-08 11:29   ` Arnd Bergmann
2014-01-08 11:49     ` Carlo Caione
2014-01-08 13:03       ` Hans de Goede [this message]
2014-01-09 14:00         ` Carlo Caione
2014-01-08 13:09       ` Arnd Bergmann
2014-01-09 13:59         ` [linux-sunxi] " Carlo Caione
2014-01-09 14:37           ` Arnd Bergmann
2014-01-08 10:41 ` [PATCH v2 0/3] ARM: sun7i: irqchip: Irqchip driver for NMI Carlo Caione

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=52CD4C89.1040604@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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.