[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f38bda2f1753645a1ae392ce5364ea0165fdc01.camel@ndufresne.ca>
Date: Thu, 04 Dec 2025 13:15:35 -0500
From: Nicolas Dufresne <nicolas@...fresne.ca>
To: Frank Li <Frank.li@....com>, ming.qian@....nxp.com
Cc: linux-media@...r.kernel.org, mchehab@...nel.org,
hverkuil-cisco@...all.nl, benjamin.gaignard@...labora.com,
p.zabel@...gutronix.de, sebastian.fricke@...labora.com,
shawnguo@...nel.org, ulf.hansson@...aro.org, s.hauer@...gutronix.de,
kernel@...gutronix.de, festevam@...il.com, linux-imx@....com,
l.stach@...gutronix.de, peng.fan@....com, eagle.zhou@....com,
imx@...ts.linux.dev, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 3/3] media: verisilicon: Avoid G2 bus error while
decoding H.264 and HEVC
Hi Frank,
Le jeudi 04 décembre 2025 à 12:34 -0500, Frank Li a écrit :
> > +static struct v4l2_m2m_dev *hantro_get_v4l2_m2m_dev(struct hantro_dev *vpu)
> > +{
> > + struct device_node *node;
> > + struct hantro_dev *shared_vpu;
> > +
> > + if (!vpu->variant || !vpu->variant->shared_devices)
> > + goto init_new_m2m_dev;
>
> I found only use shared_devices here, how to ensure that g1 and g2 operate
> alternately by using shared_devices?
shared_devices is an array of of_device_id we match against. All the matching
devices will share the same v4l2_m2m_dev (aka m2m scheduler). Typically, both
cores will be schedule as one. This achieve what alternate operations without
active polling or blocking locks/mutex.
For this platform, we only matched against the compatible for simplicity, since
we know there is only one of each type. I've suggested this method to Ming,
since it will make it really easy to apply such a quirk if other hardware have
problems or design constraints.
regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists