linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: dra7xx pci driver broken on dra7xx-evm
Date: Thu, 7 Jan 2016 10:47:50 +0530	[thread overview]
Message-ID: <568DF4FE.5010704@ti.com> (raw)
In-Reply-To: <20160106214518.GA6106@localhost.localdomain>

Hi,

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.
> 
> Adding the reset into the mainline driver cures the freeze.
> 
> Question: How on earth is this driver supposed to work?

It doesn't work out of the box in mainline. (Every time I post a PCI patch, I
add the pdata-quirks mechanism to test it). The pdata-quirks mechanism used in
TI tree is not an upstream-able solution. Something like this [1] was done for
performing reset. Not sure the latest state of that. Dan? Suman?

Thanks
Kishon

[1] -> https://patches.linaro.org/33797/
> 
> Thanks,
> Richard
> 

  reply	other threads:[~2016-01-07  5:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 21:45 dra7xx pci driver broken on dra7xx-evm Richard Cochran
2016-01-07  5:17 ` Kishon Vijay Abraham I [this message]
2016-01-07  7:37   ` Richard Cochran
2016-01-07  8:11   ` [PATCH] arm: pci: mark the dra7xx driver as broken Richard Cochran
2016-01-07  8:44     ` Kishon Vijay Abraham I
2016-01-07  9:25       ` Richard Cochran
2016-01-07 14:42         ` Bjorn Helgaas
2016-01-08  6:55           ` Kishon Vijay Abraham I
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
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=568DF4FE.5010704@ti.com \
    --to=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).