[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200907024149.20001-1-chris.packham@alliedtelesis.co.nz>
Date: Mon, 7 Sep 2020 14:41:46 +1200
From: Chris Packham <chris.packham@...iedtelesis.co.nz>
To: jason@...edaemon.net, andrew@...n.ch, gregory.clement@...tlin.com,
sebastian.hesselbarth@...il.com, robh+dt@...nel.org,
linus.walleij@...aro.org
Cc: linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: [PATCH 0/3] 98dx3236 i2c related fixes
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(-)
--
2.28.0
Powered by blists - more mailing lists