[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZzN4pO0lJDTSySaz@wunner.de>
Date: Tue, 12 Nov 2024 16:47:48 +0100
From: Lukas Wunner <lukas@...ner.de>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: linux-pci@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Rob Herring <robh@...nel.org>, Krzysztof Wilczy??ski <kw@...ux.com>,
"Maciej W . Rozycki" <macro@...am.me.uk>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Alexandru Gagniuc <mr.nuke.me@...il.com>,
Krishna chaitanya chundru <quic_krichai@...cinc.com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
"Rafael J . Wysocki" <rafael@...nel.org>, linux-pm@...r.kernel.org,
Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
linux-kernel@...r.kernel.org,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Amit Kucheria <amitk@...nel.org>, Zhang Rui <rui.zhang@...el.com>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>
Subject: Re: [PATCH v9 7/9] PCI/bwctrl: Add API to set PCIe Link Speed
On Fri, Oct 18, 2024 at 05:47:53PM +0300, Ilpo Järvinen wrote:
> +EXPORT_SYMBOL_GPL(pcie_set_target_speed);
My apologies for another belated comment on this series.
This patch is now a688ab21eb72 on pci/bwctrl:
I note that pcie_set_target_speed() is not called my a modular user
(CONFIG_PCIE_THERMAL is bool, not tristate), so the above-quoted export
isn't really necessary right now. I don't know if it was added
intentionally because some modular user is expected to show up
in the near future.
> @@ -135,6 +296,7 @@ static int pcie_bwnotif_probe(struct pcie_device *srv)
> if (!data)
> return -ENOMEM;
>
> + devm_mutex_init(&srv->device, &data->set_speed_mutex);
> ret = devm_request_threaded_irq(&srv->device, srv->irq, NULL,
> pcie_bwnotif_irq_thread,
> IRQF_SHARED | IRQF_ONESHOT,
We generally try to avoid devm_*() functions in port service drivers
because if we later on move them into the PCI core (which is the plan),
we'll have to unroll them. Not the end of the world that they're used
here, just not ideal.
Thanks,
Lukas
Powered by blists - more mailing lists