From: "Arend van Spriel" <arend@broadcom.com>
To: george@znau.edu.ua
Cc: zajec5@gmail.com, mb@bu3sch.de, linville@tuxdriver.com,
arend@broadcom.com, linux-wireless@vger.kernel.org
Subject: [RFC] drivers: brcmaxi: AMBA AXI functionality library module
Date: Mon, 21 Mar 2011 21:16:25 +0100 [thread overview]
Message-ID: <1300738586-7157-1-git-send-email-arend@broadcom.com> (raw)
To feed the active discussion some more I offer this patch to be
reviewed by those interested. I do not expect this to be all peachy
but would like to get a more concrete discussion going here.
Refer to thread 'new utility kernel module for detecting cores in newer
chipsets'. George used the term 'backplane agents'. This module could
be considered such an agent. It exposes cores to the 'core driver' by
calling driver provided callbacks. Currently it also exposes register
space (wrapper) which only concerns 'backplane agents' and not so much
to 'core drivers'. Currently, this module does not provide any code
for the 'core drivers'.
Arend van Spriel (1):
drivers: brcmaxi: provide amba axi functionality in separate module
drivers/Kconfig | 2 +
drivers/Makefile | 1 +
drivers/brcmaxi/Makefile | 23 ++
drivers/brcmaxi/axi.c | 859 ++++++++++++++++++++++++++++++++++++++++++++++
include/brcmaxi/axi.h | 340 ++++++++++++++++++
5 files changed, 1225 insertions(+), 0 deletions(-)
create mode 100644 drivers/brcmaxi/Makefile
create mode 100644 drivers/brcmaxi/axi.c
create mode 100644 include/brcmaxi/axi.h
next reply other threads:[~2011-03-21 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 20:16 Arend van Spriel [this message]
2011-03-21 20:16 ` [RFC] drivers: brcmaxi: provide amba axi functionality in separate module Arend van Spriel
2011-03-21 20:28 ` Randy Dunlap
2011-03-21 20:38 ` Johannes Berg
2011-03-21 20:42 ` Randy Dunlap
2011-03-21 20:45 ` Johannes Berg
2011-03-23 10:51 ` Arend van Spriel
[not found] ` <1300888183.18815.5.camel@Nokia-N900>
2011-03-23 13:54 ` Arend van Spriel
2011-03-23 14:09 ` Michael Büsch
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=1300738586-7157-1-git-send-email-arend@broadcom.com \
--to=arend@broadcom.com \
--cc=george@znau.edu.ua \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=zajec5@gmail.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 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.