[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210406164411.GA1937531@robh.at.kernel.org>
Date: Tue, 6 Apr 2021 11:44:11 -0500
From: Rob Herring <robh@...nel.org>
To: Hector Martin <marcan@...can.st>
Cc: Alexander Graf <graf@...zon.com>, Olof Johansson <olof@...om.net>,
Stan Skowronek <stan@...ellium.com>,
devicetree@...r.kernel.org, linux-arch@...r.kernel.org,
Arnd Bergmann <arnd@...nel.org>, Will Deacon <will@...nel.org>,
Tony Lindgren <tony@...mide.com>,
Mark Kettenis <mark.kettenis@...all.nl>,
Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Marc Zyngier <maz@...nel.org>,
Mohamed Mediouni <mohamed.mediouni@...amail.com>,
linux-doc@...r.kernel.org, Krzysztof Kozlowski <krzk@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
Mark Rutland <mark.rutland@....com>,
Christoph Hellwig <hch@...radead.org>,
Catalin Marinas <catalin.marinas@....com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH v4 05/18] dt-bindings: timer: arm,arch_timer: Add
interrupt-names support
On Fri, 02 Apr 2021 18:05:29 +0900, Hector Martin wrote:
> Not all platforms provide the same set of timers/interrupts, and Linux
> only needs one (plus kvm/guest ones); some platforms are working around
> this by using dummy fake interrupts. Implementing interrupt-names allows
> the devicetree to specify an arbitrary set of available interrupts, so
> the timer code can pick the right one.
>
> This also adds the hyp-virt timer/interrupt, which was previously not
> expressed in the fixed 4-interrupt form.
>
> Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
> Acked-by: Marc Zyngier <maz@...nel.org>
> Reviewed-by: Tony Lindgren <tony@...mide.com>
> Signed-off-by: Hector Martin <marcan@...can.st>
> ---
> .../bindings/timer/arm,arch_timer.yaml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists