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: <20161019124112.GK1722@lahna.fi.intel.com>
Date:   Wed, 19 Oct 2016 15:41:12 +0300
From:   Mika Westerberg <mika.westerberg@...ux.intel.com>
To:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Linus Walleij <linus.walleij@...aro.org>
Cc:     Alexandre Courbot <gnurou@...il.com>, linux-acpi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] ACPI / gpio: Updates to properties

On Fri, Sep 23, 2016 at 05:57:05PM +0300, Mika Westerberg wrote:
> Hi,
> 
> This series brings couple of useful GPIO related properties from Device
> Tree to ACPI _DSD device properties:
> 
>   - Names for GPIO lines
>   - GPIO hogging
>   - Holes in GPIO property lists
> 
> We are using these to get Intel Galileo better supported in the mainline
> kernel (but these may be useful for other boards as well). For example SPI
> chip select on Galileo is connected to a GPIO line so we need to be able to
> describe it in ACPI, and at the same time allow native chip selects.
> 
> GPIO hogging can be used to set initial state of certain GPIOs available on
> the headers regardless of the BIOS settings (which may be wrong as it knows
> nothing about which devices have been connected).
> 
> Mika Westerberg (5):
>   ACPI / documentation: Use recommended name in GPIO property names
>   ACPI / gpio: Add support for naming GPIOs
>   ACPI / gpio: Add hogging support
>   ACPI / property: Allow holes in reference properties
>   ACPI / gpio: Allow holes in list of GPIOs for a device

Any comments on the GPIO patches in this series?

At least the last one does not add any new bindings so it should be fine
to apply.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ