diff options
| author |  Chen Yu <yu.c.chen@intel.com>
| 2016-12-21 17:24:55 +0800 |
|---|---|---|
| committer |  Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| 2017-01-11 09:29:33 +0100 |
| commit | 8a18f4284ec94ec56189e7f14495359d3b892a52 (patch) | |
| tree | 209951c6bc4265097a8b79ec39d24d6bcffb8b6b /tools/testing/selftests/firmware | |
| parent | kref: prefer atomic_inc_not_zero to atomic_add_unless (diff) | |
| download | linux-8a18f4284ec94ec56189e7f14495359d3b892a52.tar.gz linux-8a18f4284ec94ec56189e7f14495359d3b892a52.tar.bz2 linux-8a18f4284ec94ec56189e7f14495359d3b892a52.zip | |
platform: Print the resource range if device failed to claim
Sometimes we have the following error message:
platform MSFT0101:00: failed to claim resource 1
acpi MSFT0101:00: platform device creation failed: -16
But there is not enough information to figure out which resource range
failed to claim.
Thus print the resource range at first-place thus /proc/iomem or
ioports should tell us who already claimed this resource, then
the driver bug or incorrect resource assignment which is running
into this conflict can be diagnosed:
platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
acpi MSFT0101:00: platform device creation failed: -16
Suggested-by: Len Brown <lenb@kernel.org>
Reported-by: Wendy Wang <wendy.wang@intel.com>
Signed-off-by: Chen Yu <yu.c.chen@intel.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/testing/selftests/firmware')
0 files changed, 0 insertions, 0 deletions