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  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]
Date:   Fri, 10 Aug 2018 12:11:19 +0200
From:   Linus Walleij <>
To:     Janusz Krzysztofik <>
Cc:     Boris Brezillon <>,
        Jonathan Corbet <>,
        Miquèl Raynal <>,
        Richard Weinberger <>,
        David Woodhouse <>,
        Brian Norris <>,
        Mark Vasut <>,
        ext Tony Lindgren <>,
        Aaro Koskinen <>,
        Linux ARM <>,
        Linux-OMAP <>,,,
        "open list:GPIO SUBSYSTEM" <>,
        "" <>
Subject: Re: [RFC PATCH v2 04/12] mtd: rawnand: ams-delta: request data port
 GPIO resource

On Tue, Aug 7, 2018 at 12:29 AM Janusz Krzysztofik <> wrote:

> Data port used by the driver is actually an OMAP MPUIO device, already
> under control of gpio-omap driver.  For that reason we used to not
> request the memory region of the port as that would fail because the
> region is already busy.  Despite that, we are still accessing the port
> by just ioremapping it and performing read/write operations.  Moreover,
> we are doing that without any proteciton from other users legally
> manipulating the port pins over GPIO API.
> The plan is to convert the driver to access the port over functions
> exposed by the gpio-omap driver.  Before that happens, already prevent
> from other users accessing the port pins by requesting an array of its
> GPIO descriptors.
> Signed-off-by: Janusz Krzysztofik <>

Reviewed-by: Linus Walleij <>

Linus Walleij

Powered by blists - more mailing lists