sparc64: Do not ignore 'pmu' device ranges.
I must have disabled this due to other bugs which were fixed over time. And this is needed in order for child devices of "pmu" to get proper resource values. Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
0eb78f0b1a
commit
dc8ca2a111
1 changed files with 0 additions and 6 deletions
|
@ -412,12 +412,6 @@ static int __init build_one_resource(struct device_node *parent,
|
|||
|
||||
static int __init use_1to1_mapping(struct device_node *pp)
|
||||
{
|
||||
/* If this is on the PMU bus, don't try to translate it even
|
||||
* if a ranges property exists.
|
||||
*/
|
||||
if (!strcmp(pp->name, "pmu"))
|
||||
return 1;
|
||||
|
||||
/* If we have a ranges property in the parent, use it. */
|
||||
if (of_find_property(pp, "ranges", NULL) != NULL)
|
||||
return 0;
|
||||
|
|
Loading…
Reference in a new issue