From patchwork Mon Sep 7 02:41:46 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Chris Packham X-Patchwork-Id: 1358531 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=23.128.96.18; helo=vger.kernel.org; envelope-from=linux-gpio-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=pass (p=none dis=none) header.from=alliedtelesis.co.nz Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=alliedtelesis.co.nz header.i=@alliedtelesis.co.nz header.a=rsa-sha256 header.s=mail181024 header.b=Om8O6usK; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by ozlabs.org (Postfix) with ESMTP id 4BlCGx45Jgz9sTS for ; Mon, 7 Sep 2020 12:42:01 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726362AbgIGCl7 (ORCPT ); Sun, 6 Sep 2020 22:41:59 -0400 Received: from gate2.alliedtelesis.co.nz ([202.36.163.20]:44534 "EHLO gate2.alliedtelesis.co.nz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726259AbgIGCl4 (ORCPT ); Sun, 6 Sep 2020 22:41:56 -0400 Received: from mmarshal3.atlnz.lc (mmarshal3.atlnz.lc [10.32.18.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by gate2.alliedtelesis.co.nz (Postfix) with ESMTPS id 1058C80719; Mon, 7 Sep 2020 14:41:52 +1200 (NZST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alliedtelesis.co.nz; s=mail181024; t=1599446512; bh=Hf7VVuMu9cFRktO7FXy7LMQ9Jztv9177X3UOd6CQzZw=; h=From:To:Cc:Subject:Date; b=Om8O6usK2nM5bUfaAOv4CKKh/Wcwol1+907/PJv+TT4Q8NC/V4t4oyOQ4rRmrtqR6 9jDcGBzjXZ2aSuI5lKXJjslg6savSSTCxOg6OPN07JuS5A0CerXMx8wkdwkQjcI1XZ OWi0seMzaw/k+ZzwZfxu/p7fIjB6jEU6yPqCL/2eX9t8lKVPzAZP+uYBBdp51jSvxa LbjcSLxnLVGwsOKXZ4UrkJ06V4y/7+MhVofAHfLOlaP+kCcKAZ6uT7xASPkkso+yjc g0gEX3l0at/3fynbSR8C37XDlNmaBsI3sjlmZYsU0OURPxhH9YCkWg3sVjqja3Toav 7F881PLYoUYjw== Received: from smtp (Not Verified[10.32.16.33]) by mmarshal3.atlnz.lc with Trustwave SEG (v7,5,8,10121) id ; Mon, 07 Sep 2020 14:41:51 +1200 Received: from chrisp-dl.ws.atlnz.lc (chrisp-dl.ws.atlnz.lc [10.33.22.20]) by smtp (Postfix) with ESMTP id 8582313EEB7; Mon, 7 Sep 2020 14:41:51 +1200 (NZST) Received: by chrisp-dl.ws.atlnz.lc (Postfix, from userid 1030) id C36DD280060; Mon, 7 Sep 2020 14:41:51 +1200 (NZST) From: Chris Packham To: jason@lakedaemon.net, andrew@lunn.ch, gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com, robh+dt@kernel.org, linus.walleij@linaro.org Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Packham Subject: [PATCH 0/3] 98dx3236 i2c related fixes Date: Mon, 7 Sep 2020 14:41:46 +1200 Message-Id: <20200907024149.20001-1-chris.packham@alliedtelesis.co.nz> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 x-atlnz-ls: pat Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org I noticed these while adding support for i2c recovery for a couple of our boards. They date back to when I initially added support for the 98dx3236. They probably haven't been causing a problem because the HW defaults are correct and unless you attempt to use the specific pinctrl functions there won't be a problem. Chris Packham (3): pinctrl: mvebu: Fix i2c sda definition for 98DX3236 ARM: dts: Remove non-existent i2c1 from 98dx3236 ARM: dts: Add i2c0 pinctrl information for 98dx3236 arch/arm/boot/dts/armada-xp-98dx3236.dtsi | 12 +++++++----- drivers/pinctrl/mvebu/pinctrl-armada-xp.c | 2 +- 2 files changed, 8 insertions(+), 6 deletions(-)