From: Jonathan Cameron <jic23@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: William Breathitt Gray <william.gray@linaro.org>,
linux-iio <linux-iio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
schnelle@linux.ibm.com, David Laight <David.Laight@aculab.com>,
macro@orcam.me.uk, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 0/8] Utilize iomap interface for PC104 and friends
Date: Sat, 14 May 2022 15:18:59 +0100 [thread overview]
Message-ID: <20220514151859.692928dc@jic23-huawei> (raw)
In-Reply-To: <CAMRc=McAe28ZwcGknzrju-PQTEZ7x2XAfoRyfLFMWpgGB8DVLw@mail.gmail.com>
On Sat, 14 May 2022 14:57:49 +0200
Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> On Tue, May 10, 2022 at 7:31 PM William Breathitt Gray
> <william.gray@linaro.org> wrote:
> >
> > PC104 cards and similar devices do not need to access I/O ports directly
> > via inb()/outb() and can instead use the more typical I/O memory
> > ioread8()/iowrite8() accessor calls by first calling ioport_map(). This
> > patchset converts the relevant PC104/ISA card drivers to do such. With
> > these drivers now utilizing I/O memory accessor calls, work can be done
> > to consolidate some similar devices (e.g. 104-idio-16, pci-idio-16,
> > etc.) into a unified driver in a future patchset.
> >
> > This patchset spawned from a suggestion made in another thread titled
> > "gpio: add HAS_IOPORT dependencies":
> > https://lore.kernel.org/all/c3a3cdd99d4645e2bbbe082808cbb2a5@AcuMS.aculab.com/
> >
> > William Breathitt Gray (8):
> > counter: 104-quad-8: Utilize iomap interface
> > gpio: 104-dio-48e: Utilize iomap interface
> > gpio: 104-idi-48: Utilize iomap interface
> > gpio: 104-idio-16: Utilize iomap interface
> > gpio: gpio-mm: Utilize iomap interface
> > gpio: ws16c48: Utilize iomap interface
> > iio: adc: stx104: Utilize iomap interface
> > iio: dac: cio-dac: Utilize iomap interface
> >
> > drivers/counter/104-quad-8.c | 169 +++++++++++++++++---------------
> > drivers/gpio/gpio-104-dio-48e.c | 63 ++++++------
> > drivers/gpio/gpio-104-idi-48.c | 27 ++---
> > drivers/gpio/gpio-104-idio-16.c | 33 ++++---
> > drivers/gpio/gpio-gpio-mm.c | 43 ++++----
> > drivers/gpio/gpio-ws16c48.c | 65 ++++++------
> > drivers/iio/adc/stx104.c | 56 ++++++-----
> > drivers/iio/dac/cio-dac.c | 14 +--
> > 8 files changed, 248 insertions(+), 222 deletions(-)
> >
> >
> > base-commit: ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e
> > --
> > 2.35.3
> >
>
> I don't see any dependencies so applied the GPIO part.
Likewise, I've applied the IIO ones. Initially pushed out as testing
to see if 0-day finds any issues. Given timing, we may well be looking
at next merge window now though.
Thanks,
Jonathan
>
> Bart
next prev parent reply other threads:[~2022-05-14 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 17:30 [PATCH 0/8] Utilize iomap interface for PC104 and friends William Breathitt Gray
2022-05-10 17:30 ` [PATCH 1/8] counter: 104-quad-8: Utilize iomap interface William Breathitt Gray
2022-05-10 17:30 ` [PATCH 2/8] gpio: 104-dio-48e: " William Breathitt Gray
2022-05-10 17:30 ` [PATCH 3/8] gpio: 104-idi-48: " William Breathitt Gray
2022-05-10 17:30 ` [PATCH 4/8] gpio: 104-idio-16: " William Breathitt Gray
2022-05-10 17:30 ` [PATCH 5/8] gpio: gpio-mm: " William Breathitt Gray
2022-05-10 17:30 ` [PATCH 6/8] gpio: ws16c48: " William Breathitt Gray
2022-05-10 17:30 ` [PATCH 7/8] iio: adc: stx104: " William Breathitt Gray
2022-05-10 17:31 ` [PATCH 8/8] iio: dac: cio-dac: " William Breathitt Gray
2022-05-13 20:21 ` [PATCH 0/8] Utilize iomap interface for PC104 and friends Linus Walleij
2022-05-14 12:57 ` Bartosz Golaszewski
2022-05-14 14:18 ` Jonathan Cameron [this message]
2022-05-14 15:08 ` William Breathitt Gray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220514151859.692928dc@jic23-huawei \
--to=jic23@kernel.org \
--cc=David.Laight@aculab.com \
--cc=brgl@bgdev.pl \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=schnelle@linux.ibm.com \
--cc=william.gray@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox