Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1319612yba; Tue, 2 Apr 2019 06:48:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqyqDsJ8gzH4p1DWREkP7etK6ZvCJRfVuU2ohLd+yCf5YJmuJtBMfQUVS+uJFj7zjsuvL3iN X-Received: by 2002:a17:902:1c9:: with SMTP id b67mr68811181plb.176.1554212924549; Tue, 02 Apr 2019 06:48:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554212924; cv=none; d=google.com; s=arc-20160816; b=edsMuYhcdXAfv2bjLCAHfTn8W7VMPhpjjSZIr7m1yEa1f6lM8zckqRm97c0UzvpYht LyFSwnLscUtmINbWvMJhZI4XGVU455szOAJQBH8pAQRpTU0KmxkVAk3vSXiwCS3HRIUQ FgxNObyceXvid0HV5Dexs0bTlYmBnkr5rFeGxtuc0LtRKbb7WEUbAtgS/UdL2QpJQkKZ WnsuU0yMYIccANzL0rOMfyswwhqMEjAmw79ZUtKQODUMQ/UCI/D6q3T7E8mzBOR9DUH7 aPon3iW5MtpANq4x12XUFoo0pXZB9HOnJjp6zhDA5wZNTVhr6LuzTsYR3F1pTd/BLKaL Ya5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=CHe7C5gzhqlRnV+Wh7HZs/0ocQcVziLrdHVuxvPpeS8=; b=U/j/eAW+TAizncDZPNNMm+x+a4xBECzW4fy3ZPd7sG+J28yWLaFfVgtksZwBxV5TOU ZqVU+Fe0CuC13CKFRJXfrcWeIDyZr9yW0lQgxmm/xjl7LcHIwqqRVOX4o3zsPlLoIgc5 mpw4Z2I18klZjfSKqQoA7Q1H1WG1Rq0fVoqftA7r4fuBW9+r0A4sts5/qMaHo0PrQQOe KFq5cPU4pxLFxJfkiFhReSzJSLYdumNTeXRR5ooALf2Gb0LA1bfaJi3DvF+y3ykFadBk Fdm9td9fO5+cFRpFRTuEkQ6duPtThwDT4phGmfP7+ENh+3ALfjLcOrkrnzk1+IFqwSlS sUQA== 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 g5si11113153pfi.60.2019.04.02.06.48.29; Tue, 02 Apr 2019 06:48:44 -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 S1732230AbfDBNrR (ORCPT + 99 others); Tue, 2 Apr 2019 09:47:17 -0400 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:43072 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731410AbfDBNkE (ORCPT ); Tue, 2 Apr 2019 09:40:04 -0400 Received: from [167.98.27.226] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hBJdx-0002or-Bx; Tue, 02 Apr 2019 14:40:01 +0100 Received: from ben by deadeye with local (Exim 4.92) (envelope-from ) id 1hBJdw-0004uY-MU; Tue, 02 Apr 2019 14:40:00 +0100 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, Denis Kirjanov , "Simon Horman" , "Geert Uytterhoeven" Date: Tue, 02 Apr 2019 14:38:27 +0100 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 51/99] pinctrl: sh-pfc: sh7264: Fix PFCR3 and PFCR0 register configuration In-Reply-To: X-SA-Exim-Connect-IP: 167.98.27.226 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.65-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Geert Uytterhoeven commit 1b99d0c80bbe1810572c2cb77b90f67886adfa8d upstream. The Port F Control Register 3 (PFCR3) contains only a single field. However, counting from left to right, it is the fourth field, not the first field. Insert the missing dummy configuration values (3 fields of 16 values) to fix this. The descriptor for the Port F Control Register 0 (PFCR0) lacks the description for the 4th field (PF0 Mode, PF0MD[2:0]). Add the missing configuration values to fix this. Fixes: a8d42fc4217b1ea1 ("sh-pfc: Add sh7264 pinmux support") Signed-off-by: Geert Uytterhoeven Reviewed-by: Simon Horman Signed-off-by: Ben Hutchings --- drivers/pinctrl/sh-pfc/pfc-sh7264.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) --- a/drivers/pinctrl/sh-pfc/pfc-sh7264.c +++ b/drivers/pinctrl/sh-pfc/pfc-sh7264.c @@ -1716,6 +1716,9 @@ static const struct pinmux_cfg_reg pinmu }, { PINMUX_CFG_REG("PFCR3", 0xfffe38a8, 16, 4) { + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, + 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, PF12MD_000, PF12MD_001, 0, PF12MD_011, PF12MD_100, PF12MD_101, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } @@ -1759,8 +1762,10 @@ static const struct pinmux_cfg_reg pinmu 0, 0, 0, 0, 0, 0, 0, 0, PF1MD_000, PF1MD_001, PF1MD_010, PF1MD_011, PF1MD_100, PF1MD_101, 0, 0, - 0, 0, 0, 0, 0, 0, 0, 0 - } + 0, 0, 0, 0, 0, 0, 0, 0, + PF0MD_000, PF0MD_001, PF0MD_010, PF0MD_011, + PF0MD_100, PF0MD_101, 0, 0, + 0, 0, 0, 0, 0, 0, 0, 0 } }, { PINMUX_CFG_REG("PFIOR0", 0xfffe38b2, 16, 1) {