[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5204825.yR0kSsoYV4@harkonnen>
Date: Tue, 08 Jan 2013 15:58:37 +0100
From: Federico Vaga <federico.vaga@...il.com>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: Mauro Carvalho Chehab <mchehab@...hat.com>,
Pawel Osciak <pawel@...iak.com>,
Hans Verkuil <hans.verkuil@...co.com>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
Giancarlo Asnaghi <giancarlo.asnaghi@...com>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v4 1/3] videobuf2-dma-contig: user can specify GFP flags
> Ok, then I would simply pass the flags from the driver without any
> alternation
> in the allocator itself, so drivers can pass 'GFP_KERNEL' or
> 'GFP_KERNEL | GFP_DMA' depending on their preference. Please also update
> all
> the existing clients of vb2_dma_dc allocator.
I taked a look at drivers that use dma-contig. They use the structure
vb2_alloc_ctx which is just a name, there is not a real vb2_alloc_ctx
structure implementation. "Now" driver must gain access to vb2_dc_conf to set
the correct flags.
I have the following ideas:
1. replace all the names and expose vb2_dc_conf to all drivers (like dma-
sg, it export vb2_dma_sg_desc to all its users)
2. create an helper which configure flags. This maintain the vb2_dc_conf
private
vb2_set_mem_flags(struct vb2_alloc_ctx *alloc_ctx, gfp_t flags)
3. rename vb2_dc_conf to vb2_alloc_ctx because it is an implementation
vb2_alloc_ctx and (at the moment) it is used only by dma-contig
--
Federico Vaga
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists