From: maurochehab@gmail.com (Mauro Carvalho Chehab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH/RFC v2.1 0/2] Mem-to-mem device framework
Date: Wed, 03 Feb 2010 06:44:28 -0200 [thread overview]
Message-ID: <4B69376C.1010407@gmail.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E7394044A277BB2@dbde02.ent.ti.com>
Hiremath, Vaibhav wrote:
>> -----Original Message-----
>> From: Pawel Osciak [mailto:p.osciak at samsung.com]
>> Sent: Monday, December 28, 2009 8:19 PM
>> To: 'Hans Verkuil'
>> Cc: linux-media at vger.kernel.org; linux-samsung-soc at vger.kernel.org;
>> linux-arm-kernel at lists.infradead.org; Marek Szyprowski;
>> kyungmin.park at samsung.com; Hiremath, Vaibhav; Karicheri,
>> Muralidharan; 'Guru Raj'; 'Xiaolin Zhang'; 'Magnus Damm'; 'Sakari
>> Ailus'
>> Subject: RE: [PATCH/RFC v2.1 0/2] Mem-to-mem device framework
>>
>> Hello Hans,
>>
>>
>> On Wednesday 23 December 2009 16:06:18 Hans Verkuil wrote:
>>> Thank you for working on this! It's much appreciated. Now I've
>> noticed that
>>> patches regarding memory-to-memory and memory pool tend to get
>> very few comments.
>>> I suspect that the main reason is that these are SoC-specific
>> features that do
>>> not occur in consumer-type products. So most v4l developers do not
>> have the
>>> interest and motivation (and time!) to look into this.
>> Thank you very much for your response. We were a bit surprised with
>> the lack of
>> responses as there seemed to be a good number of people interested
>> in this area.
>>
>> I'm hoping that everybody interested would take a look at the test
>> device posted
>> along with the patches. It's virtual, no specific hardware required,
>> but it
>> demonstrates the concepts behind the framework, including
>> transactions.
>>
> [Hiremath, Vaibhav] I was on vacation and resumed today itself, I will go through these patch series this weekend and will get back to you.
>
> I just had cursory look and I would say it should be really good starting point for us to support mem-to-mem devices.\
Hmm... it seems to me that those patches are still under discussion/analysis.
I'll mark them as RFC at the Patchwork.
Please let me know after you, SoC guys, go into a consensus about it. Then,
please submit me the final version.
Cheers,
Mauro
prev parent reply other threads:[~2010-02-03 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 13:17 [PATCH/RFC v2.1 0/2] Mem-to-mem device framework Pawel Osciak
2009-12-23 13:17 ` [PATCH v2.1 1/2] V4L: Add memory-to-memory device helper framework for V4L2 Pawel Osciak
2009-12-24 2:53 ` Andy Walls
2009-12-23 13:17 ` [PATCH v2.1 2/2] V4L: Add a mem-to-mem V4L2 framework test device Pawel Osciak
2009-12-23 13:17 ` [EXAMPLE v2] Mem-to-mem userspace test application Pawel Osciak
2009-12-23 15:05 ` [PATCH/RFC v2.1 0/2] Mem-to-mem device framework Hans Verkuil
2009-12-28 14:49 ` Pawel Osciak
2009-12-31 4:50 ` Hiremath, Vaibhav
2010-02-03 8:44 ` Mauro Carvalho Chehab [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=4B69376C.1010407@gmail.com \
--to=maurochehab@gmail.com \
--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).