Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3715011imj; Tue, 19 Feb 2019 08:13:07 -0800 (PST) X-Google-Smtp-Source: AHgI3Ia9BfXvj7gJ0xQv2teaK4BmBOWZ4xBxaTzBTAZ1gKbTYzpdMOapKGZU5FU/DYhrmzqcCtXX X-Received: by 2002:a17:902:b402:: with SMTP id x2mr31454373plr.53.1550592787800; Tue, 19 Feb 2019 08:13:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550592787; cv=none; d=google.com; s=arc-20160816; b=jzvho/iibIpI5W7E8D/XWrGHBIyHBlX0KK/A8oKAhoXgaUiYvatx8SmdRwlkdhCK5C izD4IFi7hOKtFB1Z8DJiEfgf4IbGiE+OAL0qSXmCdMFbzFPdorXy26Qn+5tkLCRj0BwB 1CaBeXS7qMVgiGB4gVeufok4NS36H0is5vBbs09pBREWrorerln9mMGeMzetXCY022+7 KiOicq2KvKaDOc0m7ky1qkpOap9VyIjZIl3U6BM3idz/UxPrgbljAhegpNxWynrznej0 ryf3su5Th2XBHhQg9zCxcYCBY8vf+hV9sotBfEVtBYSP3SbrEf+oNYyDp/ohb8Robtx+ ApPw== 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-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dmarc-filter:dkim-signature :dkim-signature; bh=mFnNnVYf3zt+M+jK8GdX54eiH9Qks9s8RrQqAvs48NA=; b=P5dUnWZABJm61Q7IvRJ5VmHMlgDCnI2jUmsYHm4yzhdQcE97ardiAwgde/Os75+6Dx Ey6bB5cMxYCmFzvCBqmZqiGBVAzOhL5PZUV1mEy6gDhpe7/1VEluuZ7SggIEIkV3WobT SZZlD9/tV9CkQP8j2LDs5upBu8oCHGjTGddTrylrXWuDxcgfw3LNZKIZL53jwExEBjYg TM8XPQQla13jZrTOl5WWw3AuaPVMBJhklf8xJROsGh2TBGrKWsyP2AehZYKAak5jp/u8 vp02J9zo2e5FcopFpx3Bk5E6TQiYjzECTyEYLTuMuJ0usOaoyjGcKlEXjL2ueYt8Ja7C LRHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=OpcATbZk; dkim=pass header.i=@codeaurora.org header.s=default header.b=I6DMudqg; 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 c21si15758004pfd.55.2019.02.19.08.12.52; Tue, 19 Feb 2019 08:13:07 -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=@codeaurora.org header.s=default header.b=OpcATbZk; dkim=pass header.i=@codeaurora.org header.s=default header.b=I6DMudqg; 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 S1728099AbfBSQMZ (ORCPT + 99 others); Tue, 19 Feb 2019 11:12:25 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:57020 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725885AbfBSQMY (ORCPT ); Tue, 19 Feb 2019 11:12:24 -0500 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 249CF607EF; Tue, 19 Feb 2019 16:12:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1550592743; bh=av/QoHAeg/ovIr0Embg2teNlj9SB937zBg4K/g3+yOM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=OpcATbZkHtNzjG/LdhFCqNjBnR2jC1n1EivK29fyf2x7TzX8VCL+voMfj62/lI+Zf BEphFfB+DWPtJT05tEHT+L3t2jahXQ3QmOBIbBN3OwY4ZsLhiCuqVq8hsbkOkpsl/m zXxh8YFjqv5wDBxiyE4pa0bc7pOSqpelK9SJLsHY= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.0 Received: from jcrouse1-lnx.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jcrouse@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 4B48160779; Tue, 19 Feb 2019 16:12:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1550592742; bh=av/QoHAeg/ovIr0Embg2teNlj9SB937zBg4K/g3+yOM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=I6DMudqgbwk0Kdgoe/N74aZlsob4zNnJYc7IWcAWF+Sf35Jjj5+MJz/ZHOlUeigAP uVorqsRg+MGXMDOF1KIBb3Eyohgk5RA6yMhBYddlNncmJR157LzFbXR09ccQYPnLcf QXb0TKoK+1ujdombuRa89wDoKlbB3Q8FxFs5Z8Gs= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 4B48160779 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=jcrouse@codeaurora.org Date: Tue, 19 Feb 2019 09:12:19 -0700 From: Jordan Crouse To: Rob Clark Cc: Rob Herring , freedreno , sboyd@kernel.org, linux-arm-msm , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , dri-devel , David Airlie , Mark Rutland , Daniel Vetter Subject: Re: [PATCH v1 2/6] dt-bindings: drm/msm/a6xx: Add GX power-domain for GMU bindings Message-ID: <20190219161219.GC10863@jcrouse1-lnx.qualcomm.com> Mail-Followup-To: Rob Clark , Rob Herring , freedreno , sboyd@kernel.org, linux-arm-msm , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , dri-devel , David Airlie , Mark Rutland , Daniel Vetter References: <1549296944-17285-1-git-send-email-jcrouse@codeaurora.org> <1549296944-17285-3-git-send-email-jcrouse@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 17, 2019 at 05:43:16PM -0500, Rob Clark wrote: > On Sun, Feb 17, 2019 at 4:08 PM Rob Herring wrote: > > > > On Mon, Feb 4, 2019 at 10:15 AM Jordan Crouse wrote: > > > > > > The GMU should have two power domains defined: "cx" and "gx". "cx" is the > > > actual power domain for the device and "gx" will be attached at runtime > > > to manage reference counting on the GPU device in case of a GMU crash. > > > > power-domains are supposed to be actual regions on a chip die which > > can be power gated. However, they are often abused by being defined in > > terms of kernel PM domains which are not always the same thing. This > > description sounds like the latter case. > > > > iirc (and Jordan can correct me), this arrangement was needed because > normally the GMU does the GPU power control (except for if we manage > to crash it and need to reset the GMU).. > > so maybe not 100% about the actual regions on chip die which can be > gated.. but it is a reality of how hw + fw + sw fit together.. Ack - forgot to add Stephen who knows about this. Rob is correct. The GX domain is real but it is normally controlled by an off-CPU microcontroller. The CPU needs to get involved only when the microcontroller crashes and we need to get things back to normal. So the description of it being an actual region on a chip die is accurate. It sounds like I need to describe the hardware better in the bindings document. Jordan -- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project