public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: marex@denx•de (Marek Vasut)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RFC] PCI: imx6: remove outbound io/mem ATU region mapping
Date: Wed, 4 Dec 2013 16:45:20 +0100	[thread overview]
Message-ID: <201312041645.21028.marex@denx.de> (raw)
In-Reply-To: <0E83723C55F66F43A6041464FE31119D47AB51@039-SN2MPN1-013.039d.mgd.msft.net>

On Wednesday, December 04, 2013 at 03:38:49 AM, Richard Zhu wrote:
[...]
> > > [Richard] One Pericom PI7C9X2G303EL pcie switch, and two pcie ep
> > > deivces(one is intel e1000e nic, the other is one xhci device) are
> > > tested on imx6q sabresd board.
> > 
> > How/what does have such pericom switch and can be attached to an MX6
> > sabresdp ? Where can I get it?
> 
> [Richard] You can apply the example from Pericom.

Which one? Please point me to a website or something here.

> > > Without removing outbound io/mem regions view map during the cfg0/1
> > > read/write cycle, both of these devices can't work well at my side.
> > > Works well after remove them during the cfg0/1 read/write cycles.
> > 
> > Understood. Given that the iATU programming works on other CPUs
> > (confirmed on st spear and ti dra7xx), we might have some issues with
> > the iATU on MX6 . Is there anything special about the iATU on the MX6 ?
> 
> [Richard] As I know that there is no anything special about the iATU on
> MX6. Let me to make a double check with IC team later.

Oh this would be absolutelly _amazing_ if you could do that. Thank you very 
much!
[...]
Best regards,
Marek Vasut

  reply	other threads:[~2013-12-04 15:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  4:55 [PATCH RFC] PCI: imx6: remove outbound io/mem ATU region mapping Tim Harvey
2013-10-23  5:04 ` Marek Vasut
2013-10-23  6:40 ` Pratyush Anand
2013-11-26 20:46   ` Marek Vasut
2013-11-27  3:50     ` Pratyush Anand
2013-11-27  7:42       ` Richard Zhu
2013-11-27  8:24       ` Marek Vasut
2013-11-27  8:36         ` Pratyush Anand
2013-11-27  8:45           ` Marek Vasut
2013-11-28  5:54           ` Jingoo Han
2013-11-29  2:21             ` Marek Vasut
2013-12-03  3:04               ` Richard Zhu
2013-12-03  9:19                 ` Marek Vasut
2013-12-04  2:38                   ` Richard Zhu
2013-12-04 15:45                     ` Marek Vasut [this message]
2013-12-05  0:46                       ` Richard Zhu
2013-11-25 23:09 ` Bjorn Helgaas
2013-11-26 20:47   ` Marek Vasut

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=201312041645.21028.marex@denx.de \
    --to=marex@denx$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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