On May 29, 2014, at 1:38 AM, Kishon Vijay Abraham I <kis...@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 <jguntho...@obsidianresearch.com> > Cc: Bjorn Helgaas <bhelg...@google.com> > Cc: Mohit Kumar <mohit.ku...@st.com> > Cc: Jingoo Han <jg1....@samsung.com> > Cc: Marek Vasut <ma...@denx.de> > Cc: Arnd Bergmann <a...@arndb.de> > Signed-off-by: Kishon Vijay Abraham I <kis...@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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
