Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp300519imm; Tue, 24 Jul 2018 19:42:12 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcA6ukEKDoeKwT/NSUsJPuQ5iSkyU3o32y+0DG5WGD4nbgmJNxQO4DEXlQoVMmSmT6//7u2 X-Received: by 2002:a17:902:e088:: with SMTP id cb8-v6mr5055958plb.189.1532486532792; Tue, 24 Jul 2018 19:42:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532486532; cv=none; d=google.com; s=arc-20160816; b=UZ7vhAll3sKZvkcReYlAXMaaieE95KsnbevMxnS9ww0MIAHKko48ctkB1QDeIIl1AL dodoVnKyaSBsXPx9ZKa2ddTqU3KRn6nH7wO4qqmgJW0yskG2LGhDBkZdhUPiBeFStyWk 5Ev//6XYYuAecKmImI+NO1u7SuYB6ouQB9a2NVfqA8clX5w2Gw1wHL0s23lL63kNOr8j YgQUrOlBlWGCcpIlu/FsLloKlXF5GHXE/JqrAfl38yYQGOEyvtFbUOpyJ48BTPCzzf+E HGBvpCJiThdTSjBiYfOMo6EpPiGiSKsO/OGZu5iDbesg+Ba/u4Pfthsecl7finm16FB5 rJCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :arc-authentication-results; bh=fJ+Ng6+fXVcqnXa1uZY7hTSXlxzlBUmXPLdNnfb02Gc=; b=BwLrHPli5MbZD97AZa4Me1PV4Bjc+gb7z5cjNPl/RdpSMcjjb267ENsVWL2LbQcBdo YN30cEC13aDbVurwCMAaWqJVOIdCWquj06Cbxmjhq6301rm8UMl/m1Qjqo2UT9C7grpV eZemNfIxfrmRHlcnZV32rIOBm9QhSk4RSjwPlENO59SJ7IQUvlLlPBZ7IYN9rE6wYFYQ Xo4VsvpNpuPje1iBd8YMbWx7yVf4vSUtUmRK171xvonltlSBN75bSZp7/jBJ7qS42Fx0 TfPobKU9h1QJ764nZDgVT1jj8hm5QMCvvPVg/AZPrN0y2wHF1gwYm30hY/RRDQqLPWfn 0TUg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v37-v6si12115125plg.486.2018.07.24.19.41.57; Tue, 24 Jul 2018 19:42:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388536AbeGYDub (ORCPT + 99 others); Tue, 24 Jul 2018 23:50:31 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:24743 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S2388420AbeGYDub (ORCPT ); Tue, 24 Jul 2018 23:50:31 -0400 X-UUID: eed5b49cfb8f4c0b9ff3d9cd36235ed4-20180725 Received: from mtkcas08.mediatek.inc [(172.21.101.126)] by mailgw01.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1842499235; Wed, 25 Jul 2018 10:40:57 +0800 Received: from MTKCAS06.mediatek.inc (172.21.101.30) by mtkmbs01n2.mediatek.inc (172.21.101.79) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 25 Jul 2018 10:40:55 +0800 Received: from [172.21.77.4] (172.21.77.4) by MTKCAS06.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1210.3 via Frontend Transport; Wed, 25 Jul 2018 10:40:55 +0800 Message-ID: <1532486454.9280.12.camel@mtksdaap41> Subject: Re: [PATCH v1 06/15] drm/mediatek: add memory mode for RDMA From: CK Hu To: Stu Hsieh CC: Philipp Zabel , David Airlie , Matthias Brugger , , , , , Date: Wed, 25 Jul 2018 10:40:54 +0800 In-Reply-To: <1532420235-22268-7-git-send-email-stu.hsieh@mediatek.com> References: <1532420235-22268-1-git-send-email-stu.hsieh@mediatek.com> <1532420235-22268-7-git-send-email-stu.hsieh@mediatek.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Stu: On Tue, 2018-07-24 at 16:17 +0800, Stu Hsieh wrote: > This patch add memory mode for RDMA > > If use RDMA to read data from memory, it should set memory mode to RDMA > > Signed-off-by: Stu Hsieh > --- > drivers/gpu/drm/mediatek/mtk_disp_rdma.c | 16 +++++++++++++++- > 1 file changed, 15 insertions(+), 1 deletion(-) > [...] > static inline struct mtk_disp_rdma *comp_to_rdma(struct mtk_ddp_comp *comp) > @@ -111,7 +116,8 @@ static void mtk_rdma_start(struct mtk_ddp_comp *comp) > > static void mtk_rdma_stop(struct mtk_ddp_comp *comp) > { > - rdma_update_bits(comp, DISP_REG_RDMA_GLOBAL_CON, RDMA_ENGINE_EN, 0); > + writel(RDMA_SOFT_RESET, comp->regs + DISP_REG_RDMA_GLOBAL_CON); > + writel(0, comp->regs + DISP_REG_RDMA_GLOBAL_CON); Without reset, what happen to dram mode? Why direct link mode need not this reset? > } > > static void mtk_rdma_config(struct mtk_ddp_comp *comp, unsigned int width, > @@ -121,10 +127,18 @@ static void mtk_rdma_config(struct mtk_ddp_comp *comp, unsigned int width, > unsigned int threshold; > unsigned int reg; > struct mtk_disp_rdma *rdma = comp_to_rdma(comp); > + bool *rdma_memory_mode = comp->comp_mode; > > rdma_update_bits(comp, DISP_REG_RDMA_SIZE_CON_0, 0xfff, width); > rdma_update_bits(comp, DISP_REG_RDMA_SIZE_CON_1, 0xfffff, height); > > + if (*rdma_memory_mode == true) { > + rdma_update_bits(comp, DISP_REG_RDMA_SIZE_CON_0, 0xff0000, > + MATRIX_INT_MTX_SEL_DEFAULT); > + rdma_update_bits(comp, DISP_REG_RDMA_GLOBAL_CON, > + RDMA_MODE_MEMORY, RDMA_MODE_MEMORY); > + } > + I would like this to be a kind of 'layer' config. In some SoC, one layer of OVL could switch to direct link input or dram input. So I think it's better to move this setting into some layer interface. Regards, CK > /* > * Enable FIFO underflow since DSI and DPI can't be blocked. > * Keep the FIFO pseudo size reset default of 8 KiB. Set the