From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: Ameya Palande <ameya.palande@nokia.com>,
Hiroshi Doyu <Hiroshi.DOYU@nokia.com>,
Felipe Contreras <felipe.contreras@nokia.com>,
Nishanth Menon <nm@ti.com>,
Omar Ramirez Luna <omar.ramirez@ti.com>
Subject: [PATCH 0/2] DSPBRIDGE: 128 bytes alignment check
Date: Fri, 26 Mar 2010 15:02:26 -0600 [thread overview]
Message-ID: <1269637348-20608-1-git-send-email-omar.ramirez@ti.com> (raw)
Technical info:
https://omapzoom.org/gf/download/docmanfileversion/52/985/DSP_cache.pdf
This set of patches introduces the 128 byte alignment check,
needed to avoid corruption if the dsp is meant to write to
boundary portions of an unaligned chunk of memory.
The second patch uses a field composed of 2 bits to distinguish
if the mapped chunk is readable/writeable, so the check can be
performed on w/rw chunks of memory.
Omar Ramirez Luna (2):
DSPBRIDGE: add checking 128 byte alignment for dsp cache line size
DSPBRIDGE: Distinguish between read or write buffers
arch/arm/plat-omap/include/dspbridge/dbdefs.h | 7 ++++++-
drivers/dsp/bridge/Kconfig | 14 ++++++++++++++
drivers/dsp/bridge/rmgr/proc.c | 19 +++++++++++++++++++
drivers/dsp/bridge/wmd/tiomap3430.c | 4 ++--
4 files changed, 41 insertions(+), 3 deletions(-)
next reply other threads:[~2010-03-26 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 21:02 Omar Ramirez Luna [this message]
2010-03-26 21:02 ` [PATCH 1/2] DSPBRIDGE: add checking 128 byte alignment for dsp cache line size Omar Ramirez Luna
2010-03-26 21:02 ` [PATCH 2/2] DSPBRIDGE: Distinguish between read or write buffers Omar Ramirez Luna
2010-04-06 2:49 ` [PATCH 0/2] DSPBRIDGE: 128 bytes alignment check Omar Ramirez Luna
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=1269637348-20608-1-git-send-email-omar.ramirez@ti.com \
--to=omar.ramirez@ti.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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