[PATCHv3 net-next 00/22] net: mvpp2: add initial support for PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 01/22] dt-bindings: net: update Marvell PPv2 binding for PPv2.2 support · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 02/22] net: mvpp2: use "dma" instead of "phys" where appropriate · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 03/22] net: mvpp2: remove support for buffer header · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 04/22] net: mvpp2: remove unused register definition MVPP2_TXQ_THRESH_REG · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 05/22] net: mvpp2: remove mvpp2_txq_pend_desc_num_get() function · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 06/22] net: mvpp2: store physical address of buffer in rx_desc->buf_cookie · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 08/22] net: mvpp2: add hw_version field in "struct mvpp2" · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 10/22] net: mvpp2: introduce PPv2.2 HW descriptors and adapt accessors · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 11/22] net: mvpp2: adjust the allocation/free of BM pools for PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 12/22] net: mvpp2: adapt the mvpp2_rxq_*_pool_set functions to PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 13/22] net: mvpp2: adapt mvpp2_defaults_set() to PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 14/22] net: mvpp2: adjust mvpp2_{rxq,txq}_init for PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 15/22] net: mvpp2: handle register mapping and access for PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 16/22] net: mvpp2: handle misc PPv2.1/PPv2.2 differences · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 17/22] net: mvpp2: add AXI bridge initialization for PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 18/22] net: mvpp2: rework RXQ interrupt group initialization for PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 19/22] net: mvpp2: adapt rxq distribution to PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 20/22] net: mvpp2: add support for an additional clock needed for PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
[PATCHv3 net-next 21/22] net: mvpp2: set dma mask and coherent dma mask on PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
RE: [PATCHv3 net-next 21/22] net: mvpp2: set dma mask and coherent dma mask on PPv2.2 · David Laight <hidden> · 2017-03-07
Re: [PATCHv3 net-next 21/22] net: mvpp2: set dma mask and coherent dma mask on PPv2.2 · Thomas Petazzoni <hidden> · 2017-03-07
RE: [PATCHv3 net-next 21/22] net: mvpp2: set dma mask and coherent dma mask on PPv2.2 · David Laight <hidden> · 2017-03-08
[PATCHv3 net-next 22/22] net: mvpp2: finally add the PPv2.2 compatible string · Thomas Petazzoni <hidden> · 2017-03-07

Re: [PATCHv3 net-next 21/22] net: mvpp2: set dma mask and coherent dma mask on PPv2.2

From: Thomas Petazzoni <hidden>
Date: 2017-03-07 18:12:01
Also in: linux-arm-kernel, linux-devicetree

Hello,

On Tue, 7 Mar 2017 17:24:21 +0000, David Laight wrote:

Are the coherent mappings just used for ring structures?
If it might be reasonable to allocate them as a single entity,
thus guaranteeing they all reside in a single 4G region.

Do we have the guarantee that a DMA coherent allocation will not span a
4G boundary?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help