[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2yve3R1w5igBYMy3HSFJ8Xt4BHhXQcaTAkNCdZXZ1v-w@mail.gmail.com>
Date: Mon, 16 Mar 2020 09:25:00 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Michael Kelley <mikelley@...rosoft.com>
Cc: Will Deacon <will@...nel.org>, Ard Biesheuvel <ardb@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Mark Rutland <mark.rutland@....com>,
Marc Zyngier <maz@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
gregkh <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-hyperv@...r.kernel.org,
linux-efi <linux-efi@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>, olaf@...fle.de,
Andy Whitcroft <apw@...onical.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Jason Wang <jasowang@...hat.com>, marcelo.cerri@...onical.com,
"K. Y. Srinivasan" <kys@...rosoft.com>, sunilmut@...rosoft.com,
Boqun Feng <boqun.feng@...il.com>
Subject: Re: [PATCH v6 05/10] arm64: hyperv: Add interrupt handlers for VMbus
and stimer
On Sat, Mar 14, 2020 at 4:36 PM Michael Kelley <mikelley@...rosoft.com> wrote:
>
> Add ARM64-specific code to set up and handle the interrupts
> generated by Hyper-V for VMbus messages and for stimer expiration.
>
> This code is architecture dependent and is mostly driven by
> architecture independent code in the VMbus driver and the
> Hyper-V timer clocksource driver.
>
> This code is built only when CONFIG_HYPERV is enabled.
>
> Signed-off-by: Michael Kelley <mikelley@...rosoft.com>
This looks like it should be a nested irqchip driver instead, so your
device drivers can use the normal request_irq() functions etc.
Is anything preventing you from doing that? If so, please describe
that in the changelog and in a comment in the driver.
Arnd
Powered by blists - more mailing lists