Received-SPF: pass (google.com: domain of linux-kernel+bounces-141352-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Lee Jones <lee@kernel.org>
To: pavel@ucw.cz, lee@kernel.org, matthias.bgg@gmail.com, 
 angelogioacchino.delregno@collabora.com, ChiaEn Wu <chiaen_wu@richtek.com>
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org, 
 linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, 
 peterwu.pub@gmail.com, cy_huang@richtek.com
In-Reply-To: <28FE6F1712799128000.chiaen_wu@richtek.com>
References: <28FE6F1712799128000.chiaen_wu@richtek.com>
Subject: Re: (subset) [PATCH] leds: mt6360: Fix the second LED can not
 enable torch mode by V4L2
Message-Id: <171285411780.2498946.3824215880975158305.b4-ty@kernel.org>
Date: Thu, 11 Apr 2024 17:48:37 +0100
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Tue, 09 Apr 2024 18:21:54 +0800, ChiaEn Wu wrote:
> V4L2 will disable strobe mode of the LED device when enable torch mode,
> but this logic will conflict with the "priv->fled_torch_used"
> in "mt6360_strobe_set()". So after enabling torch mode of the first
> LED, the second LED will not be able to enable torch mode correctly.
> 
> Therefore, at the beginning of "mt6360_strobe_set()", check whether the
> state of the upcoming change and the current LED device state are the
> same, so as to avoid the above problem.
> 
> [...]

Applied, thanks!

[1/1] leds: mt6360: Fix the second LED can not enable torch mode by V4L2
      commit: 0dcd0488a7a5b8762256b393a8bd0c21e5e4e0fb

--
Lee Jones [李琼斯]