From: Kishon Vijay Abraham I <kishon@ti.com>
To: Tony Lindgren <tony@atomide.com>, Suman Anna <s-anna@ti.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
Tero Kristo <t-kristo@ti.com>, "Murphy, Dan" <dmurphy@ti.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: dra7xx pci driver broken on dra7xx-evm
Date: Fri, 8 Jan 2016 11:37:09 +0530 [thread overview]
Message-ID: <568F520D.9050807@ti.com> (raw)
In-Reply-To: <20160107215946.GP12777@atomide.com>
Hi,
On Friday 08 January 2016 03:29 AM, Tony Lindgren wrote:
> * 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.
All right. I'll post the patch to do reset using platform data.
Thanks
Kishon
next prev parent reply other threads:[~2016-01-08 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160106214518.GA6106@localhost.localdomain>
[not found] ` <568DF4FE.5010704@ti.com>
2016-01-07 21:26 ` dra7xx pci driver broken on dra7xx-evm Suman Anna
2016-01-07 21:59 ` Tony Lindgren
2016-01-08 6:07 ` Kishon Vijay Abraham I [this message]
2016-01-08 9:22 ` Richard Cochran
2016-01-11 8:58 ` Kishon Vijay Abraham I
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=568F520D.9050807@ti.com \
--to=kishon@ti.com \
--cc=bhelgaas@google.com \
--cc=dmurphy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).