[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190103154439.GC16311@edgewater-inn.cambridge.arm.com>
Date: Thu, 3 Jan 2019 15:44:40 +0000
From: Will Deacon <will.deacon@....com>
To: Jonathan Cameron <jonathan.cameron@...wei.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>, linux-pci@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Shaokun Zhang <zhangshaokun@...ilicon.com>,
linuxarm@...wei.com, Keith Busch <keith.busch@...el.com>,
Zhou Wang <wangzhou1@...ilicon.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
linux-arm-kernel@...ts.infradead.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, alex.umansky@...wei.com,
Eric.Wehage@...wei.com, Logan Gunthorpe <logang@...tatee.com>
Subject: Re: [RFC PATCH 2/2] PCI/portdrv Hisilicon PCIe transport layer Port
PMU driver.
On Tue, Dec 18, 2018 at 10:21:27AM +0000, Jonathan Cameron wrote:
> On Mon, 17 Dec 2018 12:19:15 -0600
> Bjorn Helgaas <helgaas@...nel.org> wrote:
> > Agreed. I could imagine a drivers/pci/pmu/ directory sort of like
> > drivers/pci/switch/.
>
> That might work. Mark, Will what do you think? As long as you and Bjorn
> agree I don't think it'll really matter which one is chosen.
>
> driver/pci/pmu/ or drivers/perf/pci ?
I have a slight preference for the latter since the perf interface for
PMU drivers is notoriously subtle and error-prone. Keeping PMU drivers
together can be helpful to spot emerging patterns and makes cross-driver
changes easier to co-ordinate.
However, I'll defer to Bjorn since it's only a minor preference. We'd
obviously loop in linux-pci + Bjorn on any new submissions.
Will
Powered by blists - more mailing lists