From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: imx6: fix imprecise abort handler
Date: Fri, 1 Nov 2013 13:18:44 +0100 [thread overview]
Message-ID: <201311011318.44453.marex@denx.de> (raw)
In-Reply-To: <0E83723C55F66F43A6041464FE31119D418299@039-SN2MPN1-011.039d.mgd.msft.net>
Hi Richard,
[...]
> > > I'm sort of dubious about imx6q_pcie_abort_handler() to begin with --
> > > it seems like it assumes that imprecise aborts are either enabled or
> > > disabled. Isn't there some way it can *check* whether that's the
> > > case, so it won't break if those aborts are enabled at a different
> > > point in the future?
> >
> > The best way here would be to find a way to prevent the DWC controller
> > from generating data abort on missing device _at_all_ and just make the
> > read from that portion of config space be 0xffffffff or zeroes . I
> > didn't find any configuration bit that would be able to do it though :(
> > Richard, can you maybe check with FSL if such an option exists on the
> > controller?
>
> [Richard] Unfortunately, discussed with IC guys, there is no such kind of
> mechanism.
Do you know or can you please check if there's at least some mechanism to detect
whether the data abort was generated by the DWC PCIe or something else ?
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-11-01 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1382056042-7299-1-git-send-email-tharvey@gateworks.com>
2013-10-19 1:33 ` [PATCH] PCI: imx6: fix imprecise abort handler Marek Vasut
2013-10-21 0:56 ` Shawn Guo
[not found] ` <CAHM4w1nyXCuTya+TR7Rxiw0ojmwZHwz9iUmz=cG8z_8h2wKhSw@mail.gmail.com>
2013-10-29 19:46 ` Bjorn Helgaas
2013-10-30 14:55 ` Marek Vasut
2013-11-01 3:31 ` Richard Zhu
2013-11-01 12:18 ` Marek Vasut [this message]
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=201311011318.44453.marex@denx.de \
--to=marex@denx.de \
--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).