[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGb2v67eNu31pQExMTxAki1Wp4tdqRH87Oh+1j4Cb0cuK8pQRQ@mail.gmail.com>
Date: Fri, 14 Jun 2019 11:24:29 +0800
From: Chen-Yu Tsai <wens@...e.org>
To: Jagan Teki <jagan@...rulasolutions.com>
Cc: Maxime Ripard <maxime.ripard@...tlin.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
dri-devel <dri-devel@...ts.freedesktop.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
Jernej Skrabec <jernej.skrabec@...l.net>,
Michael Trimarchi <michael@...rulasolutions.com>,
linux-sunxi <linux-sunxi@...glegroups.com>,
linux-amarula@...rulasolutions.com
Subject: Re: [PATCH 4/9] drm/sun4i: tcon_top: Use clock name index macros
On Fri, Jun 14, 2019 at 2:54 AM Jagan Teki <jagan@...rulasolutions.com> wrote:
>
> TCON TOP mux blocks in R40 are registering clock using
> tcon top clock index numbers.
>
> Right now the code is using, real numbers start with 0, but
> we have proper macros that defined these name index numbers.
>
> Use the existing macros, instead of real numbers for more
> code readability.
>
> Signed-off-by: Jagan Teki <jagan@...rulasolutions.com>
Reviewed-by: Chen-Yu Tsai <wens@...e.org>
However, you might want to rename the clock first, then switch to
using the index macros?
Powered by blists - more mailing lists