From: Bjorn Helgaas <helgaas@kernel.org>
To: webgeek1234@gmail.com, "Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v7 2/3] cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use
Date: Fri, 26 Sep 2025 16:25:19 -0500 [thread overview]
Message-ID: <20250926212519.GA2268653@bhelgaas> (raw)
In-Reply-To: <20250731-pci-tegra-module-v7-2-cad4b088b8fb@gmail.com>
[cc->to: Rafael, Daniel, any feedback or ack? Would like to resolve
this (part of Aaron's series at
https://lore.kernel.org/r/20250731-pci-tegra-module-v7-0-cad4b088b8fb@gmail.com)]
On Thu, Jul 31, 2025 at 04:59:25PM -0500, Aaron Kling via B4 Relay wrote:
> From: Aaron Kling <webgeek1234@gmail.com>
>
> Add export for tegra_cpuidle_pcie_irqs_in_use() so that drivers like
> pci-tegra can be loaded as a module.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> drivers/cpuidle/cpuidle-tegra.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpuidle/cpuidle-tegra.c b/drivers/cpuidle/cpuidle-tegra.c
> index b203a93deac5f378572be90e22c73e7417adb99e..aca907a62bb5de4ee4c71c1900eacedd4b90bc0a 100644
> --- a/drivers/cpuidle/cpuidle-tegra.c
> +++ b/drivers/cpuidle/cpuidle-tegra.c
> @@ -336,6 +336,7 @@ void tegra_cpuidle_pcie_irqs_in_use(void)
> pr_info("disabling CC6 state, since PCIe IRQs are in use\n");
> tegra_cpuidle_disable_state(TEGRA_CC6);
> }
> +EXPORT_SYMBOL_GPL(tegra_cpuidle_pcie_irqs_in_use);
tegra_cpuidle_pcie_irqs_in_use() looks like a workaround for a Tegra20
hardware defect, and having no knowledge of typical Tegra20 systems,
my questions would be "Why do we even bother with this? Should
cpuidle-tegra.c just disable CC6 always, unconditionally? The whole
thing, and all of include/soc/tegra/cpuidle.h, looks like it might be
more trouble than it's worth."
Bjorn
next prev parent reply other threads:[~2025-09-26 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 21:59 [PATCH v7 0/3] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-07-31 21:59 ` [PATCH v7 1/3] irqdomain: Export irq_domain_free_irqs Aaron Kling via B4 Relay
2025-07-31 21:59 ` [PATCH v7 2/3] cpuidle: tegra: Export tegra_cpuidle_pcie_irqs_in_use Aaron Kling via B4 Relay
2025-09-26 21:25 ` Bjorn Helgaas [this message]
2025-10-20 18:53 ` Aaron Kling
2025-12-09 4:38 ` Aaron Kling
2025-07-31 21:59 ` [PATCH v7 3/3] PCI: tegra: Allow building as a module Aaron Kling via B4 Relay
2025-07-31 22:01 ` [PATCH v7 0/3] " Aaron Kling
2025-08-01 6:00 ` Manivannan Sadhasivam
2025-08-18 18:39 ` Aaron Kling
2025-09-22 16:18 ` Aaron Kling
2025-12-09 18:40 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250926212519.GA2268653@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=webgeek1234@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox