On 1/14/2016 10:29 AM, Mark Salter wrote: On Wed, 2016-01-13 at 14:20 +0100, Tomasz Nowicki wrote: > IO resources on Mustang get disabled unless I do: > > @@ -126,9 +126,10 @@ static void acpi_dev_ioresource_flags(struct > resource *res, u64 len, if (!acpi_dev_resource_len_valid(res->start, > res->end, len, true)) res->flags |= IORESOURCE_DISABLED | > IORESOURCE_UNSET; > > +#if 0 if (res->end >= 0x10003) res->flags |= IORESOURCE_DISABLED | > IORESOURCE_UNSET; - +#endif > > res->end is way beyond 0x10003 on Mustang: > > pci_bus 0000:00: root bus resource [io 0x0000-0xffff window] (bus > address [0x10000000-0x1000ffff]) > > Join the club. I complained about this and I got the message that we just do what Intel does. See Arnd Bergmann's reply. [PATCH V2 00/23] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI 1/12/2016 9:30 AM It is an artificial limit coming from the x86 world introduced into common code. > -- To unsubscribe from this list: send the line "unsubscribe > linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More > majordomo info at http://vger.kernel.org/majordomo-info.html > -- Sinan Kaya Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
