From: Marek Vasut <marex@denx.de>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Tim Harvey'" <tharvey@gateworks.com>,
"'Pratyush Anand'" <pratyush.anand@st.com>,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
"'Bjorn Helgaas'" <bhelgaas@google.com>,
"'Frank Li'" <lznuaa@gmail.com>,
"'Harro Haan'" <hrhaan@gmail.com>,
"'Mohit KUMAR DCG'" <Mohit.KUMAR@st.com>,
"'Richard Zhu'" <r65037@freescale.com>,
"'Sascha Hauer'" <s.hauer@pengutronix.de>,
"'Sean Cross'" <xobs@kosagi.com>,
"'Shawn Guo'" <shawn.guo@linaro.org>,
"'Siva Reddy Kallam'" <siva.kallam@samsung.com>,
"'Srikanth T Shivanand'" <ts.srikanth@samsung.com>,
"'Troy Kisky'" <troy.kisky@boundarydevices.com>,
"'Yinghai Lu'" <yinghai@kernel.org>
Subject: Re: [PATCH 2/7] [RFC] PCI: imx6: remove outbound io/mem ATU region mapping
Date: Thu, 28 Nov 2013 18:56:10 +0100 [thread overview]
Message-ID: <201311281856.10139.marex@denx.de> (raw)
In-Reply-To: <006301ceebfd$8d4ba040$a7e2e0c0$%han@samsung.com>
Dear Jingoo Han,
> On Wednesday, November 27, 2013 5:44 PM, Marek Vasut wrote:
> > Wednesday, November 27, 2013 1:30 PM, Pratyush Anand wrote:
> > > On Wed, Nov 27, 2013 at 05:10:43AM +0800, Marek Vasut wrote:
> > > > From: Tim Harvey <tharvey@gateworks.com>
> > > >
> > > > The IMX6 iATU is used for address translation between the AXI bus
> > > > address space and PCI address space. This is used for type0 and
> > > > type1 config cycles but is not necessary for outbound io/mem
> > > > regions.
> > > >
> > > > This patch removes the calls that inappropriately re-configures the
> > > > ATU viewport for outbound memory and IO after config cycles and
> > > > removes them altogether as they are not necessary.
> > >
> > > Yes, they are not necessary for all the cases where translation is one
> > > to one. So so for sure all the platform till now introduced should
> > > work.
> > > But, what about a platform where memory translation is not one to one?
> > >
> > > Existing code should work with all sort of memory translation on a
> > > platform having atleast two viewports capable of programming any type
> > > of outbound transaction.
> >
> > Full ACK, that's why it's called RFC.
> >
> > > > This resolves issues with PCI devices behind switches and has been
> > > > tested with a Gige device behind a PLX PEX860x switch. More testing
> > > > is needed for other configurations.
> > >
> > > I do not understand if MX6 has 4 Outbound Viewport then how this patch
> > > helps?
> > > -- PCI devices behind switches would not have been working because
> > > CFG1 transaction would not have been correct.
> > > -- It works with this patch. This patch changes viewport for CFG1 from
> > > 1 to 0.
> > > -- Can it be possible that MX6 has some restriction on viewport
> > > programming capability. I mean,like only viewport0 can be programmed
> > > for CFG0/1?
> >
> > Tim ?
> >
> > Here is the MX6 datasheet [1], the section 48.3.9.1.1 and 48.3.9.1.2
> > describe the iATU configuration on MX6. My understanding from this
> > description is that the MX6 has 4 inbound and 4 outbound iATU regions.
> > Am I wrong ?
>
> The numbers of inbound and outbound are hardware-configurable features.
> Thus, these numbers can be confirmed by Freescale hardware engineers.
> How about asking Freescale hardware engineers, if possible?
Richard is on the CC. Richard, can you please confirm those?
Thanks!
> Best regards,
> Jingoo Han
>
> > [1] http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf
> >
> > > Otherwise I do not find any convincing reason that why this patch
> > > helps in resolving issues with PCI devices behind switches.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] [RFC] PCI: imx6: remove outbound io/mem ATU region mapping
Date: Thu, 28 Nov 2013 18:56:10 +0100 [thread overview]
Message-ID: <201311281856.10139.marex@denx.de> (raw)
In-Reply-To: <006301ceebfd$8d4ba040$a7e2e0c0$%han@samsung.com>
Dear Jingoo Han,
> On Wednesday, November 27, 2013 5:44 PM, Marek Vasut wrote:
> > Wednesday, November 27, 2013 1:30 PM, Pratyush Anand wrote:
> > > On Wed, Nov 27, 2013 at 05:10:43AM +0800, Marek Vasut wrote:
> > > > From: Tim Harvey <tharvey@gateworks.com>
> > > >
> > > > The IMX6 iATU is used for address translation between the AXI bus
> > > > address space and PCI address space. This is used for type0 and
> > > > type1 config cycles but is not necessary for outbound io/mem
> > > > regions.
> > > >
> > > > This patch removes the calls that inappropriately re-configures the
> > > > ATU viewport for outbound memory and IO after config cycles and
> > > > removes them altogether as they are not necessary.
> > >
> > > Yes, they are not necessary for all the cases where translation is one
> > > to one. So so for sure all the platform till now introduced should
> > > work.
> > > But, what about a platform where memory translation is not one to one?
> > >
> > > Existing code should work with all sort of memory translation on a
> > > platform having atleast two viewports capable of programming any type
> > > of outbound transaction.
> >
> > Full ACK, that's why it's called RFC.
> >
> > > > This resolves issues with PCI devices behind switches and has been
> > > > tested with a Gige device behind a PLX PEX860x switch. More testing
> > > > is needed for other configurations.
> > >
> > > I do not understand if MX6 has 4 Outbound Viewport then how this patch
> > > helps?
> > > -- PCI devices behind switches would not have been working because
> > > CFG1 transaction would not have been correct.
> > > -- It works with this patch. This patch changes viewport for CFG1 from
> > > 1 to 0.
> > > -- Can it be possible that MX6 has some restriction on viewport
> > > programming capability. I mean,like only viewport0 can be programmed
> > > for CFG0/1?
> >
> > Tim ?
> >
> > Here is the MX6 datasheet [1], the section 48.3.9.1.1 and 48.3.9.1.2
> > describe the iATU configuration on MX6. My understanding from this
> > description is that the MX6 has 4 inbound and 4 outbound iATU regions.
> > Am I wrong ?
>
> The numbers of inbound and outbound are hardware-configurable features.
> Thus, these numbers can be confirmed by Freescale hardware engineers.
> How about asking Freescale hardware engineers, if possible?
Richard is on the CC. Richard, can you please confirm those?
Thanks!
> Best regards,
> Jingoo Han
>
> > [1] http://cache.freescale.com/files/32bit/doc/ref_manual/IMX6DQRM.pdf
> >
> > > Otherwise I do not find any convincing reason that why this patch
> > > helps in resolving issues with PCI devices behind switches.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-11-28 17:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 21:10 [PATCH 1/7] PCI: imx6: Make reset-gpio optional Marek Vasut
2013-11-26 21:10 ` Marek Vasut
2013-11-26 21:10 ` [PATCH 2/7] [RFC] PCI: imx6: remove outbound io/mem ATU region mapping Marek Vasut
2013-11-26 21:10 ` Marek Vasut
2013-11-27 4:30 ` Pratyush Anand
2013-11-27 4:30 ` Pratyush Anand
2013-11-27 8:44 ` Marek Vasut
2013-11-27 8:44 ` Marek Vasut
2013-11-28 5:49 ` Jingoo Han
2013-11-28 5:49 ` Jingoo Han
2013-11-28 17:56 ` Marek Vasut [this message]
2013-11-28 17:56 ` Marek Vasut
2013-12-04 5:49 ` Richard Zhu
2013-12-04 5:49 ` Richard Zhu
2013-12-04 7:52 ` Marek Vasut
2013-12-04 7:52 ` Marek Vasut
2013-12-05 0:44 ` Richard Zhu
2013-12-05 0:44 ` Richard Zhu
2013-12-05 1:05 ` Richard Zhu
2013-12-05 1:05 ` Richard Zhu
2013-12-05 1:59 ` Marek Vasut
2013-12-05 1:59 ` Marek Vasut
2013-12-03 20:14 ` Tim Harvey
2013-12-03 20:14 ` Tim Harvey
2013-12-04 10:33 ` Pratyush Anand
2013-12-04 10:33 ` Pratyush Anand
2013-12-04 18:51 ` Tim Harvey
2013-12-04 18:51 ` Tim Harvey
2013-12-04 22:01 ` Marek Vasut
2013-12-04 22:01 ` Marek Vasut
2013-11-26 21:10 ` [PATCH 3/7] PCI: imx6: Fix waiting for link up Marek Vasut
2013-11-26 21:10 ` Marek Vasut
2013-11-26 21:10 ` [PATCH 4/7] PCI: imx6: Split away the PHY reset Marek Vasut
2013-11-26 21:10 ` Marek Vasut
2013-11-27 16:23 ` Harro Haan
2013-11-27 16:23 ` Harro Haan
2013-12-02 23:36 ` Marek Vasut
2013-12-02 23:36 ` Marek Vasut
2013-11-26 21:10 ` [PATCH 5/7] PCI: imx6: Split away the link up wait loop Marek Vasut
2013-11-26 21:10 ` Marek Vasut
2013-11-26 21:10 ` [PATCH 6/7] PCI: imx6: Fix link start operation Marek Vasut
2013-11-26 21:10 ` Marek Vasut
2013-11-26 21:25 ` Marek Vasut
2013-11-26 21:25 ` Marek Vasut
2013-11-26 21:10 ` [PATCH 7/7] ARM: dts: imx6q-sabrelite: Enable PCI express Marek Vasut
2013-11-26 21:10 ` 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=201311281856.10139.marex@denx.de \
--to=marex@denx.de \
--cc=Mohit.KUMAR@st.com \
--cc=bhelgaas@google.com \
--cc=hrhaan@gmail.com \
--cc=jg1.han@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=pratyush.anand@st.com \
--cc=r65037@freescale.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=siva.kallam@samsung.com \
--cc=tharvey@gateworks.com \
--cc=troy.kisky@boundarydevices.com \
--cc=ts.srikanth@samsung.com \
--cc=xobs@kosagi.com \
--cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.