All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Kiran Gunda <kgunda@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V5 0/2] Fix WLED FSC Sync and brightness Sync settings
Date: Wed, 26 May 2021 19:03:24 +0000	[thread overview]
Message-ID: <162205580495.26840.15824067762315798623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1616071180-24493-1-git-send-email-kgunda@codeaurora.org>

Hello:

This series was applied to qcom/linux.git (refs/heads/for-next):

On Thu, 18 Mar 2021 18:09:38 +0530 you wrote:
> This patch series has the following two WLED fixes
>  1. As per the current implementation, for WLED5, after
>     the FSC (Full Scale Current) update the driver is incorrectly
>     toggling the MOD_SYNC register instead of toggling the SYNC register.
>     The patch 1/2 fixes this by toggling the SYNC register after
>     FSC update.
> 
> [...]

Here is the summary with links:
  - [V5,1/2] backlight: qcom-wled: Fix FSC update issue for WLED5
    https://git.kernel.org/qcom/c/4d6e9cdff7fb
  - [V5,2/2] backlight: qcom-wled: Correct the sync_toggle sequence
    https://git.kernel.org/qcom/c/5eb622eec92c

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-05-26 19:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 12:39 [PATCH V5 0/2] Fix WLED FSC Sync and brightness Sync settings Kiran Gunda
2021-03-18 12:39 ` Kiran Gunda
2021-03-18 12:39 ` [PATCH V5 1/2] backlight: qcom-wled: Fix FSC update issue for WLED5 Kiran Gunda
2021-03-18 12:39   ` Kiran Gunda
2021-03-22 17:34   ` Lee Jones
2021-03-22 17:34     ` Lee Jones
2021-03-18 12:39 ` [PATCH V5 2/2] backlight: qcom-wled: Correct the sync_toggle sequence Kiran Gunda
2021-03-18 12:39   ` Kiran Gunda
2021-03-23  9:40   ` Lee Jones
2021-03-23  9:40     ` Lee Jones
2021-05-26 19:03 ` patchwork-bot+linux-arm-msm [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162205580495.26840.15824067762315798623.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=kgunda@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.