From mboxrd@z Thu Jan  1 00:00:00 1970
From: tony@atomide.com (Tony Lindgren)
Date: Thu, 7 Jan 2016 13:59:47 -0800
Subject: dra7xx pci driver broken on dra7xx-evm
In-Reply-To: <568ED7FA.4000508@ti.com>
References: <20160106214518.GA6106@localhost.localdomain>
 <568DF4FE.5010704@ti.com> <568ED7FA.4000508@ti.com>
Message-ID: <20160107215946.GP12777@atomide.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

* Suman Anna <s-anna@ti.com> [160107 13:26]:
> On 01/06/2016 11:17 PM, Kishon Vijay Abraham I wrote:
> > Hi,
> 
> + Tero, Tony and linux-omap
> 
> > 
> > On Thursday 07 January 2016 03:15 AM, Richard Cochran wrote:
> >>
> >> The dra7xx-evm box freezes hard at the very first PCI bus access, the
> >> call to in dra7xx_pcie_readl() in dra7xx_pcie_probe().
> >>
> >> The out-of-tree 3.14.53 TI driver performs a reset via platform data,
> >> calling omap_device_assert_hardreset() by hook and crook.
> 
> Yeah, this is the only feasible way and not break multi-arch atm until a
> reset framework is in place. We have couple of drivers (omap_iommu and
> wkup_m3_rproc) following this approach.

Sounds like doing reset with platform data is the way to go until the
reset controller works.

Regards,

Tony