From: pratyush.anand@st.com (pratyush)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V7 02/17] SPEAr13xx: Add PCIe host controller base driver support.
Date: Wed, 13 Apr 2011 17:55:25 +0530 [thread overview]
Message-ID: <4DA59635.2020705@st.com> (raw)
In-Reply-To: <4DA47085.9090209@gmail.com>
Hello Rob,
...
>> SPEAr13xx family contains Synopsys designware PCIe version 3.30a. This
>> patch adds support for this PCIe module for spear platform.
>>
>
> Sorry for the late response.
>
> Other vendors are likely to have the same IP, but none of the code here
> is written to be common. In light of recent discussions this would be a
> good candidate to avoid future duplication.
>
> It doesn't appear that pcie.c contains much SPEAr specific code. The few
> defines and structs that are could be passed in. Some comments below.
>
Yes, this driver is for an PCIe host which uses Synopsys IP. But
SPEAr specific wrapper has been used heavily in the code.
Synopsis provides some signal which can be interfaced to registers
for CPU access. This interface can be different for different vendor.
All the application registers are SPEAr specific representation
and may not be same for other vendor.
So all accesses for app_reg in the code may not be similar in other
implementation.
...
>> +struct pcie_port {
>
> 3 other structs with the same name and similar fields already exist:
>
> arch/arm/mach-kirkwood/pcie.c:27:struct pcie_port {
> arch/arm/mach-dove/pcie.c:23:struct pcie_port {
> arch/arm/mach-mv78xx0/pcie.c:19:struct pcie_port {
>
>> + u8 port;
>> + u8 root_bus_nr;
>> + void __iomem *base;
>> + void __iomem *app_base;
>> + void __iomem *va_app_base;
>> + void __iomem *va_dbi_base;
like dbi interface. May not be needed in all implementation
of the same synposis IP.
>> + void __iomem *va_cfg0_base;
>> + void __iomem *va_cfg1_base;
>> + spinlock_t conf_lock;
>> + char mem_space_name[16];
>> + char io_space_name[16];
>> + struct resource res[2];
>> + struct pcie_port_info config;
>> +};
>> +
...
Regards
Pratyush
next prev parent reply other threads:[~2011-04-13 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1298977728.git.viresh.kumar@st.com>
2011-03-23 4:52 ` [PATCH V7 02/17] SPEAr13xx: Add PCIe host controller base driver support Viresh Kumar
2011-03-23 8:28 ` Arnd Bergmann
2011-04-11 12:26 ` pratyush
2011-04-11 15:22 ` Arnd Bergmann
2011-04-13 12:11 ` pratyush
2011-04-12 15:32 ` Rob Herring
2011-04-13 12:25 ` pratyush [this message]
2011-04-17 20:19 ` Arnd Bergmann
2011-04-27 6:52 ` Pratyush Anand
2011-04-27 9:03 ` Arnd Bergmann
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=4DA59635.2020705@st.com \
--to=pratyush.anand@st.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).