On 17/08/2022 22:33, Brian Norris wrote: > The Gru-Scarlet family includes a variety of SKU identifiers, using > parts of a 3-bit space {0..7}. SKU2 and SKU4 devices (under a few > different manufacturer names) also use the Innolux display. > > For reference, the original vendor tree source: > > CHROMIUM: arm64: dts: rockchip: add sku{0,2,4} compatibility > https://chromium.googlesource.com/chromiumos/third_party/kernel/+/f6ed665c9e2eb37fb2680debbb36ec9fb0e8fb97 > > CHROMIUM: arm64: dts: rockchip: scarlet: add SKU0 device tree > https://chromium.googlesource.com/chromiumos/third_party/kernel/+/9987c8776f4b087d135d761e59f7fa6cc83fc7fc > > Signed-off-by: Brian Norris <briannorris@xxxxxxxxxxxx> > --- > > .../devicetree/bindings/arm/rockchip.yaml | 27 ++++++++++++++++++- > 1 file changed, 26 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml > index 7811ba64149c..dcae534e3971 100644 > --- a/Documentation/devicetree/bindings/arm/rockchip.yaml > +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml > @@ -363,30 +363,55 @@ properties: > - const: google,gru > - const: rockchip,rk3399 > > - - description: Google Scarlet - Innolux display (Acer Chromebook Tab 10) > + - description: | > + Google Scarlet - Innolux display (Acer Chromebook Tab 10 and more) > items: > + - const: google,scarlet-rev15-sku2 > + - const: google,scarlet-rev15-sku4 This does not match the sources you linked in commit msg, so I am confused what the links are supposed to prove. Is this matching at least your DTS (dtbs_check passes)? Best regards, Krzysztof