Received: by 10.192.165.148 with SMTP id m20csp3566965imm; Mon, 23 Apr 2018 08:38:41 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+IoL8R9ySw4Kg9C97QA5QtRsxDsQkvDTM0pXkDcOype2xdiIC7TcHZmOYJI6mAjPVMVQly X-Received: by 10.98.93.20 with SMTP id r20mr20535269pfb.53.1524497921499; Mon, 23 Apr 2018 08:38:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524497921; cv=none; d=google.com; s=arc-20160816; b=S5/8zKLUfvqv74yS+jHyvam8r3zo748O5r+bmvUhGCfXW+f/35z2VJg0AZIXVfOe5O Etp+P7ryr6PPvCQyEcvQHbrhR3d2LccAgmlHAmLJrzzcgBKlpz+ESzB9fd7Pt7PML8qN uvo9GxWRlO6v7cfdBrqW/GryqsG5eGWoy92gkkFJUtDAGw9DUnpkPE57rFgQwRe+xNsk gdkFUEZdob4LzDO0X9tWghcWLxZ4fgsMk0tpLG1ciKfUMtLTkk7kyvMj2rVFIeGa33dv 2sZy/FWPqllom+tYC1GA2cCLDg10wQM2qlnrJRCjJSXGmacHp037iWqC4lB+/iY6SY6i PzRA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=J6KnqDmkVEGQcU0DHhM5I5TLO9uJkGCDtDwUpuab+Cg=; b=zs26LlZT7O8S83AX73tfhBbVI8sQcPwZcpq3vDmc4rFJ4RgsX5Wa0IQPyeInmayLYa 8VzzoaO1/J2IHFJoK1yDGIw7TRKuHhhRpmqSBoCbIglyjFPJpvrO2fwiXCg0FVW45uFl sR/ylyc1ack3hqKYNxve7/ux1Ig7CPMqSTZWxEaONy8YDljFlfjqqMq/JvhzzDIaMYTC fa4sW52G4ThJ5Lu4x4r/7orL7BkMqMkpUj2TgxVy+I9BLzDkenyVnGwBzylQaBxMrftk O1lyr7lOgkSf7F3DHgYsoBuO9ekZXNECqtmL2RGlEf75bKm/1++PPlCdV9Vgewzw5+53 Dyeg== 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 m37-v6si12302565pla.346.2018.04.23.08.38.27; Mon, 23 Apr 2018 08:38:41 -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 S1755931AbeDWPgw (ORCPT + 99 others); Mon, 23 Apr 2018 11:36:52 -0400 Received: from foss.arm.com ([217.140.101.70]:42444 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755636AbeDWPgt (ORCPT ); Mon, 23 Apr 2018 11:36:49 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 6DB8C80D; Mon, 23 Apr 2018 08:36:49 -0700 (PDT) Received: from e110455-lin.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3F2653F590; Mon, 23 Apr 2018 08:36:49 -0700 (PDT) Received: by e110455-lin.cambridge.arm.com (Postfix, from userid 1000) id 98E3A680720; Mon, 23 Apr 2018 16:36:47 +0100 (BST) Date: Mon, 23 Apr 2018 16:36:47 +0100 From: Liviu Dudau To: Ayan Kumar Halder Cc: brian.starkey@arm.com, malidp@foss.arm.com, airlied@linux.ie, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, nd@arm.com Subject: Re: [PATCH v2 6/8] drm/arm/malidp: Enable/disable the scaling engine interrupts with memory writeback Message-ID: <20180423153647.GF14661@e110455-lin.cambridge.arm.com> References: <1524495051-3891-1-git-send-email-ayan.halder@arm.com> <1524495051-3891-7-git-send-email-ayan.halder@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1524495051-3891-7-git-send-email-ayan.halder@arm.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 23, 2018 at 03:50:49PM +0100, Ayan Kumar Halder wrote: > Scaling engine interrupts need to be enabled/disabled as and when memwrite > is enabled and disabled. The reason being scaling engine interrupts are > used only by the memory writeout layer. > > This patch depends on: > https://lkml.org/lkml/2017/5/15/695 > > Signed-off-by: Ayan Kumar Halder > > --- > Changes in v2:- > - Removed the change id and modified the commit message > --- > drivers/gpu/drm/arm/malidp_hw.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/gpu/drm/arm/malidp_hw.c b/drivers/gpu/drm/arm/malidp_hw.c > index f5633bc..90d76e4 100644 > --- a/drivers/gpu/drm/arm/malidp_hw.c > +++ b/drivers/gpu/drm/arm/malidp_hw.c > @@ -621,12 +621,14 @@ static int malidp550_enable_memwrite(struct malidp_hw_device *hwdev, > malidp_hw_setbits(hwdev, MALIDP550_SE_MEMWRITE_ONESHOT | MALIDP_SE_MEMWRITE_EN, > MALIDP550_SE_CONTROL); > > + malidp_se_irq_hw_init(hwdev); > return 0; > } > > static void malidp550_disable_memwrite(struct malidp_hw_device *hwdev) > { > u32 base = malidp_get_block_base(hwdev, MALIDP_DE_BLOCK); > + malidp_se_irq_fini(hwdev); > malidp_hw_clearbits(hwdev, MALIDP550_SE_MEMWRITE_ONESHOT | MALIDP_SE_MEMWRITE_EN, > MALIDP550_SE_CONTROL); > malidp_hw_clearbits(hwdev, MALIDP_SCALE_ENGINE_EN, base + MALIDP_DE_DISPLAY_FUNC); We now know that this patch is broken, because it disables interrupts for the writeback after a previous commit has enabled them but before the writeback engine has finished writing, so the better place for enabling and disabling the SE IRQs is in the malidp_pm_{suspend,resume} functions, not here. Only for this patch: NACK. Best regards, Liviu > -- > 2.7.4 > -- ==================== | I would like to | | fix the world, | | but they're not | | giving me the | \ source code! / --------------- ¯\_(ツ)_/¯