Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp2854942pxk; Mon, 28 Sep 2020 01:37:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxaxEhGPzc976C6g03z7a/qDJUVRxVEfszDTkpCJmVg8kQou7jj6be3okMeNYgZ5CRrlfu3 X-Received: by 2002:aa7:de91:: with SMTP id j17mr489202edv.85.1601282231758; Mon, 28 Sep 2020 01:37:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601282231; cv=none; d=google.com; s=arc-20160816; b=PhYqlnA7Eyfytm5INSpssyM/AcL4zJvqAOULRgLarel3G5iA4JncGgTvO/WcdKu85L n3Aj1vFgPNZXyX1izgbvBAXtBgvGo5oPAdSW7NZPHYo1HWV/VMAy+9FXxROy0AfiFiSP 6N0kf+mGDmEfrQUsOBz5duKIw7a+JF47Q6mXUfnYoz/fdlFRcNLJ6UaonILCVLOMg6GS D/MAZL3PbZvBEDP5eQzqJ3HwvCrplB6YZEAt0CUpEBEdaZ+G0SCT1kHBai5W1lUQoEb2 eFGbuoQBuck5+CNSvCIOi5hX3VDJYVf65uUTyLBu6983AiWUfxH8zwJ4RJTwwSJxWVTs gFOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=7B6HJCik+s1CpDvWuSwrAqHsjfSuMm+sQmZOM5XikIo=; b=TWi+SSZCr6VXXBFXgD1Pjd3MyejrYcPh2u1wwdYaUmGeem5dIV4xvND3lOBPf89p1Q 2S3UXkOdYvmfHxCHSnuiFYmF5Bu6TdT+1/3N1TPsUQvam71eQq+yFOv6S09XMUw9nXis a0EO5get5OwyOWwA0rKgLd6UA0dJR2OVvVyJE9evWFm3l4aMq/Mt/TGFlWpBKY14a/4l 9CmrSeXSvqi0Zq2t+BPP9QQVB2mGvcAAcI0FdrTMUg1h3XvJDJww7xVDRPErL7wKEZz1 KGXVH5lTKdiHBVgBjU8akqDbogrjalMxg5lDNV7UMTwLOxtbRDp7+myhcchQHF+xaRGq +Pjw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="gj/OqB+7"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ml23si174220ejb.242.2020.09.28.01.36.48; Mon, 28 Sep 2020 01:37:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="gj/OqB+7"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726768AbgI1Iep (ORCPT + 99 others); Mon, 28 Sep 2020 04:34:45 -0400 Received: from fllv0016.ext.ti.com ([198.47.19.142]:41434 "EHLO fllv0016.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726691AbgI1Iem (ORCPT ); Mon, 28 Sep 2020 04:34:42 -0400 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0016.ext.ti.com (8.15.2/8.15.2) with ESMTP id 08S8Yckc080061; Mon, 28 Sep 2020 03:34:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1601282078; bh=7B6HJCik+s1CpDvWuSwrAqHsjfSuMm+sQmZOM5XikIo=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=gj/OqB+7aLZGfbDE3et30YcGxhYWIlds1+nLKXp+Nn2lm9VFM4nL772P+CVyFrjMH AJ/8K6NtzPS93DXdRxySk0fdC0eaUBxTSQSpQ6MNHzBr7zYeK1zjVNLp4NxURaJ9XR JE4pQ6jGkCD7mHjipVA+Igq1dd4e3T3qz5ykud9g= Received: from DLEE103.ent.ti.com (dlee103.ent.ti.com [157.170.170.33]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 08S8YcuO070793 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 28 Sep 2020 03:34:38 -0500 Received: from DLEE111.ent.ti.com (157.170.170.22) by DLEE103.ent.ti.com (157.170.170.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3; Mon, 28 Sep 2020 03:34:37 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DLEE111.ent.ti.com (157.170.170.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1979.3 via Frontend Transport; Mon, 28 Sep 2020 03:34:37 -0500 Received: from feketebors.ti.com (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id 08S8YEab065485; Mon, 28 Sep 2020 03:34:35 -0500 From: Peter Ujfalusi To: , , , CC: , , Subject: [PATCH 10/11] soc: ti: k3-ringacc: Use correct device for allocation in RING mode Date: Mon, 28 Sep 2020 11:34:28 +0300 Message-ID: <20200928083429.17390-11-peter.ujfalusi@ti.com> X-Mailer: git-send-email 2.28.0 In-Reply-To: <20200928083429.17390-1-peter.ujfalusi@ti.com> References: <20200928083429.17390-1-peter.ujfalusi@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- drivers/soc/ti/k3-ringacc.c | 14 +++++++++++--- include/linux/soc/ti/k3-ringacc.h | 5 +++++ 2 files changed, 16 insertions(+), 3 deletions(-) diff --git a/drivers/soc/ti/k3-ringacc.c b/drivers/soc/ti/k3-ringacc.c index 9ddd77113c5a..7d0b4092fce8 100644 --- a/drivers/soc/ti/k3-ringacc.c +++ b/drivers/soc/ti/k3-ringacc.c @@ -141,6 +141,7 @@ struct k3_ring_state { * @parent: Pointer on struct @k3_ringacc * @use_count: Use count for shared rings * @proxy_id: RA Ring Proxy Id (only if @K3_RINGACC_RING_USE_PROXY) + * @dma_dev: device to be used for DMA API (allocation, mapping) */ struct k3_ring { struct k3_ring_rt_regs __iomem *rt; @@ -160,6 +161,7 @@ struct k3_ring { struct k3_ringacc *parent; u32 use_count; int proxy_id; + struct device *dma_dev; }; struct k3_ringacc_ops { @@ -508,11 +510,12 @@ int k3_ringacc_ring_free(struct k3_ring *ring) k3_ringacc_ring_free_sci(ring); - dma_free_coherent(ringacc->dev, + dma_free_coherent(ring->dma_dev, ring->size * (4 << ring->elm_size), ring->ring_mem_virt, ring->ring_mem_dma); ring->flags = 0; ring->ops = NULL; + ring->dma_dev = NULL; if (ring->proxy_id != K3_RINGACC_PROXY_NOT_USED) { clear_bit(ring->proxy_id, ringacc->proxy_inuse); ring->proxy = NULL; @@ -633,8 +636,12 @@ int k3_ringacc_ring_cfg(struct k3_ring *ring, struct k3_ring_cfg *cfg) switch (ring->mode) { case K3_RINGACC_RING_MODE_RING: ring->ops = &k3_ring_mode_ring_ops; + ring->dma_dev = cfg->dma_dev; + if (!ring->dma_dev) + ring->dma_dev = ringacc->dev; break; case K3_RINGACC_RING_MODE_MESSAGE: + ring->dma_dev = ringacc->dev; if (ring->proxy) ring->ops = &k3_ring_mode_proxy_ops; else @@ -646,7 +653,7 @@ int k3_ringacc_ring_cfg(struct k3_ring *ring, struct k3_ring_cfg *cfg) goto err_free_proxy; } - ring->ring_mem_virt = dma_alloc_coherent(ringacc->dev, + ring->ring_mem_virt = dma_alloc_coherent(ring->dma_dev, ring->size * (4 << ring->elm_size), &ring->ring_mem_dma, GFP_KERNEL); if (!ring->ring_mem_virt) { @@ -669,12 +676,13 @@ int k3_ringacc_ring_cfg(struct k3_ring *ring, struct k3_ring_cfg *cfg) return 0; err_free_mem: - dma_free_coherent(ringacc->dev, + dma_free_coherent(ring->dma_dev, ring->size * (4 << ring->elm_size), ring->ring_mem_virt, ring->ring_mem_dma); err_free_ops: ring->ops = NULL; + ring->dma_dev = NULL; err_free_proxy: ring->proxy = NULL; return ret; diff --git a/include/linux/soc/ti/k3-ringacc.h b/include/linux/soc/ti/k3-ringacc.h index 5a472eca5ee4..658dc71d2901 100644 --- a/include/linux/soc/ti/k3-ringacc.h +++ b/include/linux/soc/ti/k3-ringacc.h @@ -67,6 +67,9 @@ struct k3_ring; * few times. It's usable when the same ring is used as Free Host PD ring * for different flows, for example. * Note: Locking should be done by consumer if required + * @dma_dev: Master device which is using and accessing to the ring + * memory when the mode is K3_RINGACC_RING_MODE_RING. Memory allocations + * should be done using this device. */ struct k3_ring_cfg { u32 size; @@ -74,6 +77,8 @@ struct k3_ring_cfg { enum k3_ring_mode mode; #define K3_RINGACC_RING_SHARED BIT(1) u32 flags; + + struct device *dma_dev; }; #define K3_RINGACC_RING_ID_ANY (-1) -- Peter Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki