[PATCH 10/11] soc: ti: k3-ringacc: Use correct device for allocation in RING mode

Grygorii Strashko grygorii.strashko at ti.com
Wed Sep 30 09:58:14 EDT 2020



On 28/09/2020 11:34, Peter Ujfalusi wrote:
> In RING mode the ringacc does not access the ring memory. In this access
> mode the ringacc coherency does not have meaning.
> 
> If the ring is configured in RING mode, then the ringacc itself will not
> access to the ring memory. Only the requester (user) of the ring is going
> to read/write to the memory.
> Extend the ring configuration parameters with a device pointer to be used
> for DMA API when the ring is configured in RING mode.
> 
> Extending the ring configuration struct will allow per ring selection of
> device to be used for allocation, thus allowing per ring coherency.
> 
> To avoid regression, fall back to use the ringacc dev in case the alloc_dev
> is not provided.
> 
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi at ti.com>
> ---
>   drivers/soc/ti/k3-ringacc.c       | 14 +++++++++++---
>   include/linux/soc/ti/k3-ringacc.h |  5 +++++
>   2 files changed, 16 insertions(+), 3 deletions(-)
> 
Reviewed-by: Grygorii Strashko <grygorii.strashko at ti.com>

-- 
Best regards,
grygorii



More information about the linux-arm-kernel mailing list