[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=XEsZVfgoOzMAMtye+NB17cP5VO9s=_yVZ2Frp4y4Y6Ug@mail.gmail.com>
Date: Wed, 27 Jan 2021 13:11:17 -0800
From: Doug Anderson <dianders@...omium.org>
To: Stephen Boyd <swboyd@...omium.org>
Cc: Sam Ravnborg <sam@...nborg.org>,
Thierry Reding <thierry.reding@...il.com>,
Rob Clark <robdclark@...omium.org>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>,
dri-devel <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 3/5] drm/panel-simple: Retry if we timeout waiting for HPD
Hi,
On Mon, Jan 25, 2021 at 12:28 PM Stephen Boyd <swboyd@...omium.org> wrote:
>
> > +/*
> > + * Some panels simply don't always come up and need to be power cycled to
> > + * work properly. We'll allow for a handful of retries.
> > + */
> > +#define MAX_PANEL_PREPARE_TRIES 5
>
> Is this define used anywhere else? Feels like it would be better to
> inline the constant and move the comment above the loop, but I guess
> this is OK too.
Hrm, usually I only add a #define like this when I need to use the
same number more than once, but I'm not doing that here. Maybe I did
in an earlier version of the code and then didn't go back and remove
the #define when I reworked it?
Since this is a bit of a style issue, I will leave it to the
simple-panel maintainers to decide. I'm happy to spin this and add
the comment before the loop and just hardcode "5" in the loop instead
of using MAX_PANEL_PREPARE_TRIES, so just let me know.
-Doug
Powered by blists - more mailing lists