[PATCH v2 03/18] PCI: designware: Configuration space should be specified in 'reg'

Kumar Gala galak at codeaurora.org
Thu May 29 08:03:54 PDT 2014


On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I <kishon at ti.com> wrote:

> The configuration address space has so far been specified in *ranges*,
> however it should be specified in *reg* making it a platform MEM resource.
> Hence used 'platform_get_resource_*' API to get configuration address
> space in the designware driver.
> 
> Cc: Jason Gunthorpe <jgunthorpe at obsidianresearch.com>
> Cc: Bjorn Helgaas <bhelgaas at google.com>
> Cc: Mohit Kumar <mohit.kumar at st.com>
> Cc: Jingoo Han <jg1.han at samsung.com>
> Cc: Marek Vasut <marex at denx.de>
> Cc: Arnd Bergmann <arnd at arndb.de>
> Signed-off-by: Kishon Vijay Abraham I <kishon at ti.com>
> ---
> .../devicetree/bindings/pci/designware-pcie.txt    |    1 +
> drivers/pci/host/pcie-designware.c                 |   17 +++++++++++++++--
> 2 files changed, 16 insertions(+), 2 deletions(-)

Why should the cfg space be defined in *reg* instead of ranges?

- k

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation




More information about the linux-arm-kernel mailing list