From: pratyush <pratyush.anand@st.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "rdunlap@xenotime.net" <rdunlap@xenotime.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"gregkh@suse.de" <gregkh@suse.de>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>,
Viresh KUMAR <viresh.kumar@st.com>,
Shiraz HASHIM <shiraz.hashim@st.com>
Subject: Re: [PATCH V5 Resend] ST SPEAr: PCIE gadget suppport
Date: Thu, 3 Mar 2011 10:30:15 +0530 [thread overview]
Message-ID: <4D6F205F.5080209@st.com> (raw)
In-Reply-To: <20110223160632.0b21c550.akpm@linux-foundation.org>
On 2/24/2011 5:36 AM, Andrew Morton wrote:
> On Mon, 21 Feb 2011 13:50:55 +0530
> Pratyush Anand <pratyush.anand@st.com> wrote:
>
>> This is a configurable gadget. can be configured by configfs interface. Any
>> IP available at PCIE bus can be programmed to be used by host
>> controller.It supoorts both INTX and MSI.
>> By default, gadget is configured for INTX and SYSRAM1 is mapped to BAR0
>> with size 0x1000
>>
>> Changes since V4:
>> - All documentation related comments incorporated
>>
>> Changes since V3:
>> - support for multiple instances of such device
>
> ^^ This doesn't seem to agree with the documentation.
>
Will add a line in documentation for it.
>> ...
>>
>> --- /dev/null
>> +++ b/Documentation/ABI/testing/configfs-spear-pcie-gadget
>> @@ -0,0 +1,30 @@
>> +What: /config/pcie-gadget
>> +Date: Feb 2011
>> +KernelVersion: 2.6.37
>> +Contact: Pratyush Anand <pratyush.anand@st.com>
>> +Description:
>> +
>> + Interface is used to configure selected dual mode PCIe controller
>> + as device and then program its various registers to configure it
>> + as a particular device type.
>> + This interfaces can be used to show spear's PCIe device capability.
>> +
>> + Nodes are only visible when configfs is mounted. To mount configfs
>> + in /config directory use:
>> + # mount -t configfs none /config/
>> +
>> + /config/pcie-gadget/
>> + link ... used to enable ltssm and read its status.
>> + int_type ...used to configure and read type of supported
>> + interrupt
>> + no_of_msi ... used to configure number of MSI vector needed and
>> + to read no of MSI granted.
>> + inta ... write 1 to assert INTA and 0 to de-assert.
>> + send_msi ... write MSI vector to be sent.
>> + vendor_id ... used to write and read vendor id (hex)
>> + device_id ... used to write and read device id (hex)
>> + bar0_size ... used to write and read bar0_size
>> + bar0_address ... used to write and read bar0 mapped area in hex.
>> + bar0_rw_offset ... used to write and read offset of bar0 where
>> + bar0_data will be written or read.
>> + bar0_data ... used to write and read data at bar0_rw_offset.
>
> What's the configfs naming scheme for the second and later devices?
>
there would be pcie-gadget.n directory under /config for
nth PCIe Device Controller.
Regards
Pratyush
>
> .
>
prev parent reply other threads:[~2011-03-03 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 8:20 [PATCH V5 Resend] ST SPEAr: PCIE gadget suppport Pratyush Anand
2011-02-24 0:06 ` Andrew Morton
2011-03-03 5:00 ` pratyush [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=4D6F205F.5080209@st.com \
--to=pratyush.anand@st.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=shiraz.hashim@st.com \
--cc=viresh.kumar@st.com \
/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