From: Murali Karicheri <m-karicheri2@ti.com>
To: Mohit KUMAR DCG <Mohit.KUMAR@st.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Jingoo Han <jg1.han@samsung.com>
Subject: Re: pcie designware question
Date: Fri, 20 Dec 2013 11:20:29 -0500 [thread overview]
Message-ID: <52B46E4D.6020805@ti.com> (raw)
In-Reply-To: <2CC2A0A4A178534D93D5159BF3BCB66189F96BAC51@EAPEX1MAIL1.st.com>
On 12/19/2013 11:21 PM, Mohit KUMAR DCG wrote:
>>> I have reviewed the designware.c code and the glue logic driver
>>> pci-exynos.c and couldn't understand few things.
>>>
>>> 1. Our pcie ss is based on designware core and following addresses are
>>> not listed in our IP's data manual. Where is defined? It does show
>>> the rest of the offsets defined in drivers/pci/host/designware.c and
>>>
>>> #define PCIE_ATU_VIEWPORT 0x900
>>> #define PCIE_ATU_REGION_INBOUND (0x1 << 31)
>>> #define PCIE_ATU_REGION_OUTBOUND (0x0 << 31)
>>> #define PCIE_ATU_REGION_INDEX1 (0x1 << 0)
>>> #define PCIE_ATU_REGION_INDEX0 (0x0 << 0)
>>> #define PCIE_ATU_CR1 0x904
>>> #define PCIE_ATU_TYPE_MEM (0x0 << 0)
>>> #define PCIE_ATU_TYPE_IO (0x2 << 0)
>>> #define PCIE_ATU_TYPE_CFG0 (0x4 << 0)
>>> #define PCIE_ATU_TYPE_CFG1 (0x5 << 0)
>>> #define PCIE_ATU_CR2 0x908
>>> #define PCIE_ATU_ENABLE (0x1 << 31)
>>> #define PCIE_ATU_BAR_MODE_ENABLE (0x1 << 30)
>>> #define PCIE_ATU_LOWER_BASE 0x90C
>>> #define PCIE_ATU_UPPER_BASE 0x910
>>> #define PCIE_ATU_LIMIT 0x914
>>> #define PCIE_ATU_LOWER_TARGET 0x918
>>> #define PCIE_ATU_BUS(x) (((x) & 0xff) << 24)
>>> #define PCIE_ATU_DEV(x) (((x) & 0x1f) << 19)
>>> #define PCIE_ATU_FUNC(x) (((x) & 0x7) << 16)
>>> #define PCIE_ATU_UPPER_TARGET 0x91C
> - These are Synopsys specific port logic registers. You can find these registers at offset 0x200
> under port logic registers section in Synpsys PCIe DM. There can be minor difference in the name
> convention as it is called 'iATU Viewport Register' in controller version3.70 and 'iATU Index Register'
> in version 4.11.
> By the way which version of IP manual you are referring?
>
>
Mohit,
I have checked with our hardware team and they confirmed that ATU
registers are not implemented in our PCIE
SS. So we need to have a way to disable this in the core driver so
that we can handle it in our glue layer driver.
But this will be a regression on the existing driver. How do we handle this?
Murali
next prev parent reply other threads:[~2013-12-20 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 22:01 pcie designware question Karicheri, Muralidharan
2013-12-19 22:57 ` Bjorn Helgaas
2013-12-19 23:38 ` Karicheri, Muralidharan
2013-12-20 4:21 ` Mohit KUMAR DCG
2013-12-20 15:42 ` Murali Karicheri
2013-12-20 16:20 ` Murali Karicheri [this message]
2014-01-08 6:55 ` Pratyush Anand
2014-01-08 15:48 ` Karicheri, Muralidharan
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=52B46E4D.6020805@ti.com \
--to=m-karicheri2@ti.com \
--cc=Mohit.KUMAR@st.com \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=linux-pci@vger.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 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).