All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: davinci-linux-open-source@linux.davincidsp.com
Cc: Manjunath Hadli <manjunath.hadli@ti.com>,
	LMML <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 07/13] davinci: vpif: add support to use videobuf_iolock()
Date: Tue, 17 Apr 2012 11:46:50 +0200	[thread overview]
Message-ID: <11508400.1umVUoMoqL@avalon> (raw)
In-Reply-To: <1334652791-15833-8-git-send-email-manjunath.hadli@ti.com>

Hi Manjunath,

Thanks for the patch.

On Tuesday 17 April 2012 14:23:05 Manjunath Hadli wrote:
> add support to use videobuf_iolock() instead of VPIF
> defined vpif_uservirt_to_phys API. Use videobuf_to_dma_contig
> API for both memory-mapped and userptr buffer allocations.
> Correspondingly removed vpif_uservirt_to_phys() VPIF defined API.

What about using videobuf2 instead ? :-)

-- 
Regards,

Laurent Pinchart


       reply	other threads:[~2012-04-17  9:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1334652791-15833-1-git-send-email-manjunath.hadli@ti.com>
     [not found] ` <1334652791-15833-8-git-send-email-manjunath.hadli@ti.com>
2012-04-17  9:46   ` Laurent Pinchart [this message]
2012-05-11  5:26     ` [PATCH v2 07/13] davinci: vpif: add support to use videobuf_iolock() Hadli, Manjunath
     [not found] ` <1334652791-15833-6-git-send-email-manjunath.hadli@ti.com>
2012-04-17 10:02   ` [PATCH v2 05/13] davinci: vpif display: declare contiguous region of memory handled by dma_alloc_coherent Laurent Pinchart
2012-05-11  5:30     ` Hadli, Manjunath
2012-05-14  7:46       ` Laurent Pinchart
2012-06-07 11:15         ` Hadli, Manjunath
     [not found] ` <1334652791-15833-2-git-send-email-manjunath.hadli@ti.com>
2012-04-17 10:06   ` [PATCH v2 01/13] davinci: vpif: add check for genuine interrupts in the isr Laurent Pinchart
2012-05-11  5:32     ` Hadli, Manjunath
2012-05-14  7:49       ` Laurent Pinchart
2012-06-07 11:25         ` Hadli, Manjunath

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=11508400.1umVUoMoqL@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-media@vger.kernel.org \
    --cc=manjunath.hadli@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 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.