From: Kevin Hilman <khilman@deeprootsystems.com>
To: Russell King <rmk@arm.linux.org.uk>, Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: RFD: OMAP PRCM register access holding up PM branch submissions
Date: Thu, 12 Mar 2009 08:25:55 -0700 [thread overview]
Message-ID: <87hc1y930c.fsf@deeprootsystems.com> (raw)
Russell, Paul,
As we discussed a bit in the OMAP clocks thread, there is not yet a
decision on the best way to access the PRCM registers. I'd like to
get some discussion going so I can begin submissions of the rest of
the OMAP PM core code.
We currently have two methods for PRCM register access
1) direct access using __raw_[read|write] and OMAP_PRM_REGADDR() #defines
2) "MOD + offset" access using prm_[read|write|rmw]_*
The current code (in Russell's omap-clks3) branch is kind of a hybrid
with lots of usages of both methods, and Paul's patch (A 09) which
converted everything to (2) has been rejected. However, I'm still not
entirely clear whether the objection was because you're opposed to the
'MOD + offset' approach in general, or just the way it was done in
this patch.
So, what is the path forward? If you are not opposed to moving to the
'MOD + offset' approach in principle, I propose we just make a new
attempt at converting to it. If you're opposed to it all together, we
need to start some discussion. Russell, you seem to have suggested
you had some ideas[1]. Would you mind posting your ideas for
discussion, not necessarily patches, but just rough ideas to start
discussions.
Until we get some decision on this, it is impossible to move forward
with submissions of the rest of the OMAP PM code.
Thanks,
Kevin
[1] http://marc.info/?l=linux-omap&m=123609877205834&w=2
next reply other threads:[~2009-03-12 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 15:25 Kevin Hilman [this message]
2009-03-12 16:28 ` RFD: OMAP PRCM register access holding up PM branch submissions Russell King - ARM Linux
2009-03-12 16:54 ` Kevin Hilman
2009-03-12 17:01 ` Russell King - ARM Linux
2009-03-12 17:26 ` Tony Lindgren
2009-03-12 17:55 ` Kevin Hilman
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=87hc1y930c.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rmk@arm.linux.org.uk \
/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