From: Alexandre Bounine <alexandre.bounine@idt.com>
To: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Micha Nelissen <micha.nelissen@Prodrive.nl>,
Andre van Herk <andre.van.herk@Prodrive.nl>,
Alexandre Bounine <alexandre.bounine@idt.com>
Subject: [PATCH v2 0/3] rapidio: changes to enumeration/discovery
Date: Tue, 30 Apr 2013 17:25:52 -0400 [thread overview]
Message-ID: <1367357155-11586-1-git-send-email-alexandre.bounine@idt.com> (raw)
Systems that use RapidIO fabric may need to implement their own enumeration
and discovery methods which are better suitable for needs of a target
application.
The following set of patches is intended to simplify process of introduction of
new RapidIO fabric enumeration/discovery methods.
The first patch offers ability to add new RapidIO enumeration/discovery methods
using kernel configuration options. This new configuration option mechanism
allows to select statically linked or modular enumeration/discovery method(s)
from the list of existing methods or use external module(s).
This patch also updates the currently existing enumeration/discovery code to be
used as a statically linked or modular method. The corresponding configuration
option is named "Basic enumeration/discovery" method. This is the only one
configuration option available today but new methods are expected to be
introduced after adoption of provided patches.
The second patch address a long time complaint of RapidIO subsystem users
regarding fabric enumeration/discovery start sequence. Existing implementation
offers only a boot-time enumeration/discovery start which requires synchronized
boot of all endpoints in RapidIO network. While it works for small closed
configurations with limited number of endpoints, using this approach in systems
with large number of endpoints is quite challenging.
To eliminate requirement for synchronized start the second patch introduces
RapidIO enumeration/discovery start from user space.
For compatibility with the existing RapidIO subsystem implementation, automatic
boot time enumeration/discovery start can be configured in by specifying
"rio-scan.scan=1" command line parameter if statically linked basic enumeration
method is selected.
Changes since v1:
(1) Addressed comments made by Andrew Morton for v1:
- reworked enumeration/discovery module initialization
- added locking for list of mport devices
- made mport list static
- removed CONFIG_RAPIDIO_ENUM_AUTO option: not needed with new
module initialization
- added default value for "Enumeration method" choice in Kconfig
Cc: Matt Porter <mporter@kernel.crashing.org>
Cc: Li Yang <leoli@freescale.com>
Cc: Kumar Gala <galak@kernel.crashing.org>
Cc: Andre van Herk <andre.van.herk@Prodrive.nl>
Cc: Micha Nelissen <micha.nelissen@Prodrive.nl>
Alexandre Bounine (3):
rapidio: make enumeration/discovery configurable
rapidio: add enumeration/discovery start from user space
rapidio: documentation update for enumeration changes
Documentation/rapidio/rapidio.txt | 128 ++++++++++++++++++--
Documentation/rapidio/sysfs.txt | 17 +++
drivers/rapidio/Kconfig | 20 +++
drivers/rapidio/Makefile | 3 +-
drivers/rapidio/rio-driver.c | 8 ++
drivers/rapidio/rio-scan.c | 190 +++++++++-------------------
drivers/rapidio/rio-sysfs.c | 45 +++++++
drivers/rapidio/rio.c | 246 +++++++++++++++++++++++++++++++++++-
drivers/rapidio/rio.h | 13 ++-
include/linux/rio.h | 18 +++-
include/linux/rio_drv.h | 1 +
11 files changed, 536 insertions(+), 153 deletions(-)
--
1.7.8.4
next reply other threads:[~2013-04-30 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 21:25 Alexandre Bounine [this message]
2013-04-30 21:25 ` [PATCH v2 1/3] rapidio: make enumeration/discovery configurable Alexandre Bounine
2013-04-30 21:25 ` [PATCH v2 2/3] rapidio: add enumeration/discovery start from user space Alexandre Bounine
2013-04-30 21:25 ` [PATCH v2 3/3] rapidio: documentation update for enumeration changes Alexandre Bounine
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=1367357155-11586-1-git-send-email-alexandre.bounine@idt.com \
--to=alexandre.bounine@idt.com \
--cc=akpm@linux-foundation.org \
--cc=andre.van.herk@Prodrive.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=micha.nelissen@Prodrive.nl \
/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