[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169651070763.1133315.8714234562874350620.b4-ty@kernel.org>
Date: Mon, 9 Oct 2023 17:56:42 +0100
From: Will Deacon <will@...nel.org>
To: robin.murphy@....com, catalin.marinas@....com,
suzuki.poulose@....com, ilkka@...amperecomputing.com,
Besar Wicaksono <bwicaksono@...dia.com>, mark.rutland@....com
Cc: kernel-team@...roid.com, Will Deacon <will@...nel.org>,
jonathanh@...dia.com, rwiley@...dia.com,
linux-arm-kernel@...ts.infradead.org, efunsten@...dia.com,
linux-kernel@...r.kernel.org, treding@...dia.com,
linux-tegra@...r.kernel.org, vsethi@...dia.com
Subject: Re: [PATCH v6] perf: arm_cspmu: Separate Arm and vendor module
On Mon, 21 Aug 2023 18:16:08 -0500, Besar Wicaksono wrote:
> Arm Coresight PMU driver consists of main standard code and
> vendor backend code. Both are currently built as a single module.
> This patch adds vendor registration API to separate the two to
> keep things modular. The main driver requests each known backend
> module during initialization and defer device binding process.
> The backend module then registers an init callback to the main
> driver and continue the device driver binding process.
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] perf: arm_cspmu: Separate Arm and vendor module
https://git.kernel.org/will/c/bfc653aa89cb
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
Powered by blists - more mailing lists