This v3 addresses an automated ("Sashiko AI") review comment on v2 [2]:
spacemit,k3-gpu didn't match any "if" block constraining clocks, so it
fell back to this schema's general 1-3 item range, which would have
let an invalid DT with 2 or 3 clocks pass validation even though this
platform only ever has one. Patch 1 now also adds spacemit,k3-gpu to
the existing ti,am62-gpu/ti,am62p-gpu/ti,j721s2-gpu "if" block that
restricts clocks to a single entry, since K3 has the same requirement.
See the v3 note under patch 1 for details.v2 reordered and extended the earlier standalone pvr_power.c change per Alessio's review [1]. On the SpacemiT K3 SoC, the GPU power domain is enabled once by the bootloader before Linux boots and is neither modelled nor switched by Linux at runtime. As pointed out in review, img,powervr-rogue.yaml currently has no compatible entry this platform's GPU can use, so patch 1 adds one (spacemit,k3-gpu + img,img-bxm-4-64 + img,img-rogue) as its own oneOf entry, distinct from thead,th1520-gpu since the two differ in clock requirements. This new compatible doesn't match any "if" block that constrains power-domains, so that property falls back to the schema's default (optional) behaviour for it -- no additional required/false override is needed. Patch 2 is the previously-sent driver change: pvr_power_domains_init() treats a missing "power-domains" property as "nothing to attach" instead of failing probe with -ENOENT. [1] https://lore.kernel.org/all/[email protected]/ [2] https://sashiko.dev/#/patchset/[email protected]?part=1 Sterling-Ash (2): dt-bindings: gpu: img,powervr-rogue: add spacemit,k3-gpu drm/imagination: allow probe when no power-domains are described .../devicetree/bindings/gpu/img,powervr-rogue.yaml | 6 ++++++ drivers/gpu/drm/imagination/pvr_power.c | 9 +++++++++ 2 files changed, 15 insertions(+) -- 2.34.1
