Message ID | 20230514165651.2199-7-jszhang@kernel.org (mailing list archive) |
---|---|
State | Superseded |
Delegated to: | Conor Dooley |
Headers | show |
Series | riscv: add Bouffalolab bl808 support | expand |
Context | Check | Description |
---|---|---|
conchuod/cover_letter | success | Series has a cover letter |
conchuod/tree_selection | success | Guessed tree name to be for-next at HEAD ac9a78681b92 |
conchuod/fixes_present | success | Fixes tag not required for -next series |
conchuod/maintainers_pattern | success | MAINTAINERS pattern errors before the patch: 6 and now 6 |
conchuod/verify_signedoff | success | Signed-off-by tag matches author and committer |
conchuod/kdoc | success | Errors and warnings before: 0 this patch: 0 |
conchuod/build_rv64_clang_allmodconfig | fail | Failed to build the tree with this patch. |
conchuod/module_param | success | Was 0 now: 0 |
conchuod/build_rv64_gcc_allmodconfig | fail | Failed to build the tree with this patch. |
conchuod/build_rv32_defconfig | success | Build OK |
conchuod/dtb_warn_rv64 | success | Errors and warnings before: 5 this patch: 5 |
conchuod/header_inline | success | No static functions without inline keyword in header files |
conchuod/checkpatch | warning | WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? |
conchuod/build_rv64_nommu_k210_defconfig | success | Build OK |
conchuod/verify_fixes | success | No Fixes tag |
conchuod/build_rv64_nommu_virt_defconfig | success | Build OK |
On Mon, May 15, 2023 at 12:56:47AM +0800, Jisheng Zhang wrote: > +title: Bouffalo Lab Technology SoC-based boards I know you're only propagating an existing pattern, but the "SoC-based" looks rather odd! > +properties: > + $nodename: > + const: '/' > + compatible: > + oneOf: > + - description: Carrier boards for the Sipeed M1s SoM > + items: > + - enum: > + - sipeed,m1s-dock BTW, do you know of any other m1s compatible docks? I couldn't find any other ones via Google, so maybe it is just worth swapping the enum here for another const. Either is fine by me though. Reviewed-by: Conor Dooley <conor.dooley@microchip.com> Thanks, Conor.
On Sun, May 14, 2023 at 07:39:28PM +0100, Conor Dooley wrote: > On Mon, May 15, 2023 at 12:56:47AM +0800, Jisheng Zhang wrote: > > > +title: Bouffalo Lab Technology SoC-based boards > > I know you're only propagating an existing pattern, but the "SoC-based" > looks rather odd! > > > +properties: > > + $nodename: > > + const: '/' > > + compatible: > > + oneOf: > > + - description: Carrier boards for the Sipeed M1s SoM > > + items: > > + - enum: > > + - sipeed,m1s-dock > > BTW, do you know of any other m1s compatible docks? > I couldn't find any other ones via Google, so maybe it is just worth FWICT, there's no other m1s compatible docks, but in theory the SoM can be used to build different docks, I just keep it as is since you are fine with it too ;) > swapping the enum here for another const. > Either is fine by me though. > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > > Thanks, > Conor.
diff --git a/Documentation/devicetree/bindings/riscv/bouffalolab.yaml b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml new file mode 100644 index 000000000000..3b25d1a5d04a --- /dev/null +++ b/Documentation/devicetree/bindings/riscv/bouffalolab.yaml @@ -0,0 +1,29 @@ +# 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: Carrier boards for the Sipeed M1s SoM + items: + - enum: + - sipeed,m1s-dock + - const: sipeed,m1s + - const: bouffalolab,bl808 + +additionalProperties: true + +...