From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: hvaibhav@ti.com
Cc: linux-media@vger.kernel.org, Amber Jain <amber@ti.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL for v3.0] OMAP_VOUT bug fixes and code cleanup
Date: Fri, 01 Jul 2011 15:43:11 -0300 [thread overview]
Message-ID: <4E0E153F.5000303@redhat.com> (raw)
In-Reply-To: <1308771169-10741-1-git-send-email-hvaibhav@ti.com>
Em 22-06-2011 16:32, hvaibhav@ti.com escreveu:
> The following changes since commit af0d6a0a3a30946f7df69c764791f1b0643f7cd6:
> Linus Torvalds (1):
> Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/.../tip/linux-2.6-tip
>
> are available in the git repository at:
>
> git://arago-project.org/git/people/vaibhav/ti-psp-omap-video.git for-linux-media
>
> Amber Jain (2):
> V4L2: omap_vout: Remove GFP_DMA allocation as ZONE_DMA is not configured on OMAP
> OMAP2: V4L2: Remove GFP_DMA allocation as ZONE_DMA is not configured on OMAP
> From: Amber Jain <amber@ti.com>
> Date: Tue May 31 11:45:36 2011 -0300
>
> OMAP2: V4L2: Remove GFP_DMA allocation as ZONE_DMA is not configured on OMAP
>
> Remove GFP_DMA from the __get_free_pages() call from omap24xxcam as ZONE_DMA
> is not configured on OMAP. Earlier the page allocator used to return a page
> from ZONE_NORMAL even when GFP_DMA is passed and CONFIG_ZONE_DMA is disabled.
> As a result of commit a197b59ae6e8bee56fcef37ea2482dc08414e2ac, page allocator
> returns null in such a scenario with a warning emitted to kernel log.
>
> Signed-off-by: Amber Jain <amber@ti.com>
> Acked-by: Sakari Ailus <sakari.ailus@iki.fi>
> Signed-off-by: Vaibhav Hiremath <hvaibhav@ti.com>
>
> diff --git a/drivers/media/video/omap24xxcam.c b/drivers/media/video/omap24xxcam.c
> index f6626e8..d92d4c6 100644
> --- a/drivers/media/video/omap24xxcam.c
> +++ b/drivers/media/video/omap24xxcam.c
> @@ -309,11 +309,11 @@ static int omap24xxcam_vbq_alloc_mmap_buffer(struct videobuf_buffer *vb)
> order--;
>
> /* try to allocate as many contiguous pages as possible */
> - page = alloc_pages(GFP_KERNEL | GFP_DMA, order);
> + page = alloc_pages(GFP_KERNEL, order);
> /* if allocation fails, try to allocate smaller amount */
> while (page == NULL) {
> order--;
> - page = alloc_pages(GFP_KERNEL | GFP_DMA, order);
> + page = alloc_pages(GFP_KERNEL, order);
> if (page == NULL && !order) {
> err = -ENOMEM;
> goto out;
Hmm... the proper fix wouldn't be to define ZONE_DMA at OMAP?
Thanks,
Mauro
next prev parent reply other threads:[~2011-07-01 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 19:32 [GIT PULL for v3.0] OMAP_VOUT bug fixes and code cleanup hvaibhav
2011-07-01 18:43 ` Mauro Carvalho Chehab [this message]
2011-07-05 11:34 ` JAIN, AMBER
2011-07-06 20:43 ` David Rientjes
2011-07-07 5:55 ` Hiremath, Vaibhav
2011-07-07 5:57 ` JAIN, AMBER
2011-07-08 20:16 ` David Rientjes
2011-07-11 13:35 ` Hiremath, Vaibhav
2011-07-01 18:48 ` Mauro Carvalho Chehab
2011-07-01 22:49 ` Archit Taneja
2011-07-01 23:44 ` Mauro Carvalho Chehab
2011-07-02 1:31 ` Archit Taneja
2011-07-04 5:09 ` Hiremath, Vaibhav
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=4E0E153F.5000303@redhat.com \
--to=mchehab@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amber@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-media@vger.kernel.org \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.