Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3468375ybc; Thu, 14 Nov 2019 09:31:12 -0800 (PST) X-Google-Smtp-Source: APXvYqzWdrHkejWbNyaH/BuPoA9wZs2AGG44aPOX4UjpWP2mmsUssm4Y/+e87C2gcR1Q3bzdn4BA X-Received: by 2002:a05:6402:70e:: with SMTP id w14mr2564377edx.95.1573752672278; Thu, 14 Nov 2019 09:31:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573752672; cv=none; d=google.com; s=arc-20160816; b=WBlLT88AOdhWHqvEQ64vtP1ulQ6C8vGgnOeZRybuqCTNOtxvEXQL7E5R8qY6UN4uMH A2iKSegSDEsXutWqLl7nHpjM67MJl1znUaJdqDqkat9fYyjaB6d23xmnMrxPayQLto5v nVW6X3CMh8eTkG2VvFECZp7Hq3p5st5YqbJclXE4BR5muuFp/QfSclplKFIV2t/4Iad7 zDsQ2n6ZjCeZDTmlXpaJzjeB7qAFRiWdhmm5n1Dv/3EMhu6M3xgq/5OgYB6pmRhSTYpg I43ys5p2SfXUSohW3Au82iBAGU6kDUqoXD3rsCjsVTXL6cGUmlJgjTS0ZyNLUvSSHeEO n8Ug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:user-agent:to:subject:from:cc :references:in-reply-to:content-transfer-encoding:mime-version :message-id:dkim-signature; bh=CcYQV1LmmMin4KfNUQWfqXUn7x+pyW1iTl5f3vQ+Lhw=; b=guDsfyVQ3+CwD+uFFsIiR2rN1f+NDJNz7EjWmAYvyFuScVbr/wqsmAmvR3y4HOVxA2 c23Zz12ZfiGeJ8Bcqzl+AU753sGZMoTZ9EbseKFgF9/ykhWE7fJvCbuXAWMbW9l7NR6t o/zmrbuzZKRofdIDhbnWXW9U4pHGPj0Sy12ezUx4YNaQrasbwhD/1leE9Ty9AcbXOSu/ fNPFsdBduItorw02tNNuiflJKLA0pjZdTBGCUlALlJVuBTm+qYLvBsNdP1F2aRQSb++e PPMZvnBnAu2uZ2VJTz/npP4g+gMwa9LnAA8fMkQ691wEuN+7ep0iXpzGhb6RfRXTl+sV r1Ig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=NxMGYSTt; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i20si3815068ejc.177.2019.11.14.09.30.46; Thu, 14 Nov 2019 09:31:12 -0800 (PST) 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; dkim=pass header.i=@chromium.org header.s=google header.b=NxMGYSTt; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726818AbfKNR3o (ORCPT + 99 others); Thu, 14 Nov 2019 12:29:44 -0500 Received: from mail-pg1-f193.google.com ([209.85.215.193]:34169 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726491AbfKNR3o (ORCPT ); Thu, 14 Nov 2019 12:29:44 -0500 Received: by mail-pg1-f193.google.com with SMTP id z188so4214513pgb.1 for ; Thu, 14 Nov 2019 09:29:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=message-id:mime-version:content-transfer-encoding:in-reply-to :references:cc:from:subject:to:user-agent:date; bh=CcYQV1LmmMin4KfNUQWfqXUn7x+pyW1iTl5f3vQ+Lhw=; b=NxMGYSTtBK4i5RPqbguGXItXdVNjv2nYm1/iGpCOqRIVhhVH6vf7946u7XMPm25GJA q7nWJkt3+Xf/XDjNbHKHgXjXTbJHCI69Wm000ian3oAhz2GlGBNz1DTe9WXQgjh7aurH DMoXuOTRdgV6nuAZHMYwbqnm9praYO+bqeVas= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version :content-transfer-encoding:in-reply-to:references:cc:from:subject:to :user-agent:date; bh=CcYQV1LmmMin4KfNUQWfqXUn7x+pyW1iTl5f3vQ+Lhw=; b=jiZVWooO7h1c/PcD3B1joFUHPQo1yt9AAAcNjhtNZk843flfyYAYV3ExZT0KSshqDG cn6Kroxx/tcVAge/vBOK0EgXotqKUncuDpqN3VP4mRHChv5mF8WrGT+DMkSL23afqu40 cK5KH8BOJhuU8cawbdBJs5BNj5iafO3u1d6pUQJB3x5Zm/D1zcGTZ5g3JNb1z4wNh8/2 GfhV47Fb5k7peQ7qgGFc974RBUnPgmr4ct1D2zqfKMphFOQyLhg549wVmU4J2pkNSnpN rEVsBguD92IyGh0LbTk4Qton0fpCYl0xVbSOwrqJ1iULrZ+gZJB4xwyNGW4mTaHjQ/CJ Uxtw== X-Gm-Message-State: APjAAAUh9QKwYgijJ4mLNoqP9TdQ3Vy6/I7+qU9jE0c65g8QPPEr0suv rMOUQd62tJRPrxibSdU3Clo4UylJNE8= X-Received: by 2002:aa7:8256:: with SMTP id e22mr12167282pfn.247.1573752582247; Thu, 14 Nov 2019 09:29:42 -0800 (PST) Received: from chromium.org ([2620:15c:202:1:fa53:7765:582b:82b9]) by smtp.gmail.com with ESMTPSA id i71sm6900213pfe.103.2019.11.14.09.29.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 14 Nov 2019 09:29:41 -0800 (PST) Message-ID: <5dcd8f05.1c69fb81.bdd4.2b0a@mx.google.com> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <1573710976-27551-1-git-send-email-dhar@codeaurora.org> References: <1573710976-27551-1-git-send-email-dhar@codeaurora.org> Cc: Shubhashree Dhar , linux-kernel@vger.kernel.org, robdclark@gmail.com, seanpaul@chromium.org, hoegsberg@chromium.org, abhinavk@codeaurora.org, jsanka@codeaurora.org, chandanu@codeaurora.org, nganji@codeaurora.org From: Stephen Boyd Subject: Re: [v2] msm: disp: dpu1: add support to access hw irqs regs depending on revision To: Shubhashree Dhar , devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org User-Agent: alot/0.8.1 Date: Thu, 14 Nov 2019 09:29:40 -0800 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Shubhashree Dhar (2019-11-13 21:56:16) > Current code assumes that all the irqs registers offsets can be > accessed in all the hw revisions; this is not the case for some > targets that should not access some of the irq registers. What happens if we read the irq registers that we "should not access"? Does the system reset? It would be easier to make those registers return 0 when read indicating no interrupt and ignore writes so that everything keeps working without having to skip registers. > This change adds the support to selectively remove the irqs that > are not supported in some of the hw revisions. >=20 > Change-Id: I6052b8237b703a1a9edd53893e04f7bd72223da1 Please remove these before sending upstream. > Signed-off-by: Shubhashree Dhar > --- > drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c | 1 + > drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h | 3 +++ > drivers/gpu/drm/msm/disp/dpu1/dpu_hw_interrupts.c | 22 +++++++++++++++++= ----- > drivers/gpu/drm/msm/disp/dpu1/dpu_hw_interrupts.h | 1 + > 4 files changed, 22 insertions(+), 5 deletions(-) >=20 > diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h b/drivers/gpu= /drm/msm/disp/dpu1/dpu_hw_catalog.h > index ec76b868..def8a3f 100644 > --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h > +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.h > @@ -646,6 +646,7 @@ struct dpu_perf_cfg { > * @dma_formats Supported formats for dma pipe > * @cursor_formats Supported formats for cursor pipe > * @vig_formats Supported formats for vig pipe > + * @mdss_irqs Bitmap with the irqs supported by the target Hmm pretty sure there needs to be a colon so that kernel-doc can match this but maybe I'm wrong. > */ > struct dpu_mdss_cfg { > u32 hwversion;