Bug 11241 - ACPID shouldn't depend on BR2_x86_64 || BR2_i386
Summary: ACPID shouldn't depend on BR2_x86_64 || BR2_i386
Status: RESOLVED FIXED
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-17 17:59 UTC by happycorsair
Modified: 2018-08-29 20:07 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description happycorsair 2018-08-17 17:59:48 UTC 
Nowadays multiple ARM-based devboards provide ACPI, so this restriction is not a good option anymore. For example I've used standard Buildroot acpi package on Cubieboard 6 without any issue.
Comment 1 Peter Korsgaard 2018-08-18 08:08:06 UTC 
Sorry, what firmware provides ACPI on your cubieboard? Or do you just mean that some of the functionality of acpid is usable without firmware/kernel support? drivers/acpi in the Linux kernel is guarded by ARCH_SUPPORTS_ACPI, which is selected for arm64/ia64/x86.

With that said, if it builds on other architectures and there are use cases for it on those, then I don't have a problem exposing it.
Comment 2 happycorsair 2018-08-18 08:54:29 UTC 
Hi, Peter!

I'm not a specialist in ACPI or power management, so please don't blame me a lot :)

It seems to me, that you are right. All ACPI-related options in Cubieboard 6 kernel config are disabled (it's ARM, not ARM64). But at the same time, acpid handles power button pushes and powers off the board. If no acpid is running, I can only reboot the board by long push.

So, it's useful. I found no building issues.