linux-kernel - Re: [PATCH 0/8] Utilize iomap interface for PC104 and friends

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220514151859.692928dc@jic23-huawei>
Date:   Sat, 14 May 2022 15:18:59 +0100
From:   Jonathan Cameron <jic23@...nel.org>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     William Breathitt Gray <william.gray@...aro.org>,
        linux-iio <linux-iio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        schnelle@...ux.ibm.com, David Laight <David.Laight@...lab.com>,
        macro@...am.me.uk, Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH 0/8] Utilize iomap interface for PC104 and friends

On Sat, 14 May 2022 14:57:49 +0200
Bartosz Golaszewski <brgl@...ev.pl> wrote:

> On Tue, May 10, 2022 at 7:31 PM William Breathitt Gray
> <william.gray@...aro.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