From: Alex Deucher <alexdeucher@gmail.com>
To: "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Takashi Iwai <tiwai@suse.de>,
"Siqueira, Rodrigo" <Rodrigo.Siqueira@amd.com>,
"Wentland, Harry" <Harry.Wentland@amd.com>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/4] drm/amdgpu/display: don't assert in set backlight function
Date: Thu, 4 Mar 2021 13:41:46 -0500 [thread overview]
Message-ID: <CADnq5_NRF4N+85Rf-3xOq0nmOFjkwRbdj7znHsL9J2vN=Ufg5w@mail.gmail.com> (raw)
In-Reply-To: <eeb3b2e8-affe-ffa9-b538-d0da4a34c877@amd.com>
On Thu, Mar 4, 2021 at 1:33 PM Kazlauskas, Nicholas
<nicholas.kazlauskas@amd.com> wrote:
>
> On 2021-03-04 12:41 p.m., Alex Deucher wrote:
> > It just spams the logs.
> >
> > Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>
> This series in general looks reasonable to me:
> Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
>
> > ---
> > drivers/gpu/drm/amd/display/dc/core/dc_link.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_link.c b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> > index fa9a62dc174b..974b70f21837 100644
> > --- a/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> > +++ b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> > @@ -2614,7 +2614,6 @@ bool dc_link_set_backlight_level(const struct dc_link *link,
> > if (pipe_ctx->plane_state == NULL)
> > frame_ramp = 0;
> > } else {
> > - ASSERT(false);
>
> Just a comment on what's actually going on here with this warning:
>
> Technically we can't apply the backlight level without a plane_state in
> the context but the panel is also off anyway.
>
> I think there might be a bug here when the panel turns on and we're not
> applying values set when it was off but I don't think anyone's reported
> this as an issue.
>
> I'm not entirely sure if the value gets cached and reapplied with the
> correct value later, but it's something to keep in mind.
It doesn't. I have additional patches here to cache it:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=backlight_wip
Alex
>
> Regards,
> Nicholas Kazlauskas
>
> > return false;
> > }
> >
> >
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2021-03-04 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 17:40 [PATCH 0/4] Backlight fixes Alex Deucher
2021-03-04 17:41 ` [PATCH 1/4] drm/amdgpu/display: simplify backlight setting Alex Deucher
2021-03-04 17:41 ` [PATCH 2/4] drm/amdgpu/display: don't assert in set backlight function Alex Deucher
2021-03-04 18:33 ` Kazlauskas, Nicholas
2021-03-04 18:41 ` Alex Deucher [this message]
2021-03-04 18:50 ` Kazlauskas, Nicholas
2021-03-04 17:41 ` [PATCH 3/4] drm/amdgpu/display: handle aux backlight in backlight_get_brightness Alex Deucher
2021-03-04 17:41 ` [PATCH 4/4] drm/amd/display: Add a backlight module option Alex Deucher
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='CADnq5_NRF4N+85Rf-3xOq0nmOFjkwRbdj7znHsL9J2vN=Ufg5w@mail.gmail.com' \
--to=alexdeucher@gmail.com \
--cc=Harry.Wentland@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=nicholas.kazlauskas@amd.com \
--cc=tiwai@suse.de \
/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.