[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49af8f44-51d4-aded-a34e-55c7c5780008@marek.ca>
Date: Wed, 1 Jul 2020 13:13:34 -0400
From: Jonathan Marek <jonathan@...ek.ca>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: freedreno@...ts.freedesktop.org, Rob Clark <robdclark@...il.com>,
Sean Paul <sean@...rly.run>, David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
Jordan Crouse <jcrouse@...eaurora.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Brian Masney <masneyb@...tation.org>,
Fabio Estevam <festevam@...il.com>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<linux-arm-msm@...r.kernel.org>,
"open list:DRM DRIVER FOR MSM ADRENO GPU"
<dri-devel@...ts.freedesktop.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/msm: handle for EPROBE_DEFER for of_icc_get
On 7/1/20 1:12 PM, Matthias Kaehlcke wrote:
> Hi Jonathan,
>
> On Tue, Jun 30, 2020 at 11:08:41PM -0400, Jonathan Marek wrote:
>> Check for EPROBE_DEFER instead of silently not using icc if the msm driver
>> probes before the interconnect driver.
>
> Agreed with supporting deferred ICC probing.
>
>> Only check for EPROBE_DEFER because of_icc_get can return other errors that
>> we want to ignore (ENODATA).
>
> What would be the -ENODATA case?
>
The of_icc_get for the ocmem_icc_path can return -ENODATA when the ocmem
path is not specified (it is optional and only relevant for a3xx/a4xx).
> If the 'interconnects' property is not specified of_icc_get() returns NULL,
> shouldn't all (or most) errors be propagated rather than staying silent?
>
> Thanks
>
> Matthias
>
Powered by blists - more mailing lists