[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aJHWtaLung8Ubdh8@trex>
Date: Tue, 5 Aug 2025 12:02:29 +0200
From: Jorge Ramirez <jorge.ramirez@....qualcomm.com>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>
Cc: Jorge Ramirez-Ortiz <jorge.ramirez@....qualcomm.com>,
quic_dikshita@...cinc.com, quic_vgarodia@...cinc.com,
konradybcio@...nel.org, krzk+dt@...nel.org, mchehab@...nel.org,
conor+dt@...nel.org, andersson@...nel.org, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 2/7] media: venus: Define minimum valid firmware
version
On 05/08/25 09:29:55, Bryan O'Donoghue wrote:
> On 05/08/2025 07:44, Jorge Ramirez-Ortiz wrote:
> > + if (!is_fw_rev_or_newer(core, ver->major, ver->minor, ver->rev))
> > + return -EINVAL;
> > +
>
> This is the sort of error case that deserves a kernel log.
>
> dev_err(dev, "Firmware version %d.%d < minimum version %d.%d\n, etc);
>
> If I were to try booting venus with an old/unsupported I wouldn't know why
> the probe was failing.
ok
>
> ---
> bod
Powered by blists - more mailing lists