From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: "Bryan Wu" <cooloney.lkml@gmail.com>
Subject: [rfc] exposing MMR's of on-chip peripherals for debugging purposes
Date: Mon, 28 Jan 2008 05:16:20 -0500 [thread overview]
Message-ID: <8bd0f97a0801280216x56d52028s2ea247dd969e85e2@mail.gmail.com> (raw)
we have guys who maintain xml descriptions of all Blackfin processors.
these include an exhaustive list of all the peripherals and their
MMRs. for example, there is an element that binds the address, the
MMR name (as described in the processor's hardware manual), the bit
size of it, and all those fun details. i feed these xml files through
an xsl to generate a C file that populates /sys/kernel/debug/blackfin/
by using the standard debugfs functions. so when i'm debugging the
watchdog driver, i can simply go into
/sys/kernel/debug/blackfin/watchdog/ and see the watchdog-specific
MMRs and cat/echo them on the fly. it's been quite handy and feedback
from customers/developers is that it's nicely filled a small void in
the development process.
the trouble is that this file currently weighs in at ~1.8 megs. this
is because it contains all the information for all Blackfin processors
we support (which currently, is about ~23 variants). it's only going
to get bigger as we support more. Bryan cringes at the thought of
submitting it to LKML :). so i'm fishing around for alternatives ...
the code was originally developed against 2.6.21, so UIO was not a
possibility. i'm still not sure if it is ... i'd have to research it
a bit more and play with things.
any pointers ?
-mike
next reply other threads:[~2008-01-28 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 10:16 Mike Frysinger [this message]
2008-01-28 10:19 ` [rfc] exposing MMR's of on-chip peripherals for debugging purposes Mike Frysinger
2008-01-28 10:40 ` Bryan Wu
2008-01-28 11:06 ` Mike Frysinger
2008-01-28 13:04 ` richard kennedy
2008-01-28 13:10 ` Mike Frysinger
2008-01-29 0:08 ` Daniel Barkalow
2008-01-29 0:15 ` Mike Frysinger
2008-01-29 0:30 ` Daniel Barkalow
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=8bd0f97a0801280216x56d52028s2ea247dd969e85e2@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=cooloney.lkml@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox