[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X9EYRNDXS1Xcy4iU@kroah.com>
Date: Wed, 9 Dec 2020 19:32:36 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: John Garry <john.garry@...wei.com>
Cc: jejb@...ux.ibm.com, martin.petersen@...cle.com, lenb@...nel.org,
rjw@...ysocki.net, tglx@...utronix.de, maz@...nel.org,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxarm@...wei.com, linux-acpi@...r.kernel.org, dwagner@...e.de
Subject: Re: [PATCH v5 4/5] Driver core: platform: Add
devm_platform_get_irqs_affinity()
On Wed, Dec 02, 2020 at 06:36:56PM +0800, John Garry wrote:
> Drivers for multi-queue platform devices may also want managed interrupts
> for handling HW queue completion interrupts, so add support.
Why would a platform device want all of this? Shouldn't such a device
be on a "real" bus instead?
What in-kernel driver needs this complexity? I can't take new apis
without a real user in the tree, sorry.
thanks,
greg k-h
Powered by blists - more mailing lists