All of lore.kernel.org
 help / color / mirror / Atom feed
From: Federico Vaga <federico.vaga@gmail.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: 'Mauro Carvalho Chehab' <mchehab@infradead.org>,
	'Pawel Osciak' <pawel@osciak.com>,
	'Hans Verkuil' <hans.verkuil@cisco.com>,
	'Giancarlo Asnaghi' <giancarlo.asnaghi@st.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	'Jonathan Corbet' <corbet@lwn.net>,
	Tomasz Stanislawski <t.stanislaws@samsung.local>
Subject: Re: [PATCH 2/3] [media] videobuf2-dma-streaming: new videobuf2 memory allocator
Date: Fri, 24 Aug 2012 15:23:09 +0200	[thread overview]
Message-ID: <1417436.RHVOLNlTxk@harkonnen> (raw)
In-Reply-To: <02f301cd7eaa$4fa7a7a0$eef6f6e0$%szyprowski@samsung.com>

> Getting back to your patch - in your approach cpu cache handling is
> missing. I suspect that it worked fine only because it has been
> tested on some simple platform without any cpu caches (or with very
> small ones).

Is missing from the memory allocator because I do it on the device 
driver. The current operations don't allow me to do that in the memory 
allocator.


> Please check the following thread:
> http://www.spinics.net/lists/linux-media/msg51768.html where Tomasz
> has posted his ongoing effort on updating and extending videobuf2 and
> dma-contig allocator. Especially the patch
> http://www.spinics.net/lists/linux-media/msg51776.html will be
> interesting for you, because cpu cache synchronization
> (dma_sync_single_for_device / dma_sync_single_for_cpu) should be
> called from prepare/finish callbacks.

You are right, it is interesting because avoid me to use cache sync in 
my driver. Can I work on these patches?

>From this page I understand that these patches are not approved yet
https://patchwork.kernel.org/project/linux-media/list/?page=2

-- 
Federico Vaga

  reply	other threads:[~2012-08-24 13:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 20:17 Update VIP to videobuf2 and control framework Federico Vaga
2012-07-31 20:17 ` [PATCH 1/3] [media] adv7180: remove {query/g_/s_}ctrl Federico Vaga
2012-07-31 20:20   ` Federico Vaga
2012-08-12  1:46     ` Mauro Carvalho Chehab
2012-07-31 20:17 ` [PATCH 2/3] [media] videobuf2-dma-streaming: new videobuf2 memory allocator Federico Vaga
2012-08-20  8:03   ` Marek Szyprowski
2012-08-24 13:23     ` Federico Vaga [this message]
2012-08-24 13:40       ` Marek Szyprowski
2012-08-24 13:48         ` Federico Vaga
2012-07-31 20:17 ` [PATCH 3/3] [media] sta2x11_vip: convert to videobuf2 and control framework Federico Vaga
2012-08-06  8:17   ` [PATCH 3/3 v2] " Federico Vaga
2012-08-06  8:42     ` Hans Verkuil
2012-08-06  8:55       ` Federico Vaga
2012-07-31 20:27 ` Update VIP " Federico Vaga
2012-08-01  6:41 ` Hans Verkuil
2012-08-01 13:04   ` Jonathan Corbet
2012-08-16 11:29     ` Federico Vaga
2012-08-05 17:11   ` Federico Vaga
2012-08-06  7:26     ` Hans Verkuil
2012-08-06  7:38       ` Federico Vaga
2012-08-06  7:36         ` Hans Verkuil
2012-08-06  8:20           ` Federico Vaga

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=1417436.RHVOLNlTxk@harkonnen \
    --to=federico.vaga@gmail.com \
    --cc=corbet@lwn.net \
    --cc=giancarlo.asnaghi@st.com \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mchehab@infradead.org \
    --cc=pawel@osciak.com \
    --cc=t.stanislaws@samsung.local \
    /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.