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: <070c5650-3f48-6533-b977-b5d8a8b322b8@gmail.com>
Date:   Wed, 4 May 2022 22:50:32 +0300
From:   Markuss Broks <markuss.broks@...il.com>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Pavel Machek <pavel@....cz>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Christophe JAILLET <christophe.jaillet@...adoo.fr>,
        Linus Walleij <linus.walleij@...aro.org>,
        Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
        Linux LED Subsystem <linux-leds@...r.kernel.org>,
        devicetree <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7 0/2] Make AUX gpio pin optional for ktd2692

Hi Andy,

On 5/4/22 22:44, Andy Shevchenko wrote:
> On Wed, May 4, 2022 at 9:35 PM Markuss Broks <markuss.broks@...il.com> wrote:
>> Some appliances of ktd2692 don't have the AUX pin connected to
>> a GPIO. Specifically, Samsung Galaxy J5 (2015), which uses ktd2692
>> for driving the front flash LED, has the pin not connected anywhere on
>> schematics. Make specifying the AUX pin optional, since it is additional
>> functionality and only affects amount of current going through the LED.
> the amount
>
>> Also convert the txt device-tree bindings to yaml and pick up maintenance
>> over the yaml binding and the driver itself.
> ...
>
>> v7:
>> - drop the MAINTAINERS part
> I'm not sure why it happened.
Pavel asked me to drop the MAINTAINERS part for now.
>
> What I mentioned is to create a series out of 4 (four) patches:
> 1) fix the potential issue with the repetitive message;
Bummer, totally forgot about that, thank you for a reminder!
> 2) update DT;
> 3) switch to optional GPIO;
> 4) update MAINTAINERS.
>
>
- Markuss

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ