From: pratyush.anand@st.com (pratyush)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ST SPEAr: PCIE gadget suppport
Date: Fri, 7 Jan 2011 14:27:01 +0530 [thread overview]
Message-ID: <4D26D55D.4010600@st.com> (raw)
In-Reply-To: <20110106184840.GA21672@kroah.com>
On 1/7/2011 12:18 AM, Greg KH wrote:
> On Thu, Jan 06, 2011 at 05:29:10PM +0530, Viresh Kumar wrote:
>> From: Pratyush Anand <pratyush.anand@st.com>
>>
>> This is a configurable gadget. can be configured by sysfs 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 V1:
>> - __iomem added for register addresses
>> - kerneldoc comment removed whereever not required.
>> - help node moved from sysfs to documentation/misc-devices
>> - strict_strtoul used instead of sscanf
>>
>> Signed-off-by: Pratyush Anand <pratyush.anand@st.com>
>> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
>> ---
>> Documentation/misc-devices/spear-pcie-gadget.txt | 125 ++++
>
> New sysfs entries require updates to the Documentation/ABI/ directory
> for them.
>
> Please rework the patch to include these entries.
>
Ok..will send [Patch V3] with these modifications.
But, are these rework needed if I move this interface to configfs
as you have suggested below.
Or is there some different directory where documentation for configfs
node can be mentioned?
>> +read behaviour of nodes:
>> +------------------------------
>> +link :gives ltssm status.
>> +int_type :type of supported interrupt
>> +no_of_msi read :zero if MSI is not enabled by host.A positive value is the
>> + number of MSI vector granted.
>> +vendor_id :returns programmed vendor id (hex)
>> +device_id :returns programmed device id(hex)
>> +bar0_size: :retruns size of bar0 in hex.
>> +bar0_address :returns address of bar0 mapped area in hex.
>> +bar0_rw_offset :returns offset of bar0 for which bar0_data will return value.
>> +bar0_data :returns data at bar0_rw_offset.
>> +
>> +write behaviour of nodes:
>> +------------------------------
>> +link :write UP to enable ltsmm DOWN to disable
>> +int_type :write interrupt type to be configured and (int_type could be
>> + INTA, MSI or NO_INT).select MSI only when you have programmed
>> + no_of_msi node.
>> +no_of_msi :number of MSI vector needed.
>> +inta :write 1 to assert INTA and 0 to de-assert.
>> +send_msi :write MSI vector to be send.
>> +vendor_id :write vendor id(hex) to be programmed.
>> +device_id :write device id(hex) to be programmed.
>> +bar0_size :write size of bar0 in hex. default bar0 size is 1000 (hex)
>> + bytes.
>> +bar0_address :write address of bar0 mapped area in hex. (default mapping of
>> + bar0 is SYSRAM1(E0800000).Aalways program bar size before bar
>> + address. kernel might modify bar size and address to align. So
>> + read back bar size and address after writing to cross check.
>> +bar0_rw_offset :write offset of bar0 for which bar0_data will write value.
>> +bar0_data :write data to be written at bar0_rw_offset.
>
> Should you use configfs for this instead of sysfs? It looks like that
> is what you are looking for here.
>
configfs seems better option. Will do that in V3.
Regards
Pratyush
> thanks,
>
> greg k-h
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: pratyush <pratyush.anand@st.com>
To: Greg KH <greg@kroah.com>
Cc: Viresh KUMAR <viresh.kumar@st.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"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>
Subject: Re: [PATCH V2] ST SPEAr: PCIE gadget suppport
Date: Fri, 7 Jan 2011 14:27:01 +0530 [thread overview]
Message-ID: <4D26D55D.4010600@st.com> (raw)
In-Reply-To: <20110106184840.GA21672@kroah.com>
On 1/7/2011 12:18 AM, Greg KH wrote:
> On Thu, Jan 06, 2011 at 05:29:10PM +0530, Viresh Kumar wrote:
>> From: Pratyush Anand <pratyush.anand@st.com>
>>
>> This is a configurable gadget. can be configured by sysfs 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 V1:
>> - __iomem added for register addresses
>> - kerneldoc comment removed whereever not required.
>> - help node moved from sysfs to documentation/misc-devices
>> - strict_strtoul used instead of sscanf
>>
>> Signed-off-by: Pratyush Anand <pratyush.anand@st.com>
>> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
>> ---
>> Documentation/misc-devices/spear-pcie-gadget.txt | 125 ++++
>
> New sysfs entries require updates to the Documentation/ABI/ directory
> for them.
>
> Please rework the patch to include these entries.
>
Ok..will send [Patch V3] with these modifications.
But, are these rework needed if I move this interface to configfs
as you have suggested below.
Or is there some different directory where documentation for configfs
node can be mentioned?
>> +read behaviour of nodes:
>> +------------------------------
>> +link :gives ltssm status.
>> +int_type :type of supported interrupt
>> +no_of_msi read :zero if MSI is not enabled by host.A positive value is the
>> + number of MSI vector granted.
>> +vendor_id :returns programmed vendor id (hex)
>> +device_id :returns programmed device id(hex)
>> +bar0_size: :retruns size of bar0 in hex.
>> +bar0_address :returns address of bar0 mapped area in hex.
>> +bar0_rw_offset :returns offset of bar0 for which bar0_data will return value.
>> +bar0_data :returns data at bar0_rw_offset.
>> +
>> +write behaviour of nodes:
>> +------------------------------
>> +link :write UP to enable ltsmm DOWN to disable
>> +int_type :write interrupt type to be configured and (int_type could be
>> + INTA, MSI or NO_INT).select MSI only when you have programmed
>> + no_of_msi node.
>> +no_of_msi :number of MSI vector needed.
>> +inta :write 1 to assert INTA and 0 to de-assert.
>> +send_msi :write MSI vector to be send.
>> +vendor_id :write vendor id(hex) to be programmed.
>> +device_id :write device id(hex) to be programmed.
>> +bar0_size :write size of bar0 in hex. default bar0 size is 1000 (hex)
>> + bytes.
>> +bar0_address :write address of bar0 mapped area in hex. (default mapping of
>> + bar0 is SYSRAM1(E0800000).Aalways program bar size before bar
>> + address. kernel might modify bar size and address to align. So
>> + read back bar size and address after writing to cross check.
>> +bar0_rw_offset :write offset of bar0 for which bar0_data will write value.
>> +bar0_data :write data to be written at bar0_rw_offset.
>
> Should you use configfs for this instead of sysfs? It looks like that
> is what you are looking for here.
>
configfs seems better option. Will do that in V3.
Regards
Pratyush
> thanks,
>
> greg k-h
> .
>
next prev parent reply other threads:[~2011-01-07 8:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 11:59 [PATCH V2] ST SPEAr: PCIE gadget suppport Viresh Kumar
2011-01-06 11:59 ` Viresh Kumar
2011-01-06 18:48 ` Greg KH
2011-01-06 18:48 ` Greg KH
2011-01-07 8:57 ` pratyush [this message]
2011-01-07 8:57 ` pratyush
2011-01-07 18:32 ` Greg KH
2011-01-07 18:32 ` Greg KH
2011-01-06 20:18 ` Andrew Morton
2011-01-06 20:18 ` Andrew Morton
2011-01-07 8:54 ` pratyush
2011-01-07 8:54 ` pratyush
2011-01-07 22:32 ` Arnd Bergmann
2011-01-07 22:32 ` Arnd Bergmann
2011-01-10 11:20 ` pratyush
2011-01-10 11:20 ` pratyush
2011-01-18 14:51 ` Arnd Bergmann
2011-01-18 14:51 ` 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=4D26D55D.4010600@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 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.