[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180622231934.GO3402@tuxbook-pro>
Date: Fri, 22 Jun 2018 16:19:34 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Tomasz Figa <tfiga@...omium.org>
Cc: vgarodia@...eaurora.org, Hans Verkuil <hverkuil@...all.nl>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh@...nel.org>,
Mark Rutland <mark.rutland@....com>, andy.gross@...aro.org,
Stanimir Varbanov <stanimir.varbanov@...aro.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
linux-soc@...r.kernel.org, devicetree@...r.kernel.org,
Alexandre Courbot <acourbot@...omium.org>
Subject: Re: [PATCH v2 3/5] venus: add check to make scm calls
On Mon 04 Jun 05:58 PDT 2018, Tomasz Figa wrote:
> Hi Vikash,
>
> On Sat, Jun 2, 2018 at 5:27 AM Vikash Garodia <vgarodia@...eaurora.org> wrote:
> [snip]
> > +int venus_boot(struct venus_core *core)
> > +{
> > + phys_addr_t mem_phys;
> > + size_t mem_size;
> > + int ret;
> > + struct device *dev;
> > +
> > + if (!IS_ENABLED(CONFIG_QCOM_MDT_LOADER))
> > + return -EPROBE_DEFER;
>
> Why are we deferring probe here? The option will not magically become
> enabled after probe is retried.
>
The original code should have read:
if (IS_ENABLED(CONFIG_QCOM_MDT_LOADER) && !qcom_scm_is_available())
return -EPROBE_DEFER;
The code does depend on CONFIG_QCOM_MDT_LOADER regardless of it using
scm for firmware verification.
Regards,
Bjorn
Powered by blists - more mailing lists