From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: dma_declare_coherent_memory() again.
Date: Tue, 22 Feb 2011 09:41:09 +0100 [thread overview]
Message-ID: <20110222084109.GW22310@pengutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1102211602140.26977@axis700.grange>
On Mon, Feb 21, 2011 at 04:37:00PM +0100, Guennadi Liakhovetski wrote:
> Hi All
>
> AFAIU, dma_declare_coherent_memory() is still present on the following
> platforms:
>
> arch/arm/mach-mx3/mach-pcm037.c
I had a patch for that one[1]. Russell considered it OK if I got him
correctly. (I think it's OK from a platform's POV, maybe there are some
architecture problems?)
There were a few minor review nits, I can respin if there is general
agreement that the patch is fine.
> arch/arm/mach-mx3/mach-mx31moboard.c
> arch/arm/mach-shmobile/board-ap4evb.c
> arch/arm/mach-shmobile/board-mackerel.c (latter 2 via
> drivers/media/video/sh_mobile_ceu_camera.c)
>
> and there are no pending patches to fix them for 2.6.38, is this right? If
> there are no realistic plans for proper memory reservation on ARM in
> 2.6.38, shall I just submit patches to disable those calls on the above
> platforms and hope, that the user manages to get RAM without boot-time
> reservation? Or is a definite failure preferred?
Thanks
Uwe
[1] http://mid.gmane.org/1290505382-16110-1-git-send-email-u.kleine-koenig at pengutronix.de
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2011-02-22 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 15:37 dma_declare_coherent_memory() again Guennadi Liakhovetski
2011-02-21 20:25 ` Philippe Rétornaz
2011-02-22 8:41 ` Uwe Kleine-König [this message]
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=20110222084109.GW22310@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).