Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1572446imm; Sat, 4 Aug 2018 06:17:21 -0700 (PDT) X-Google-Smtp-Source: AAOMgpd29DJTJVzncWtKwDIhfGUooV1xs5aNDHGwplhVRjWdfM+W4+SRBW4BqocnVuLz3TUeVrnj X-Received: by 2002:a63:686:: with SMTP id 128-v6mr7622507pgg.338.1533388641279; Sat, 04 Aug 2018 06:17:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533388641; cv=none; d=google.com; s=arc-20160816; b=VIw7g045IPrA468KpwTH4xfxb9EG2hcPiW06lCPSWqXS6mH2z5yXnhyWFU+MgZy+7O ZtdbtRnkz+o72/OWQJ00fPoq+hw0G3DHy1uWj+4oAS84KlERQGvRf/ArIiGUH2fQAUdK SCxAYizu1NTr3XAcYHVt1nVm3qGOVPGoDGWBxuIsDGnaMtZrjmbNXyCCK3TdpRlbJ38J Z1ctB6IKHu91reCXhvBfqy5sqAjZCrPWNlWrLv1XCXVXJxV90h/DiWwuOul2Q3xgWltq H8+q6vtPrqAPYh10CXjGfMCP6r0U5BcW0MYE7qxBIGB9PsiV+ugu0T3iBbEXbax/TXf/ ebwA== 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:message-id:date:subject:cc:to:from :arc-authentication-results; bh=dEJbPNotRL9YojgKVOztAom0jX1Tc5GEbUYiBJoeiK4=; b=LBEW1OwcSI9IHpyDykS5Pn64M3BBcOyZBU413RiBan42cgxiVnPz8jsMiOitL7FkP8 Z+1rjH6jW4LXNvcUvocqUoGM4rKY6rnWjemVWhCi7UtNKOD3Ot+bdnFZm6AAt/adCQII mb6kblojiqrB0oJoRtDJXZXl6Fy97aBWexNUk6MckVDxli+5oBI41jikb7CUIFMkgKol T2Cc3PANVJaLdJtjmJwXZSCCRagVa6iTj3ehA1qy32QxWOXh+A79gu3pRjIyco+DlIG1 LsjgIXG7FajfnaK5Jyu6J3TDHm+snTe4dHLBaoZzyBCYO2r6rUE18XDmobPDWQ73RhAr OZMg== 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 o5-v6si5694938plk.25.2018.08.04.06.17.04; Sat, 04 Aug 2018 06:17:21 -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 S1729600AbeHDPQy (ORCPT + 99 others); Sat, 4 Aug 2018 11:16:54 -0400 Received: from gloria.sntech.de ([185.11.138.130]:59450 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726871AbeHDPQx (ORCPT ); Sat, 4 Aug 2018 11:16:53 -0400 Received: from wd0970.dip.tu-dresden.de ([141.76.111.202] helo=phil.localnet) by gloria.sntech.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1flwPa-0003JK-5Z; Sat, 04 Aug 2018 15:16:02 +0200 From: Heiko Stuebner To: djw@t-chip.com.cn Cc: linux-rockchip@lists.infradead.org, Wayne Chou , Simon Xue , David Wu , Finley Xiao , devicetree@vger.kernel.org, Klaus Goger , Sugar Zhang , linux-kernel@vger.kernel.org, Robin Murphy , Rob Herring , Rocky Hao , Will Deacon , Mark Rutland , Catalin Marinas , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v4 2/4] arm64: dts: rockchip: add GRF GPIO controller to rk3328 Date: Sat, 04 Aug 2018 15:16:01 +0200 Message-ID: <4016409.aba6YNvtTb@phil> In-Reply-To: <1533016762-5268-3-git-send-email-djw@t-chip.com.cn> References: <1533016762-5268-1-git-send-email-djw@t-chip.com.cn> <1533016762-5268-3-git-send-email-djw@t-chip.com.cn> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Levin, Am Dienstag, 31. Juli 2018, 07:59:20 CEST schrieb djw@t-chip.com.cn: > From: Levin Du > > Adding a GRF GPIO controller labled "grf_gpio" to rk3328, currently > providing access to the GPIO_MUTE pin, which is manupulated by the > GRF_SOC_CON10 register. > > The GPIO_MUTE pin is referred to as <&grf_gpio 0>. > > Signed-off-by: Levin Du applied to my dts64 branch, with 2 changes: - reordered, please sort nodes without address alphabetically - removed default disabled status The controlled pin is always present on the soc, so doesn't need to be enabled on a per-board level Heiko