From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
anaghi@mail.gnudd.com, balbi@ti.com
Subject: Re: [PATCH V2 0/2] debugfs: a tool to print 32-bit registers
Date: Tue, 22 Nov 2011 13:04:33 +0000 [thread overview]
Message-ID: <20111122130433.GC21029@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111118002049.GA24806@mail.gnudd.com>
On Fri, Nov 18, 2011 at 01:20:49AM +0100, Alessandro Rubini wrote:
> Mark, if you say this is not useful at this point, I'm fine with it; I
> may return with some regbase-aware code when time permits if it's not
> already there.
We definitely can't just use this directly with regmap as regmap is for
non memory mapped devices and makes some assumptions in that regard. I
was mostly just suggesting that we try to keep the file formats similar
to make life easier for userspace.
prev parent reply other threads:[~2011-11-22 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 0:20 [PATCH V2 0/2] debugfs: a tool to print 32-bit registers Alessandro Rubini
2011-11-18 13:36 ` Felipe Balbi
2011-11-18 13:55 ` Alessandro Rubini
2011-11-18 13:50 ` [PATCH V2 1/2] debugfs: add tools to printk " Alessandro Rubini
2011-11-18 13:51 ` [PATCH V2 2/2] usb: dwc3: use debugfs_print_regs32() Alessandro Rubini
2011-11-18 18:31 ` Greg KH
2011-11-18 19:26 ` Felipe Balbi
2011-11-18 19:48 ` Greg KH
2011-11-18 22:53 ` [PATCH] usb: dwc3: fix a warning Alessandro Rubini
2011-11-18 22:53 ` [PATCH] debugfs: print_regs32: make regs array a const pointer Alessandro Rubini
2011-11-22 13:04 ` Mark Brown [this message]
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=20111122130433.GC21029@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anaghi@mail.gnudd.com \
--cc=balbi@ti.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.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.