J-Core is a clean-room open source processor and SoC design using the
SuperH instruction set.
The 'jcore' prefix is in use by IP cores originating from this design.
Link: https://j-core.org
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Artur Rojek <contact@artur-rojek.eu>
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
index a92261b10c52..558f51665616 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -783,6 +783,8 @@ patternProperties:
description: Jadard Technology Inc.
"^jasonic,.*":
description: Jasonic Technology Ltd.
+ "^jcore,.*":
+ description: J-Core Open Processor
"^jdi,.*":
description: Japan Display Inc.
"^jedec,.*":
--
2.50.1
On 15/08/2025 21:48, Artur Rojek wrote: > J-Core is a clean-room open source processor and SoC design using the > SuperH instruction set. > > The 'jcore' prefix is in use by IP cores originating from this design. > > Link: https://j-core.org > Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org> > Signed-off-by: Artur Rojek <contact@artur-rojek.eu> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Best regards, Krzysztof
On 15/08/2025 21:48, Artur Rojek wrote: > J-Core is a clean-room open source processor and SoC design using the > SuperH instruction set. > > The 'jcore' prefix is in use by IP cores originating from this design. > > Link: https://j-core.org > Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org> How is it possible if this is v1? If this is not v1, where is changelog and why isn't it marked as vx? > Signed-off-by: Artur Rojek <contact@artur-rojek.eu> > --- > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++ > 1 file changed, 2 insertions(+) Best regards, Krzysztof
Hi Krzysztof, On Sat, 16 Aug 2025 at 10:18, Krzysztof Kozlowski <krzk@kernel.org> wrote: > On 15/08/2025 21:48, Artur Rojek wrote: > > J-Core is a clean-room open source processor and SoC design using the > > SuperH instruction set. > > > > The 'jcore' prefix is in use by IP cores originating from this design. > > > > Link: https://j-core.org > > Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org> > > How is it possible if this is v1? If this is not v1, where is changelog > and why isn't it marked as vx? The patch series had several iterations (v0, v-1, v-2 ;-), with a limited audience. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
On 16/08/2025 10:22, Geert Uytterhoeven wrote: > Hi Krzysztof, > > On Sat, 16 Aug 2025 at 10:18, Krzysztof Kozlowski <krzk@kernel.org> wrote: >> On 15/08/2025 21:48, Artur Rojek wrote: >>> J-Core is a clean-room open source processor and SoC design using the >>> SuperH instruction set. >>> >>> The 'jcore' prefix is in use by IP cores originating from this design. >>> >>> Link: https://j-core.org >>> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org> >> >> How is it possible if this is v1? If this is not v1, where is changelog >> and why isn't it marked as vx? > > The patch series had several iterations (v0, v-1, v-2 ;-), with a limited > audience. Thanks, would be nice to see it reflected somewhere. Best regards, Krzysztof
On 2025-08-16 11:40, Krzysztof Kozlowski wrote: > On 16/08/2025 10:22, Geert Uytterhoeven wrote: >> Hi Krzysztof, Hi Krzysztof, thanks for the review! >> >> On Sat, 16 Aug 2025 at 10:18, Krzysztof Kozlowski <krzk@kernel.org> >> wrote: >>> On 15/08/2025 21:48, Artur Rojek wrote: >>>> J-Core is a clean-room open source processor and SoC design using >>>> the >>>> SuperH instruction set. >>>> >>>> The 'jcore' prefix is in use by IP cores originating from this >>>> design. >>>> >>>> Link: https://j-core.org >>>> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org> >>> >>> How is it possible if this is v1? If this is not v1, where is >>> changelog >>> and why isn't it marked as vx? >> >> The patch series had several iterations (v0, v-1, v-2 ;-), with a >> limited >> audience. > > Thanks, would be nice to see it reflected somewhere. I mentioned it in the cover letter. For the record: v1: capitalize Open Processor v0: new patch Cheers, Artur > > Best regards, > Krzysztof
© 2016 - 2025 Red Hat, Inc.