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: <m2oa1p6dn6.fsf@baylibre.com>
Date:   Tue, 08 Nov 2016 10:16:13 -0800
From:   Kevin Hilman <khilman@...libre.com>
To:     Axel Haslam <ahaslam@...libre.com>
Cc:     linus.walleij@...aro.org, gnurou@...il.com, nsekhar@...com,
        david@...hnology.com, grygorii.strashko@...com, keerthy@...com,
        linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gpio: davinci: Use unique labels for each gpio chip

Axel Haslam <ahaslam@...libre.com> writes:

> The gpiod framework uses the chip label to match a specific chip.
> The davinci gpio driver, creates several chips using always the same
> label, which is not compatible with gpiod.
>
> To allow platform data to declare gpio lookup tables, and for drivers
> to use the gpiod framework, allocate unique label per registered chip.
>
> Signed-off-by: Axel Haslam <ahaslam@...libre.com>

Acked-by: Kevin Hilman <khilman@...libre.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ