[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADaigPXdn84cR0Pu-uLnCwOVHNUiOi_t6u7OYYDU6tkSvdWp6A@mail.gmail.com>
Date: Tue, 18 Feb 2020 13:58:39 -0800
From: Eric Anholt <eric@...olt.net>
To: Jordan Crouse <jcrouse@...eaurora.org>
Cc: linux-arm-msm@...r.kernel.org, David Airlie <airlied@...ux.ie>,
Sean Paul <sean@...rly.run>, Wen Yang <wen.yang99@....com.cn>,
AngeloGioacchino Del Regno <kholk11@...il.com>,
linux-kernel@...r.kernel.org,
DRI Development <dri-devel@...ts.freedesktop.org>,
Rob Clark <robdclark@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
freedreno@...ts.freedesktop.org,
Jeffrey Hugo <jeffrey.l.hugo@...il.com>,
Ben Dooks <ben.dooks@...ethink.co.uk>,
Daniel Vetter <daniel@...ll.ch>
Subject: Re: [PATCH] drm/msm/a5xx: Always set an OPP supported hardware value
On Fri, Feb 14, 2020 at 10:36 AM Jordan Crouse <jcrouse@...eaurora.org> wrote:
>
> If the opp table specifies opp-supported-hw as a property but the driver
> has not set a supported hardware value the OPP subsystem will reject
> all the table entries.
>
> Set a "default" value that will match the default table entries but not
> conflict with any possible real bin values. Also fix a small memory leak
> and free the buffer allocated by nvmem_cell_read().
>
> Signed-off-by: Jordan Crouse <jcrouse@...eaurora.org>
This does fix my warn at boot on db820c.
Reviewed-by: Eric Anholt <eric@...olt.net>
Powered by blists - more mailing lists