[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YioEQ3g1LlqEv5BY@lunn.ch>
Date: Thu, 10 Mar 2022 14:59:31 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Chris Packham <chris.packham@...iedtelesis.co.nz>
Cc: linus.walleij@...aro.org, robh+dt@...nel.org,
catalin.marinas@....com, will@...nel.org,
gregory.clement@...tlin.com, sebastian.hesselbarth@...il.com,
kostap@...vell.com, robert.marko@...tura.hr,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v1 2/4] pinctrl: mvebu: pinctrl driver for 98DX2530 SoC
On Thu, Mar 10, 2022 at 04:00:37PM +1300, Chris Packham wrote:
> This pinctrl driver supports the 98DX25xx and 98DX35xx family of chips
> from Marvell. It is based on the Marvell SDK with additions for various
> (non-gpio) pin configurations based on the datasheet.
>
> Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
Hi Chris
Past experience with pinctrl and gpio for mvebu is that developers get
GPI and GPO pins wrong. Are there any pins which are not GPIO but only
a subset, so only GPI or GPO?
Andrew
Powered by blists - more mailing lists