[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZn-PV6H+uBcoONt=SThGBAODy-YG=rkx5OX-rcpeE+aw@mail.gmail.com>
Date: Mon, 11 Jul 2022 15:02:10 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: William Breathitt Gray <william.gray@...aro.org>
Cc: brgl@...ev.pl, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, Fred Eckert <Frede@...laser.com>,
John Hentges <jhentges@...esio.com>,
Jay Dolan <jay.dolan@...esio.com>
Subject: Re: [PATCH v2 1/6] gpio: i8255: Introduce the i8255 module
On Fri, Jul 8, 2022 at 1:16 AM William Breathitt Gray
<william.gray@...aro.org> wrote:
> Exposes consumer functions providing support for Intel 8255 Programmable
> Peripheral Interface devices. A CONFIG_GPIO_I8255 Kconfig option is
> introduced; modules wanting access to these functions should select this
> Kconfig option.
>
> Tested-by: Fred Eckert <Frede@...laser.com>
> Cc: John Hentges <jhentges@...esio.com>
> Cc: Jay Dolan <jay.dolan@...esio.com>
> Signed-off-by: William Breathitt Gray <william.gray@...aro.org>
This chip is like 50 years old, but so am I and I am not obsolete, it's about
time that we implement a proper driver for it!
But I suppose you are not really using the actual discrete i8255 component?
This is certainly used as integrated into some bridge or so? (Should be
mentioned in the commit.)
> +config GPIO_I8255
> + tristate
That's a bit terse :D Explain that this is a Intel 8255 PPI chip first developed
in the first half of the 1970ies.
> +++ b/include/linux/gpio/i8255.h
You need to provide a rationale for the separate .h file in the commit
message even if it is clear
how it is used in the following patches.
Yours,
Linus Walleij
Powered by blists - more mailing lists