Commit 2f3102c6 authored by Jean Delvare's avatar Jean Delvare Committed by Greg Kroah-Hartman

ACPI: Clarify resource conflict message

commit 14f03343 upstream.

The message "ACPI: Device needs an ACPI driver" is misleading. The
device _may_ need an ACPI driver, if the BIOS implemented a custom
API for the device in question (which, AFAIK, can't be checked.) If
not, then either a generic ACPI driver may be used (for example
"thermal"), or nothing can be done (other than a white list).

I propose to reword the message to:

ACPI: If an ACPI driver is available for this device, you should use
it instead of the native driver

which I think is more correct. Comments and suggestions welcome.

I also added a message warning about possible problems and system
instability when users pass acpi_enforce_resources=lax, as suggested
by Len.
Signed-off-by: default avatarJean Delvare <jdelvare@suse.de>
Cc: Thomas Renninger <trenn@suse.de>
Cc: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Signed-off-by: default avatarLen Brown <len.brown@intel.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent 3ee41bac
...@@ -1182,7 +1182,13 @@ int acpi_check_resource_conflict(struct resource *res) ...@@ -1182,7 +1182,13 @@ int acpi_check_resource_conflict(struct resource *res)
res_list_elem->name, res_list_elem->name,
(long long) res_list_elem->start, (long long) res_list_elem->start,
(long long) res_list_elem->end); (long long) res_list_elem->end);
printk(KERN_INFO "ACPI: Device needs an ACPI driver\n"); if (acpi_enforce_resources == ENFORCE_RESOURCES_LAX)
printk(KERN_NOTICE "ACPI: This conflict may"
" cause random problems and system"
" instability\n");
printk(KERN_INFO "ACPI: If an ACPI driver is available"
" for this device, you should use it instead of"
" the native driver\n");
} }
if (acpi_enforce_resources == ENFORCE_RESOURCES_STRICT) if (acpi_enforce_resources == ENFORCE_RESOURCES_STRICT)
return -EBUSY; return -EBUSY;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment