Message ID | 20221127132448.4034-6-jszhang@kernel.org (mailing list archive) |
---|---|
State | Changes Requested |
Headers | show |
Series | riscv: add Bouffalolab bl808 support | expand |
Context | Check | Description |
---|---|---|
conchuod/tree_selection | fail | Guessing tree name failed |
On Sun, 27 Nov 2022 21:24:44 +0800, Jisheng Zhang wrote: > Several SoMs and boards are available that feature the Bouffalolab > bl808 SoC. Document the compatible strings. > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org> > --- > .../bindings/riscv/bouffalolab.yaml | 34 +++++++++++++++++++ > 1 file changed, 34 insertions(+) > create mode 100644 Documentation/devicetree/bindings/riscv/bouffalolab.yaml > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13): yamllint warnings/errors: ./Documentation/devicetree/bindings/riscv/bouffalolab.yaml:20:36: [error] syntax error: mapping values are not allowed here (syntax) dtschema/dtc warnings/errors: make[1]: *** Deleting file 'Documentation/devicetree/bindings/riscv/bouffalolab.example.dts' Documentation/devicetree/bindings/riscv/bouffalolab.yaml:20:36: mapping values are not allowed in this context make[1]: *** [Documentation/devicetree/bindings/Makefile:26: Documentation/devicetree/bindings/riscv/bouffalolab.example.dts] Error 1 make[1]: *** Waiting for unfinished jobs.... ./Documentation/devicetree/bindings/riscv/bouffalolab.yaml:20:36: mapping values are not allowed in this context /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/riscv/bouffalolab.yaml: ignoring, error parsing file make: *** [Makefile:1492: dt_binding_check] Error 2 doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20221127132448.4034-6-jszhang@kernel.org This check can fail if there are any dependencies. The base for a patch series is generally the most recent rc1. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command.
On Sun, Nov 27, 2022 at 09:24:44PM +0800, Jisheng Zhang wrote: > Several SoMs and boards are available that feature the Bouffalolab > bl808 SoC. Document the compatible strings. > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org> > --- > .../bindings/riscv/bouffalolab.yaml | 34 +++++++++++++++++++ > 1 file changed, 34 insertions(+) > create mode 100644 Documentation/devicetree/bindings/riscv/bouffalolab.yaml > > diff --git a/Documentation/devicetree/bindings/riscv/bouffalolab.yaml b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > new file mode 100644 > index 000000000000..91ca9dbdc798 > --- /dev/null > +++ b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > @@ -0,0 +1,34 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/riscv/bouffalolab.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Bouffalo Lab Technology SoC-based boards > + > +maintainers: > + - Jisheng Zhang <jszhang@kernel.org> > + > +description: > + Bouffalo Lab Technology SoC-based boards > + > +properties: > + $nodename: > + const: '/' > + compatible: > + oneOf: > + - description: Sipeed M1s SoM: ^ Drop these :s in the descriptions to placate Rob's bot :) > + items: > + - const: sipeed,m1s > + - const: bouffalolab,bl808 > + > + - description: Carrier boards for the Sipeed M1s SoM: > + items: > + - enum: > + - sipeed,m1s-dock Do we need the enum when there's only one? I assume you're future proofing against adding more carriers? Otherwise than those two bits: Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > + - const: sipeed,m1s > + - const: bouffalolab,bl808 > + > +additionalProperties: true > + > +... > -- > 2.38.1 >
On 27/11/2022 14:24, Jisheng Zhang wrote: > Several SoMs and boards are available that feature the Bouffalolab > bl808 SoC. Document the compatible strings. > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org> > --- > .../bindings/riscv/bouffalolab.yaml | 34 +++++++++++++++++++ > 1 file changed, 34 insertions(+) > create mode 100644 Documentation/devicetree/bindings/riscv/bouffalolab.yaml > > diff --git a/Documentation/devicetree/bindings/riscv/bouffalolab.yaml b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > new file mode 100644 > index 000000000000..91ca9dbdc798 > --- /dev/null > +++ b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > @@ -0,0 +1,34 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/riscv/bouffalolab.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Bouffalo Lab Technology SoC-based boards > + > +maintainers: > + - Jisheng Zhang <jszhang@kernel.org> > + > +description: > + Bouffalo Lab Technology SoC-based boards > + > +properties: > + $nodename: > + const: '/' > + compatible: > + oneOf: > + - description: Sipeed M1s SoM: > + items: > + - const: sipeed,m1s > + - const: bouffalolab,bl808 I don't think that SoM is usable alone. It always needs a carrier, so drop this entry. Please run `make dt_binding_check` (see Documentation/devicetree/bindings/writing-schema.rst for instructions). Best regards, Krzysztof
Hey Krzysztof, On Thu, Dec 01, 2022 at 12:05:04PM +0100, Krzysztof Kozlowski wrote: > On 27/11/2022 14:24, Jisheng Zhang wrote: > > Several SoMs and boards are available that feature the Bouffalolab > > bl808 SoC. Document the compatible strings. > > > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org> > > --- > > .../bindings/riscv/bouffalolab.yaml | 34 +++++++++++++++++++ > > 1 file changed, 34 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/riscv/bouffalolab.yaml > > > > diff --git a/Documentation/devicetree/bindings/riscv/bouffalolab.yaml b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > > new file mode 100644 > > index 000000000000..91ca9dbdc798 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml > > @@ -0,0 +1,34 @@ > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/riscv/bouffalolab.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Bouffalo Lab Technology SoC-based boards > > + > > +maintainers: > > + - Jisheng Zhang <jszhang@kernel.org> > > + > > +description: > > + Bouffalo Lab Technology SoC-based boards > > + > > +properties: > > + $nodename: > > + const: '/' > > + compatible: > > + oneOf: > > + - description: Sipeed M1s SoM: > > + items: > > + - const: sipeed,m1s > > + - const: bouffalolab,bl808 > > I don't think that SoM is usable alone. It always needs a carrier, so > drop this entry. For my own information, if a SoM is not capable of functioning without a carrier there is no merit in it having a compatible? Does this also apply if there are multiple possible carriers from different vendors? Thanks, Conor.
On 01/12/2022 12:14, Conor Dooley wrote: > Hey Krzysztof, > > On Thu, Dec 01, 2022 at 12:05:04PM +0100, Krzysztof Kozlowski wrote: >> On 27/11/2022 14:24, Jisheng Zhang wrote: >>> Several SoMs and boards are available that feature the Bouffalolab >>> bl808 SoC. Document the compatible strings. >>> >>> Signed-off-by: Jisheng Zhang <jszhang@kernel.org> >>> --- >>> .../bindings/riscv/bouffalolab.yaml | 34 +++++++++++++++++++ >>> 1 file changed, 34 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/riscv/bouffalolab.yaml >>> >>> diff --git a/Documentation/devicetree/bindings/riscv/bouffalolab.yaml b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml >>> new file mode 100644 >>> index 000000000000..91ca9dbdc798 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml >>> @@ -0,0 +1,34 @@ >>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >>> +%YAML 1.2 >>> +--- >>> +$id: http://devicetree.org/schemas/riscv/bouffalolab.yaml# >>> +$schema: http://devicetree.org/meta-schemas/core.yaml# >>> + >>> +title: Bouffalo Lab Technology SoC-based boards >>> + >>> +maintainers: >>> + - Jisheng Zhang <jszhang@kernel.org> >>> + >>> +description: >>> + Bouffalo Lab Technology SoC-based boards >>> + >>> +properties: >>> + $nodename: >>> + const: '/' >>> + compatible: >>> + oneOf: >>> + - description: Sipeed M1s SoM: >>> + items: >>> + - const: sipeed,m1s >>> + - const: bouffalolab,bl808 >> >> I don't think that SoM is usable alone. It always needs a carrier, so >> drop this entry. > > For my own information, if a SoM is not capable of functioning without a > carrier there is no merit in it having a compatible? > Does this also apply if there are multiple possible carriers from > different vendors? Compatible makes sense anyway. There will be different boards using this SoM (not only carriers, but final products) and they all will have common piece - the SoM. It's the same for other SoM designs (e.g. for iMX). Best regards, Krzysztof
diff --git a/Documentation/devicetree/bindings/riscv/bouffalolab.yaml b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml new file mode 100644 index 000000000000..91ca9dbdc798 --- /dev/null +++ b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml @@ -0,0 +1,34 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/riscv/bouffalolab.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Bouffalo Lab Technology SoC-based boards + +maintainers: + - Jisheng Zhang <jszhang@kernel.org> + +description: + Bouffalo Lab Technology SoC-based boards + +properties: + $nodename: + const: '/' + compatible: + oneOf: + - description: Sipeed M1s SoM: + items: + - const: sipeed,m1s + - const: bouffalolab,bl808 + + - description: Carrier boards for the Sipeed M1s SoM: + items: + - enum: + - sipeed,m1s-dock + - const: sipeed,m1s + - const: bouffalolab,bl808 + +additionalProperties: true + +...
Several SoMs and boards are available that feature the Bouffalolab bl808 SoC. Document the compatible strings. Signed-off-by: Jisheng Zhang <jszhang@kernel.org> --- .../bindings/riscv/bouffalolab.yaml | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 Documentation/devicetree/bindings/riscv/bouffalolab.yaml