Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2068090ybl; Thu, 15 Aug 2019 06:07:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqxgfGwFUK3GuZbkp9hp4Jml2Bw6vqe3pWFD1K0XTIcovQJb5Fej82f1BdfmklSGnUI27UVn X-Received: by 2002:a17:902:b905:: with SMTP id bf5mr3933156plb.342.1565874438273; Thu, 15 Aug 2019 06:07:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565874438; cv=none; d=google.com; s=arc-20160816; b=RU0t1gAnknZGBNLTExjaLDxz0V5EWsKib3t9uZuFOE+MGMv+SN9lwh5ZDxMOVtLBHa 4P8FzVXkn3r4O1mPMbHusrZWdmS9K48uhVBfB0uJAOLvxHc3w390n7IXwSpFhcBLIS8G NHfz1XpG1jRJuYU+Iok7dCTKyuyFLsEshlBFrJjIX/iVNqWV9IVeCrf+7ErFTidQG1Ls ARp/Vu/97nmofpDlbwIlfMllsJYrEyZEMJf3ixHPyBG+zYNy55aAnU4efqMZwIS8BDnl NrGEMscJ0A07E/BjerPsMesTjNH1/28rwTV5SZWkQrD7asoa9awjBh+e62OhRTx3Tq3+ u8Kw== 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; bh=xJppxc2qr9Ve4qpv/m+HZWWTRCQgGU6LMkmSc8X28FU=; b=SInvK6fiCyxB8U75vLKft6W43XUfmZuo60Zx9J/++r11buh1nn5VLyulHSTmy20Tnw rqv+YQS6H4XjA6PrqfR3g54qTRDQQ6ukfWvqSNZB0s29s3VWqm5Q+lrQB0MlxaZofHOy Q97zGHdo6M99JAUavxPaL7uHyWFTn9ktyO/9Rd0ak8dwVEPRWwytWUUtA1GQiPNZ+Gp3 S7hHAw1xx8EGPw5s1Nb4o3RwF0TydGtscfWMcH9f/u6d/OinaSN58TDZSNPKnTpxodv7 LCebZAGcMA9lZ+HcfcXhLp1ZKooMijOO+3VQ2luN3JvDPNnr/5+bG9ysB4oCu2ZLyQ2R jfZw== 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 w198si1977214pfd.106.2019.08.15.06.06.55; Thu, 15 Aug 2019 06:07:18 -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 S1731719AbfHONFb (ORCPT + 99 others); Thu, 15 Aug 2019 09:05:31 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:40855 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730304AbfHONFa (ORCPT ); Thu, 15 Aug 2019 09:05:30 -0400 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1hyFRX-0004uh-TQ; Thu, 15 Aug 2019 15:05:27 +0200 Message-ID: <1565874327.3011.11.camel@pengutronix.de> Subject: Re: [PATCH] reset: Add driver for dispmix reset From: Philipp Zabel To: Fancy Fang , "shawnguo@kernel.org" , "s.hauer@pengutronix.de" Cc: "festevam@gmail.com" , "kernel@pengutronix.de" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , dl-linux-imx Date: Thu, 15 Aug 2019 15:05:27 +0200 In-Reply-To: References: <20190625055557.7507-1-chen.fang@nxp.com> <1561474623.5559.4.camel@pengutronix.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Fancy, On Wed, 2019-06-26 at 06:46 +0000, Fancy Fang wrote: > Hi Philipp, > > Thanks for your comments. And please see my answers below. > [...] > > +Specifying sft-rstn control of devices > > +====================================== > > + > > +Device nodes in Display Mix should specify the reset channel required > > +in their "resets" property, containing a phandle to the sft-rstn > > +device node and an index to specify which channel to use, as > > +described in Documentation/devicetree/bindings/reset/reset.txt. > > + > > +example: > > + > > + lcdif_resets: lcdif-resets { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + #reset-cells = <0>; > > + > > + lcdif-soft-resetn { > > + compatible = "lcdif,soft-resetn"; > > + resets = <&dispmix_sft_rstn IMX8MN_LCDIF_APB_CLK_RESET>, > > + <&dispmix_sft_rstn > > + IMX8MN_LCDIF_PIXEL_CLK_RESET>; > > From these names, on i.MX8MN these look like they could be an internal property of the DISPMIX clocks provided to the submodules. But on i.MX8MM the soft reset bits do look like actual module resets. Can you confirm whether this is true? > [FF] I'll check this with the IC designer, and I'll let you know the result when I get the answer. Did you get some feedback on what these resets actually are? I'm asking because I'm wondering about how to best support VPUMIX for the three VPU cores on i.MX8MM. The VPUMIX seems to have a SOFT_RESET register and a CLOCK_ENABLE register, each with three bits, one bit for each VPU. I'd be interested in knowing what these actually reset / gate as well. regards Philipp