linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kgunda@codeaurora.org
To: Pavel Machek <pavel@ucw.cz>
Cc: bjorn.andersson@linaro.org, jingoohan1@gmail.com,
	lee.jones@linaro.org, b.zolnierkie@samsung.com,
	dri-devel@lists.freedesktop.org, daniel.thompson@linaro.org,
	jacek.anaszewski@gmail.com, robh+dt@kernel.org,
	mark.rutland@arm.com, linux-leds@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V1 0/2] Fix WLED FSC Sync and brightness Sync settings
Date: Wed, 24 Feb 2021 09:19:03 +0530	[thread overview]
Message-ID: <1fcacbe5de8dd7d3a0df2b6108d734f6@codeaurora.org> (raw)
In-Reply-To: <20210219180839.GB8596@duo.ucw.cz>

On 2021-02-19 23:38, Pavel Machek wrote:
> Hi!
> 
>> The FSC (Full scale current) setting is not updated properly due to 
>> the
>> wrong register toggling for WLED5. Also the ILED_SYNC toggle and 
>> MOD_SYNC
>> toggle sequence is updated as per the hardware team recommendation to 
>> fix
>> the FSC update and brightness update issue.
> 
> If this is phone hardware, it might make sense to cc:
> phone-devel@vger...
> 
Yes. it is for phone hardware. Will cc the email.
> Best regards,
> 									Pavel

  reply	other threads:[~2021-02-24  3:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 14:07 [PATCH V1 0/2] Fix WLED FSC Sync and brightness Sync settings Kiran Gunda
2021-02-19 14:07 ` [PATCH V1 1/2] backlight: qcom-wled: Fix FSC update issue for WLED5 Kiran Gunda
2021-02-19 14:07 ` [PATCH V1 2/2] backlight: qcom-wled: Correct the sync_toggle sequence Kiran Gunda
2021-02-19 18:08 ` [PATCH V1 0/2] Fix WLED FSC Sync and brightness Sync settings Pavel Machek
2021-02-24  3:49   ` kgunda [this message]
2021-02-24  3:50 Kiran Gunda

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=1fcacbe5de8dd7d3a0df2b6108d734f6@codeaurora.org \
    --to=kgunda@codeaurora.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel.thompson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=jingoohan1@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).