[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230307023656.cyntxctzqgpam5u3@offworld>
Date: Mon, 6 Mar 2023 18:36:56 -0800
From: Davidlohr Bueso <dave@...olabs.net>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>
Cc: linux-cxl@...r.kernel.org, peterz@...radead.org, mingo@...hat.com,
acme@...nel.org, mark.rutland@....com, will@...nel.org,
dan.j.williams@...el.com, bwidawsk@...nel.org, ira.weiny@...el.com,
vishal.l.verma@...el.com, alison.schofield@...el.com,
linuxarm@...wei.com, linux-perf-users@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/4] cxl/pci: Find and register CXL PMU devices
On Fri, 03 Mar 2023, Jonathan Cameron wrote:
>+int devm_cxl_cpmu_add(struct device *parent, struct cxl_cpmu_regs *regs, int index)
>+{
>+ struct cxl_cpmu *cpmu;
>+ struct device *dev;
>+ int rc;
>+
>+ cpmu = kzalloc(sizeof(*cpmu), GFP_KERNEL);
>+ if (!cpmu)
>+ return -ENOMEM;
>+
>+ cpmu->base = regs->cpmu;
>+ dev = &cpmu->dev;
>+ device_initialize(dev);
>+ device_set_pm_not_required(dev);
>+ dev->parent = parent;
>+ dev->bus = &cxl_bus_type;
>+ dev->type = &cxl_cpmu_type;
>+ rc = ida_alloc(&cpmu_ida, GFP_KERNEL);
>+ if (rc < 0)
>+ goto err;
Probably better to do the ida_alloc after the cpmu allocation above, before
arming the dev.
Powered by blists - more mailing lists