From: Kumar Gala <galak@kernel.crashing.org>
To: Zhang Wei <wei.zhang@freescale.com>
Cc: mporter@kernel.crashing.org, paulus@samba.org,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 5/5 v3] Add the memory management driver to RapidIO.
Date: Thu, 24 Jan 2008 01:01:07 -0600 [thread overview]
Message-ID: <71AAAC27-C150-4C3D-B065-BC15196BED2B@kernel.crashing.org> (raw)
In-Reply-To: <11854393771067-git-send-email-wei.zhang@freescale.com>
On Jul 26, 2007, at 3:42 AM, Zhang Wei wrote:
> This patch adds the memory management driver to RapidIO.
> The RapidIO system size is changed to automatically detection.
> Add the memory mapping driver to RapidIO basic driver.
> Multi master ports are supported.
> Add a simple Bitmap RapidIO space allocator driver.
Can we break up the functionality here into separate patches. I'm
seeing 4 logical patches:
* system size is changed to automatic detection
* support for multi master ports
* bitmap allocator
* memory map driver
> Signed-off-by: Zhang Wei <wei.zhang@freescale.com>
> ---
> drivers/net/rionet.c | 17 +-
> drivers/rapidio/Kconfig | 18 +-
> drivers/rapidio/Makefile | 1 +
> drivers/rapidio/rio-access.c | 10 +-
> drivers/rapidio/rio-scan.c | 53 +++--
> drivers/rapidio/rio-sysfs.c | 3 +-
> drivers/rapidio/rio.c | 479 ++++++++++++++++++++++++++
> ++++++++-
> drivers/rapidio/rio.h | 9 +-
> drivers/rapidio/sallocator/Kconfig | 9 +
> drivers/rapidio/sallocator/Makefile | 12 +
> drivers/rapidio/sallocator/bitmap.c | 382 ++++++++++++++++++++++++++
> ++
> include/linux/rio.h | 71 +++++-
> include/linux/rio_drv.h | 41 +++-
> 13 files changed, 1046 insertions(+), 59 deletions(-)
> create mode 100644 drivers/rapidio/sallocator/Kconfig
> create mode 100644 drivers/rapidio/sallocator/Makefile
> create mode 100644 drivers/rapidio/sallocator/bitmap.c
[snip]
> +config RAPIDIO_PROC_FS
> + bool "I/O and Memory resource debug"
> + depends on RAPIDIO && PROC_FS
> + default y
> + ---help---
> + Enable this option, it will create a /proc/riores node for
> + monitoring the RapidIO I/O and Memory resource.
> +
This isn't going to be acceptable. You should use sysfs or debugfs
not proc.
- k
next prev parent reply other threads:[~2008-01-24 7:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 8:42 [PATCH 0/5 v3] Porting RapidIO driver from ppc to powerpc architecture and adding memory mapped RapidIO driver Zhang Wei
2007-07-26 8:42 ` [PATCH 1/5 v3] Add the explanation and a sample of RapidIO OF node to the document of booting-without-of.txt file Zhang Wei
2007-07-26 8:42 ` [PATCH 2/5 v3] Add RapidIO OF-node to the MPC8641HPCN board dts file Zhang Wei
2007-07-26 8:42 ` [PATCH 3/5 v3] Add the platform device support with RapidIO to MPC8641HPCN platform Zhang Wei
2007-07-26 8:42 ` [PATCH 4/5 v3] Add RapidIO support to powerpc architecture Zhang Wei
2007-07-26 8:42 ` [PATCH 5/5 v3] Add the memory management driver to RapidIO Zhang Wei
2008-01-24 7:01 ` Kumar Gala [this message]
2007-07-27 8:12 ` [PATCH 4/5 v3] Add RapidIO support to powerpc architecture Stephen Rothwell
2007-07-27 8:22 ` Kumar Gala
2007-07-27 9:03 ` Zhang Wei-r63237
2007-07-27 7:54 ` [PATCH 3/5 v3] Add the platform device support with RapidIO to MPC8641HPCN platform Stephen Rothwell
2007-07-29 13:56 ` Arnd Bergmann
2007-07-30 8:26 ` Zhang Wei-r63237
2007-07-27 8:51 ` [PATCH 1/5 v3] Add the explanation and a sample of RapidIO OF node to the document of booting-without-of.txt file Kumar Gala
2007-07-27 9:12 ` Zhang Wei-r63237
2007-07-31 16:15 ` Segher Boessenkool
2007-07-31 16:19 ` Segher Boessenkool
2007-07-27 8:28 ` [PATCH 0/5 v3] Porting RapidIO driver from ppc to powerpc architecture and adding memory mapped RapidIO driver Kumar Gala
2007-10-29 19:38 ` Phil Terry
2007-10-29 20:30 ` Kumar Gala
2007-10-30 8:40 ` Zhang Wei-r63237
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=71AAAC27-C150-4C3D-B065-BC15196BED2B@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mporter@kernel.crashing.org \
--cc=paulus@samba.org \
--cc=wei.zhang@freescale.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
all inboxes | Powered by JetHome®