[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140515205210.GB14722@obsidianresearch.com>
Date: Thu, 15 May 2014 14:52:10 -0600
From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To: Murali Karicheri <m-karicheri2@...com>
Cc: Arnd Bergmann <arnd@...db.de>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"Strashko, Grygorii" <grygorii.strashko@...com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Jingoo Han <jg1.han@...sung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Shilimkar, Santosh" <santosh.shilimkar@...com>,
Mohit Kumar <mohit.kumar@...com>,
Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [PATCH v1 5/5] pci: keystone: add pcie driver based on
designware core driver
On Thu, May 15, 2014 at 04:04:47PM -0400, Murali Karicheri wrote:
> Jason What you mean by "The PCI core handles setting the maximum
> read request size already" I see there is function pcie_write_mrrs()
> in the drivers/pci/probe.c that reads the mps using pcie_get_mps()
> and then set mrrs to mps. But this function is called only from
> pcie_bus_configure_set() that is called by
> pcie_bus_configure_settings()
Right, that is the common code that correctly sets the MRRS that you
should be using instead of quirks.
> None of them gets called on ARM platform.
Hmm, a cursory glance tells me the same as well.
That seems to be the root problem here, ARM needs to do the PCIE
setup just as much as any other arch.
So, I would prefer to see you fix ARM common code to call
pcie_bus_configure_settings() properly, that seems very simple and is
obviously needed for any PCI-E host driver on ARM.
Thoughts? Arnd? Bjorn?
Jason
--
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