From: Kevin Cernekee <cernekee@gmail.com>
To: ralf@linux-mips.org
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] MIPS: Extend plat_* abstractions, cache support
Date: Thu, 23 Apr 2009 17:03:43 -0700 [thread overview]
Message-ID: <0483452db22e72f57289e63fcf097120d94c2a37.1240533480.git@localhost> (raw)
Hi,
I am upgrading an SoC to the 2.6.29.1 kernel from an earlier version,
and in the process I am switching over the old board support
customizations to use the newer, cleaner plat_* functions. I found two
cases where the plat_* functions did not provide enough information,
so I had to modify the API:
plat_unmap_dma_mem() - Our handler needs to know the size and direction
of the DMA mapping. This information is not encoded in the DMA address,
so it needed to be passed in explicitly.
plat_dma_addr_to_phys() - The bus<->physical address mappings differ
based on which bus is being used. It is not always possible to infer
which bus is being used from the bus address alone, so I added a
"struct device" to the function definition.
Also, our MIPS core uses 64-byte D$ lines, so I needed to generate the
corresponding blast* functions.
These patches apply against the linux-mips.org GIT tree.
next reply other threads:[~2009-04-24 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 0:03 Kevin Cernekee [this message]
2009-04-24 0:03 ` [PATCH 1/3] MIPS: Add size and direction arguments to plat_unmap_dma_mem() Kevin Cernekee
2009-04-24 0:25 ` [PATCH 2/3] MIPS: Pass struct device to plat_dma_addr_to_phys() Kevin Cernekee
2009-04-24 0:36 ` [PATCH 3/3] MIPS: Support 64-byte D-cache line size Kevin Cernekee
2009-04-24 1:46 ` [PATCH 0/3] MIPS: Extend plat_* abstractions, cache support Bob Zhang
2009-04-24 4:23 ` Ralf Baechle
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=0483452db22e72f57289e63fcf097120d94c2a37.1240533480.git@localhost \
--to=cernekee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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
Powered by JetHome