Message ID | 20220520143502.v4.2.I6418884d8bab6956c7016304f45adc7df808face@changeid (mailing list archive) |
---|---|
State | Accepted |
Headers | show |
Series | [v4,1/5] dt-bindings: Document how Chromebooks with depthcharge boot | expand |
On 20/05/2022 23:38, Douglas Anderson wrote: > The qcom.yaml bindings file has a whole description of what the > top-level compatible should look like for Qualcomm devices. It doesn't > match what Chromebooks do, so add a link to the Chromebook docs. > > Reported-by: Stephen Boyd <swboyd@chromium.org> > Signed-off-by: Douglas Anderson <dianders@chromium.org> > Reviewed-by: Matthias Kaehlcke <mka@chromium.org> > --- Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml index 5c06d1bfc046..5ac28e11ea7b 100644 --- a/Documentation/devicetree/bindings/arm/qcom.yaml +++ b/Documentation/devicetree/bindings/arm/qcom.yaml @@ -90,6 +90,11 @@ description: | A dragonboard board v0.1 of subtype 1 with an apq8074 SoC version 2, made in foundry 2. + There are many devices in the list below that run the standard ChromeOS + bootloader setup and use the open source depthcharge bootloader to boot the + OS. These devices do not use the scheme described above. For details, see: + https://docs.kernel.org/arm/google/chromebook-boot-flow.html + properties: $nodename: const: "/"