From: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
ravishankar.srivatsa@intel.com, chethan.tumkur.narayan@intel.com,
Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH v1] Bluetooth: btintel_pcie: Fix build error when CONFIG_ACPI is disabled
Date: Thu, 16 Apr 2026 11:33:51 +0530 [thread overview]
Message-ID: <20260416060352.1392139-1-chandrashekar.devegowda@intel.com> (raw)
btintel_pcie_acpi_reset_method() uses ACPI APIs such as
acpi_evaluate_object() and acpi_has_method() which are not available
when CONFIG_ACPI is disabled, causing build errors on architectures
like ppc64le that lack ACPI support.
Guard btintel_pcie_acpi_reset_method() with IS_ENABLED(CONFIG_ACPI)
and provide a stub returning -ENODEV when ACPI is not enabled.
Fixes: 912a499a7955 ("Bluetooth: btintel_pcie: Support Product level reset")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
---
drivers/bluetooth/btintel_pcie.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index 076beb45c410..4d136ff342b8 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -2280,6 +2280,7 @@ static void btintel_pcie_inc_recovery_count(struct pci_dev *pdev,
static int btintel_pcie_setup_hdev(struct btintel_pcie_data *data);
static void btintel_pcie_reset(struct hci_dev *hdev);
+#if IS_ENABLED(CONFIG_ACPI)
static int btintel_pcie_acpi_reset_method(struct btintel_pcie_data *data)
{
union acpi_object *obj, argv4;
@@ -2333,6 +2334,12 @@ static int btintel_pcie_acpi_reset_method(struct btintel_pcie_data *data)
pci_dev_unlock(data->pdev);
return ret;
}
+#else
+static int btintel_pcie_acpi_reset_method(struct btintel_pcie_data *data)
+{
+ return -ENODEV;
+}
+#endif
static void btintel_pcie_perform_pldr(struct btintel_pcie_data *data)
{
--
2.43.0
next reply other threads:[~2026-04-16 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 6:03 Chandrashekar Devegowda [this message]
2026-04-16 7:15 ` [v1] Bluetooth: btintel_pcie: Fix build error when CONFIG_ACPI is disabled bluez.test.bot
2026-04-16 8:02 ` [PATCH v1] " Paul Menzel
2026-04-16 10:06 ` Devegowda, Chandrashekar
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=20260416060352.1392139-1-chandrashekar.devegowda@intel.com \
--to=chandrashekar.devegowda@intel.com \
--cc=bhelgaas@google.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ravishankar.srivatsa@intel.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