Non-conformant VK 1.1+ support on A702

--000000000000aac8f106499fc367
Content-Type: text/plain; charset="UTF-8"

Hi Turnip Team,

You may have noticed that Arduino/Qualcomm released the Arduino Uno Q SBC
which has a QRB2210 SoC and an Adreno 702 GPU.   I suspect they'll sell a
decent number of these devices.

I skimmed the driver and noticed the A702 doesn't support multiview which
is mandatory in VK 1.1 and therefore `.apiVersion` is set to 1.0.x which
lops off a lot of interesting Vulkan features.

It's too bad that the lack of multiview has gated so many features (I
understand why) but let's say I won't be using multiview and, for example,
really want to use subgroup compute capabilities.

How accurate are the rest of the physical device properties for A702 in
case I want to run a non-conformant driver that lifts the `.apiVersion` to
1.3 or 1.4?

I don't recall the Vulkan org describing a workaround for a situation like
this (nor should they).

Whatever the answer, it's interesting that a low-end board now has an
*almost* compliant Vulkan 1.4 GPU...

Thanks for any suggestions.

Allan

----

A702 checks in `tu_device.cc`:

   -
   https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/freedreno/vulkan/tu_device.cc?ref_type=heads#L1220
   -
   https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/freedreno/vulkan/tu_device.cc?ref_type=heads#L151

--000000000000aac8f106499fc367
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Turnip Team,</div><div><br></div><div>You may have=
 noticed that Arduino/Qualcomm released the Arduino Uno Q SBC which has a=
=C2=A0QRB2210 SoC and an Adreno 702 GPU.=C2=A0 =C2=A0I suspect they&#39;ll =
sell a decent number of these devices.</div><div><br></div><div>I skimmed t=
he driver and noticed the A702 doesn&#39;t support multiview which is manda=
tory in VK 1.1 and therefore `.apiVersion` is set to 1.0.x which lops off a=
 lot of interesting Vulkan features.</div><div><br></div><div>It&#39;s too =
bad that the lack of multiview has gated so many features (I understand why=
) but let&#39;s say I won&#39;t be using multiview and, for example, really=
 want to use subgroup compute capabilities.</div><div><br></div><div>How ac=
curate are the rest of the physical device properties for A702 in case I wa=
nt to run a non-conformant driver that lifts the `.apiVersion` to 1.3 or 1.=
4?</div><div><br><div>I don&#39;t recall the Vulkan org describing a workar=
ound for a situation like this (nor should they).</div><div></div></div><di=
v><br>Whatever the answer, it&#39;s interesting that a low-end board now ha=
s an *almost* compliant Vulkan 1.4 GPU...</div><div><br></div><div>Thanks f=
or any suggestions.</div><div><br></div><div>Allan</div><div><br></div><div=
>----</div><div><br></div><div>A702 checks in `tu_device.cc`:</div><div><ul=
><li><a href=3D"https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/fr=
eedreno/vulkan/tu_device.cc?ref_type=3Dheads#L1220">https://gitlab.freedesk=
top.org/mesa/mesa/-/blob/main/src/freedreno/vulkan/tu_device.cc?ref_type=3D=
heads#L1220</a></li><li><a href=3D"https://gitlab.freedesktop.org/mesa/mesa=
/-/blob/main/src/freedreno/vulkan/tu_device.cc?ref_type=3Dheads#L151">https=
://gitlab.freedesktop.org/mesa/mesa/-/blob/main/src/freedreno/vulkan/tu_dev=
ice.cc?ref_type=3Dheads#L151</a></li></ul></div></div>

--000000000000aac8f106499fc367--