[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170710125210.GK29638@localhost>
Date: Mon, 10 Jul 2017 14:52:10 +0200
From: Johan Hovold <johan@...nel.org>
To: Anatolij Gustschin <agust@...x.de>
Cc: Lee Jones <lee.jones@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Alan Tull <atull@...nel.org>,
Moritz Fischer <moritz.fischer@...us.com>,
linux-gpio@...r.kernel.org, linux-fpga@...r.kernel.org,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
David Laight <David.Laight@...lab.com>
Subject: Re: [PATCH 1/3] mfd: Add support for FTDI FT232H devices
On Thu, Jul 06, 2017 at 10:49:16PM +0200, Anatolij Gustschin wrote:
> Add USB part with common functions for USB-GPIO/I2C/SPI master
> adapters. These allow communication with chip's control, transmit
> and receive endpoints and will be used by various FT232H drivers.
> +static const struct mfd_cell ftdi_cells[] = {
> + { .name = "ftdi-cbus-gpio", },
> + { .name = "ftdi-mpsse-i2c", },
> + { .name = "ftdi-mpsse-spi", },
> + { .name = "ftdi-fifo-fpp-mgr", },
> +};
Correct me if I'm wrong, but aren't these modes really mutually
exclusive, possibly with exception of cbus-gpio (some pins are at least
available as GPIOs in MPSSE mode)? Then MFD is not is not the right fit
here either.
And as David Laight already pointed out, your ftdi-fifo-fpp-mgr driver
seems too application specific for a generic chip like this.
Johan
Powered by blists - more mailing lists