linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: federico.vaga@gmail.com (Federico Vaga)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] modify videobuf2-dma-contig and update sta2x11_vip
Date: Thu, 10 Jan 2013 16:22:39 +0100	[thread overview]
Message-ID: <1491201.YT9CD19YNt@harkonnen> (raw)
In-Reply-To: <1357822010-30419-1-git-send-email-federico.vaga@gmail.com>

We have some new ideas for this new complex architecture (sta2x11) that can 
fix our DMA problems without change the existent code. Obviously, ideas arrive 
when I already sent the patches. Anyway, consider this patch series as an RFC. 
They are not ready for the mainline. I take some time to investigate on the 
architecture side of the project to try to fix our problem.

Anyway, if you consider interesting configure the gfp flags for dma-contig, I 
can propose a v6 series which correct the alloc coherent line.

Sorry for the spam :(

-- 
Federico Vaga

  parent reply	other threads:[~2013-01-10 15:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 12:46 [PATCH v5] modify videobuf2-dma-contig and update sta2x11_vip Federico Vaga
2013-01-10 12:46 ` [PATCH v5 1/3] videobuf2-dma-contig: user can specify GFP flags Federico Vaga
2013-01-10 14:32   ` Federico Vaga
2013-01-10 12:46 ` [PATCH v5 2/3] sta2x11_vip: convert to videobuf2 and control framework Federico Vaga
2013-01-10 12:57   ` Federico Vaga
2013-01-10 14:41     ` Hans Verkuil
2013-01-10 14:58       ` Federico Vaga
2013-01-10 14:01   ` Dan Carpenter
2013-01-10 14:43     ` Federico Vaga
2013-01-10 12:46 ` [PATCH v5 3/3] adv7180: remove {query/g_/s_}ctrl Federico Vaga
2013-01-10 15:22 ` Federico Vaga [this message]
2013-01-10 16:06   ` [PATCH v5] modify videobuf2-dma-contig and update sta2x11_vip Mauro Carvalho Chehab

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=1491201.YT9CD19YNt@harkonnen \
    --to=federico.vaga@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).