From: joshc@codeaurora.org (Josh Cartwright)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC v2 2/5] spmi: Linux driver framework for SPMI
Date: Mon, 9 Sep 2013 11:56:04 -0500 [thread overview]
Message-ID: <20130909165604.GM808@joshc.qualcomm.com> (raw)
In-Reply-To: <20130909155224.GQ29403@sirena.org.uk>
Hey Mark-
Thanks for the comments.
On Mon, Sep 09, 2013 at 04:52:24PM +0100, Mark Brown wrote:
> On Fri, Aug 23, 2013 at 11:06:25AM -0500, Josh Cartwright wrote:
> > On Thu, Aug 22, 2013 at 04:10:54PM -0700, Greg Kroah-Hartman wrote:
> > > On Fri, Aug 09, 2013 at 01:37:09PM -0700, Josh Cartwright wrote:
>
> > > > + "Example: Read 4 bytes starting at register address 0x1234 for SID 2\n"
> > > > + "\n"
> > > > + "echo 0x21234 > address\n"
> > > > + "echo 4 > count\n"
> > > > + "cat data\n"
> > > > + "\n"
> > > > + "Example: Write 3 bytes starting at register address 0x1008 for SID 1\n"
> > > > + "\n"
> > > > + "echo 0x11008 > address\n"
> > > > + "echo 0x01 0x02 0x03 > data\n"
> > > > + "\n"
> > > > + "Note that the count file is not used for writes. Since 3 bytes are\n"
> > > > + "written to the 'data' file, then 3 bytes will be written across the\n"
> > > > + "SPMI bus.\n\n";
>
> > > The help file within the kernel is a nice touch :)
>
> > > Or is this only for "debugging"? If so, please document it as such.
>
> > It's there because it provides a useful interface for debugging of the
> > controller code, and for simple peek/poke of the slave registers without
> > having a full driver in place. Will document this.
>
> This looks awfully like a version of the debugfs interfaces that regmap
> provides, and indeed the entire bus sounds like something that could
> idiomatically be supported via regmap. Have you considered doing that?
> This would give access to standard tracepoints as well, plus the cache
> infrastructure.
It does indeed look like regmap might work out nicely for SPMI. I
hadn't seriously considered it just due to a lack of familiarity. I'll
give it a shot and see if I run into any problems.
Thanks,
Josh
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-09-09 16:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 20:18 [PATCH RFC v2 0/3] Add support for the System Power Management Interface (SPMI) Josh Cartwright
2013-08-09 20:37 ` [PATCH RFC v2 4/5] spmi: Add MSM PMIC Arbiter SPMI controller Josh Cartwright
2013-08-09 20:37 ` [PATCH RFC v2 5/5] spmi: document the PMIC arbiter SPMI bindings Josh Cartwright
2013-08-23 21:55 ` Stephen Warren
2013-08-09 20:37 ` [PATCH RFC v2 2/5] spmi: Linux driver framework for SPMI Josh Cartwright
2013-08-22 23:10 ` Greg Kroah-Hartman
2013-08-23 16:06 ` Josh Cartwright
2013-09-09 15:52 ` Mark Brown
2013-09-09 16:56 ` Josh Cartwright [this message]
2013-08-22 19:59 ` [PATCH RFC v2 3/5] spmi: add generic SPMI controller binding documentation Josh Cartwright
2013-08-23 21:58 ` Stephen Warren
2013-08-27 17:01 ` Josh Cartwright
2013-08-27 21:55 ` Stephen Warren
2013-08-28 18:00 ` Josh Cartwright
2013-08-28 18:32 ` Stephen Warren
2013-10-06 6:11 ` Bjorn Andersson
2013-10-07 21:17 ` Josh Cartwright
2013-08-22 22:57 ` [PATCH RFC v2 1/5] of: Add empty for_each_available_child_of_node() macro definition Josh Cartwright
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=20130909165604.GM808@joshc.qualcomm.com \
--to=joshc@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).