Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220504193439.15938-1-markuss.broks@gmail.com>
In-Reply-To: <20220504193439.15938-1-markuss.broks@gmail.com>
From:   Andy Shevchenko <andy.shevchenko@gmail.com>
Date:   Wed, 4 May 2022 21:44:50 +0200
Message-ID: <CAHp75VeMCiwgTFFy5vGBoWYSw4mGQU6623B1eMr7apJZF_L-kg@mail.gmail.com>
Subject: Re: [PATCH v7 0/2] Make AUX gpio pin optional for ktd2692
To:     Markuss Broks <markuss.broks@gmail.com>
Cc:     Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
        Linus Walleij <linus.walleij@linaro.org>,
        Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
        Linux LED Subsystem <linux-leds@vger.kernel.org>,
        devicetree <devicetree@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, May 4, 2022 at 9:35 PM Markuss Broks <markuss.broks@gmail.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.

What I mentioned is to create a series out of 4 (four) patches:
1) fix the potential issue with the repetitive message;
2) update DT;
3) switch to optional GPIO;
4) update MAINTAINERS.


-- 
With Best Regards,
Andy Shevchenko