From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Jonas Gorski <jonas.gorski@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 2/2] irqchip: add support for BCM6345 external interrupt controller
Date: Wed, 24 Feb 2021 08:08:28 +0100 [thread overview]
Message-ID: <C423E680-1741-43C0-A4DA-DCF65509C510@gmail.com> (raw)
In-Reply-To: <7de8507d-82dd-291e-1f63-7c1460e6a6b2@gmail.com>
Hi Florian,
> El 24 feb 2021, a las 4:43, Florian Fainelli <f.fainelli@gmail.com> escribió:
>
>
>
> On 2/23/2021 12:43 PM, Álvaro Fernández Rojas wrote:
>> This interrupt controller is present on bcm63xx SoCs in order to generate
>> interrupts based on GPIO status changes.
>>
>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
>> ---
>
> [snip]
>> +static int __init bcm6345_ext_intc_of_init(struct device_node *node,
>> + struct device_node *parent)
>> +{
>> + int num_irqs, ret = -EINVAL;
>> + unsigned i;
>> + void __iomem *base;
>> + int irqs[MAX_IRQS] = { 0 };
>> + u32 shift;
>> + bool toggle_clear_on_ack = false;
>> +
>> + num_irqs = of_irq_count(node);
>> +
>> + if (!num_irqs || num_irqs > MAX_IRQS)
>> + return -EINVAL;
>> +
>> + if (of_property_read_u32(node, "brcm,field-width", &shift))
>> + shift = 4;
>
> This property is not documented in the binding, other than that:
Nice catch, I will add it in next version.
>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> --
> Florian
next prev parent reply other threads:[~2021-02-24 7:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 18:08 [PATCH 0/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-23 18:08 ` [PATCH 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-02-23 19:34 ` Rob Herring
2021-02-24 9:35 ` kernel test robot
2021-02-23 18:08 ` [PATCH 2/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24 1:38 ` kernel test robot
2021-02-23 20:43 ` [PATCH v2 0/2] " Álvaro Fernández Rojas
2021-02-23 20:43 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-02-24 3:39 ` Florian Fainelli
2021-02-24 3:49 ` Rob Herring
2021-02-23 20:43 ` [PATCH v2 2/2] irqchip: add support for " Álvaro Fernández Rojas
2021-02-24 3:43 ` Florian Fainelli
2021-02-24 7:08 ` Álvaro Fernández Rojas [this message]
2021-02-24 7:56 ` [PATCH v2 0/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24 7:56 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: document BCM6345 external " Álvaro Fernández Rojas
2021-03-06 20:14 ` Rob Herring
2021-03-07 10:12 ` Álvaro Fernández Rojas
2021-03-10 17:21 ` Rob Herring
2021-02-24 7:56 ` [PATCH v2 2/2] irqchip: add support for " Álvaro Fernández Rojas
2021-03-09 10:58 ` Marc Zyngier
2021-02-24 7:58 ` [PATCH v2 0/2] irqchip: add support for BCM6345 " Álvaro Fernández Rojas
2021-02-24 10:03 ` Marc Zyngier
2021-02-27 6:49 ` Álvaro Fernández Rojas
2021-03-06 20:11 ` Rob Herring
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=C423E680-1741-43C0-A4DA-DCF65509C510@gmail.com \
--to=noltari@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--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
all inboxes | Powered by JetHome®