[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <563B6C52.8020204@codeaurora.org>
Date: Thu, 5 Nov 2015 09:48:50 -0500
From: Sinan Kaya <okaya@...eaurora.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: rjw@...ysocki.net, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org,
will.deacon@....com, ddaney@...iumnetworks.com,
Narinder.Dhillon@...iumnetworks.com, linaro-acpi@...ts.linaro.org,
wangyijing@...wei.com, robert.richter@...iumnetworks.com,
tglx@...utronix.de, catalin.marinas@....com, bhelgaas@...gle.com,
Liviu.Dudau@....com, jiang.liu@...ux.intel.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [Linaro-acpi] [PATCH V1 11/11] arm64, pci, acpi: Support for ACPI
based PCI hostbridge init
On 11/3/2015 12:43 PM, Sinan Kaya wrote:
> In any case, the hardware document says 32 bit configuration space
> access to the host bridge only. I'll get more clarification.
>
I got confirmation this morning that this chip supports 32 bit access to
the root complex configuration space. 8/16/32 bits accesses to the
endpoints are supported.
>>
>> You can probably work around this by using the legacy I/O port method
>> rather than ECAM, if the PCI host bridge itself is functional and just
>> the host bus it is connected to is buggy.
>
> From the sounds of it, we'll need a quirk for config space. We support
> legacy I/O only to make the endpoints happy. Some endpoints do not get
> initialized if they don't have a BAR address assigned to all the BAR
> resources.
We'll need an MCFG fix up.
--
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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists