From: omar.luna@linaro.org (Omar Ramirez Luna)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] OMAP: control: bootaddr and bootmod APIs
Date: Wed, 2 May 2012 21:11:50 -0500 [thread overview]
Message-ID: <1336011113-31502-1-git-send-email-omar.luna@linaro.org> (raw)
Recently a patch went in for tidspbridge code, to ioremap
SCM registers and solve a build break[1]. However it has
been pointed out before that this is a layer violation
given that control module should handle its own registers, this
series is an attempt to create APIs for the users of these
registers.
With some adaptations this patch might also make use of it:
http://www.mail-archive.com/linux-omap at vger.kernel.org/msg66491.html
Patch: staging: tidspbridge: use scm functions to set boot address and mode,
will be sent separately to staging tree.
Tested on OMAP3 Beagleboard.
[1] http://www.mail-archive.com/devel at linuxdriverproject.org/msg18762.html
Omar Ramirez Luna (3):
OMAP2+: control: new APIs to configure boot address and mode
OMAP: dsp: interface to control module functions
staging: tidspbridge: use scm functions to set boot address and mode
arch/arm/mach-omap2/control.c | 43 ++++++++++++++++++++
arch/arm/mach-omap2/control.h | 2 +
arch/arm/mach-omap2/dsp.c | 4 ++
.../include/mach/ctrl_module_core_44xx.h | 1 +
arch/arm/plat-omap/include/plat/dsp.h | 3 +
drivers/staging/tidspbridge/core/tiomap3430.c | 32 +++-----------
6 files changed, 60 insertions(+), 25 deletions(-)
--
1.7.4.1
next reply other threads:[~2012-05-03 2:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 2:11 Omar Ramirez Luna [this message]
2012-05-03 2:11 ` [PATCH 1/3] OMAP2+: control: new APIs to configure boot address and mode Omar Ramirez Luna
2012-05-03 2:11 ` [PATCH 2/3] OMAP: dsp: interface to control module functions Omar Ramirez Luna
2012-05-03 2:11 ` [PATCH 3/3] staging: tidspbridge: use scm functions to set boot address and mode Omar Ramirez Luna
2012-05-16 2:20 ` [PATCH 0/3] OMAP: control: bootaddr and bootmod APIs Omar Ramirez Luna
2012-05-18 22:50 ` Paul Walmsley
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=1336011113-31502-1-git-send-email-omar.luna@linaro.org \
--to=omar.luna@linaro.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).