[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aJSvjqfQw3kNrVVH@trex>
Date: Thu, 7 Aug 2025 15:52:14 +0200
From: Jorge Ramirez <jorge.ramirez@....qualcomm.com>
To: Vikash Garodia <quic_vgarodia@...cinc.com>
Cc: Jorge Ramirez <jorge.ramirez@....qualcomm.com>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
bryan.odonoghue@...aro.org, quic_dikshita@...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 5/7] media: venus: core: Add qcm2290 DT compatible and
resource data
On 07/08/25 16:36:41, Vikash Garodia wrote:
>
> > It was agreed that this complexity was not necessary and that we should
> > just drop <6.0.55 firmware support (which would in any case only include
> > video decode).
> >
> > And so on v8, I removed the above.
> >
> > Now I have v9 ready to post it, but Dmitry is asking why cant we have
> > the v7 functionality so I am waiting for direction.
>
> the issue is in firmware for both encoder and decoder. Didn't like the idea of
> driver carrying the hack for a firmware issue. Just because, for encoder, we are
> unable to hack it in driver, we are ok to have it enabled in a newer version of
> the firmware, we can follow the same for decoders as well.
if that is the only reason please do explain what do you mean by hack.
Powered by blists - more mailing lists