From: Omar Ramirez Luna <omar.ramirez@copitl.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Victor Manuel Jaquez Leal <vjaquez@igalia.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Omar Ramirez Luna <omar.ramirez@copitl.com>
Subject: [PATCH 0/6] staging: tidspbridge fixes for 3.7
Date: Wed, 24 Oct 2012 17:09:14 -0500 [thread overview]
Message-ID: <1351116560-6918-1-git-send-email-omar.ramirez@copitl.com> (raw)
With 3.7-rc1 changes:
- New irq numbering in OMAP3 broke the driver request for a mmu irq,
until this is migrated to the common iommu framework we can only
hardcode the new number.
- _raw_* accessors changed a type of one of their parameters with patch
"195bbca ARM: 7500/1: io: avoid writeback addressing modes for
__raw_ accessors", so the build system was filled with warnings from
the old parameter usage.
Omar Ramirez Luna (6):
staging: tidspbridge: request the right irq for mmu
staging: tidspbridge: drop const from custom mmu implementation
staging: tidspbridge: change type to __iomem for per and core
addresses
staging: tidspbridge: ioremap dsp sync addr
staging: tidspbridge: ioremap physical address of the stack segment
in shm
staging: tidspbridge: delete unused mmu functions
drivers/staging/tidspbridge/core/tiomap3430.c | 37 +++++--
drivers/staging/tidspbridge/hw/hw_mmu.c | 115 ++++----------------
drivers/staging/tidspbridge/hw/hw_mmu.h | 31 +++---
.../tidspbridge/include/dspbridge/cfgdefs.h | 4 +-
.../tidspbridge/include/dspbridge/host_os.h | 4 +-
drivers/staging/tidspbridge/rmgr/drv.c | 8 +-
drivers/staging/tidspbridge/rmgr/node.c | 21 +++-
7 files changed, 83 insertions(+), 137 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-10-24 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 22:09 Omar Ramirez Luna [this message]
2012-10-24 22:09 ` [PATCH 1/6] staging: tidspbridge: request the right irq for mmu Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 2/6] staging: tidspbridge: drop const from custom mmu implementation Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 3/6] staging: tidspbridge: change type to __iomem for per and core addresses Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 4/6] staging: tidspbridge: ioremap dsp sync addr Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 5/6] staging: tidspbridge: ioremap physical address of the stack segment in shm Omar Ramirez Luna
2012-10-24 22:09 ` [PATCH 6/6] staging: tidspbridge: delete unused mmu functions Omar Ramirez Luna
2012-10-24 22:28 ` [PATCH 0/6] staging: tidspbridge fixes for 3.7 Greg Kroah-Hartman
2012-10-24 23:25 ` Omar Ramirez Luna
2012-10-24 23:35 ` Greg Kroah-Hartman
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=1351116560-6918-1-git-send-email-omar.ramirez@copitl.com \
--to=omar.ramirez@copitl.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vjaquez@igalia.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 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).