[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aSWnTE-jeHEg12N3@trex>
Date: Tue, 25 Nov 2025 13:55:40 +0100
From: Jorge Ramirez <jorge.ramirez@....qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
Cc: Jorge Ramirez-Ortiz <jorge.ramirez@....qualcomm.com>,
vikash.garodia@....qualcomm.com, dikshita.agarwal@....qualcomm.com,
bod@...nel.org, mchehab@...nel.org, linux-media@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] media: venus: assign unique bus_info strings for encoder
and decoder
On 21/11/25 20:22:13, Konrad Dybcio wrote:
> On 11/21/25 7:43 PM, Jorge Ramirez-Ortiz wrote:
> > The Venus encoder and decoder video devices currently report the same
> > bus_info string ("platform:qcom-venus").
> >
> > Assign unique bus_info identifiers by appending ":dec" and ":enc" to the
> > parent device name. With this change v4l2-ctl will display two separate
> > logical devices
> >
> > Signed-off-by: Jorge Ramirez-Ortiz <jorge.ramirez@....qualcomm.com>
> > ---
>
> Perhaps that's a stupid question, but is there a reason they're
> separate at all?
not sure I understand, enc/dec support different APIs, v4l2 controls..is
that what you mean?
>
> Konrad
>
Powered by blists - more mailing lists