All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
Cc: "alex@ghiti.fr" <alex@ghiti.fr>,
	"anup@brainfault.org" <anup@brainfault.org>,
	"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"daniel.lezcano@kernel.org" <daniel.lezcano@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
	"inochiama@outlook.com" <inochiama@outlook.com>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"palmer@dabbelt.com" <palmer@dabbelt.com>,
	"pjw@kernel.org" <pjw@kernel.org>,
	"radu@rendec.net" <radu@rendec.net>,
	"robh@kernel.org" <robh@kernel.org>,
	"tglx@kernel.org" <tglx@kernel.org>,
	"vladimir.kondratiev@mobileye.com"
	<vladimir.kondratiev@mobileye.com>
Subject: Re: [PATCH 3/9] dt-bindings: riscv: Add MIPS Boston board compatible
Date: Wed, 14 Oct 2026 17:33:32 +0100	[thread overview]
Message-ID: <20261014-defection-tiny-3e653ce56e60@spud> (raw)
In-Reply-To: <3d13e372-80da-44bb-845c-14f5022e326a@htecgroup.com>

[-- Attachment #1: Type: text/plain, Size: 3412 bytes --]

On Wed, Oct 14, 2026 at 01:16:16PM +0000, Aleksa Paunovic wrote:
> Hi Conor,
> On 9/15/26 19:58, Conor Dooley wrote:
> > On Mon, Sep 14, 2026 at 03:55:51PM +0200, Aleksa Paunovic via B4 Relay wrote:
> >> From: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> >>
> >> Document the MIPS Boston board compatible with a P8700 bitfile.
> >>
> >> Co-developed-by: Djordje Todorovic <djordje.todorovic@htecgroup.com>
> >> Signed-off-by: Djordje Todorovic <djordje.todorovic@htecgroup.com>
> >> Signed-off-by: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> >> ---
> >>  Documentation/devicetree/bindings/riscv/gf.yaml | 27 +++++++++++++++++++++++++
> >>  1 file changed, 27 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/riscv/gf.yaml b/Documentation/devicetree/bindings/riscv/gf.yaml
> >> new file mode 100644
> >> index 0000000000000000000000000000000000000000..060910c9b04f482aee6f08f8f72232acbad118bb
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/riscv/gf.yaml
> >> @@ -0,0 +1,27 @@
> >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> >> +%YAML 1.2
> >> +---
> >> +$id: http://devicetree.org/schemas/riscv/gf.yaml#
> >> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> +
> >> +title: GlobalFoundries MIPS SoC-based boards
> >> +
> >> +maintainers:
> >> +  - Djordje Todorovic <djordje.todorovic@htecgroup.com>
> >> +  - Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> >> +
> >> +description:
> >> +  GlobalFoundries MIPS SoC-based boards
> >> +
> >> +properties:
> >> +  $nodename:
> >> +    const: '/'
> >> +  compatible:
> >> +    oneOf:
> >> +      - description: Boston FPGA development board with a MIPS P8700 bitfile
> > I'm not convinced that this is specific enough at all.
> > I have absolutely no idea from this description if there's even a
> > specific FPGA involved here - this could mean a bitstream used on an Altera
> > platform or a Xilinx one, with totally different contents.
> I'll document this in v2. FWIW it's the identical board as [1], just with a 
> different bitstream. 
> > I'm only happy with FPGA bitstream content being supported if it is
> > versioned strictly and matches with some clear and obvious releases from
> > the vendor.
> I'll see if I can find one for v2. A version identifier would also work
> as a SoC-specific fallback, since it's the SoC that's bitstream content in our case.
> I'm not sure anything's public though. If not, I'd keep the board compatible 
> without a fallback (if possible). 

It's worth mentioning that this is the standard that we've discussed for
platforms on riscv, because of the nature of riscv and the ability of
anyone to create bitstreams for custom "SoCs" running on FPGAs.
It doesn't have to be public what a version actually means, but it must
be there.

Thanks,
Conor.

> >  I cannot even find this board by googling it, let alone find
> > clear information about what this could correspond to.
> >
> >> +        items:
> >> +          - const: gf,mips-p8700-boston
> > "items: - const" is the same as just having "const".
> Will fix in v2.
> >  SoC-specific
> > fallback is also missing, although in this case it'll be tricky to have
> > a meaningful one.
> 
> Links:
> [1] https://github.com/torvalds/linux/blob/master/arch/mips/boot/dts/img/boston.dts
> 
> Best regards,
> Aleksa

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
Cc: "alex@ghiti.fr" <alex@ghiti.fr>,
	"anup@brainfault.org" <anup@brainfault.org>,
	"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"daniel.lezcano@kernel.org" <daniel.lezcano@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Djordje Todorovic <Djordje.Todorovic@htecgroup.com>,
	"inochiama@outlook.com" <inochiama@outlook.com>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"palmer@dabbelt.com" <palmer@dabbelt.com>,
	"pjw@kernel.org" <pjw@kernel.org>,
	"radu@rendec.net" <radu@rendec.net>,
	"robh@kernel.org" <robh@kernel.org>,
	"tglx@kernel.org" <tglx@kernel.org>,
	"vladimir.kondratiev@mobileye.com"
	<vladimir.kondratiev@mobileye.com>
Subject: Re: [PATCH 3/9] dt-bindings: riscv: Add MIPS Boston board compatible
Date: Wed, 14 Oct 2026 17:33:32 +0100	[thread overview]
Message-ID: <20261014-defection-tiny-3e653ce56e60@spud> (raw)
In-Reply-To: <3d13e372-80da-44bb-845c-14f5022e326a@htecgroup.com>


[-- Attachment #1.1: Type: text/plain, Size: 3412 bytes --]

On Wed, Oct 14, 2026 at 01:16:16PM +0000, Aleksa Paunovic wrote:
> Hi Conor,
> On 9/15/26 19:58, Conor Dooley wrote:
> > On Mon, Sep 14, 2026 at 03:55:51PM +0200, Aleksa Paunovic via B4 Relay wrote:
> >> From: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> >>
> >> Document the MIPS Boston board compatible with a P8700 bitfile.
> >>
> >> Co-developed-by: Djordje Todorovic <djordje.todorovic@htecgroup.com>
> >> Signed-off-by: Djordje Todorovic <djordje.todorovic@htecgroup.com>
> >> Signed-off-by: Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> >> ---
> >>  Documentation/devicetree/bindings/riscv/gf.yaml | 27 +++++++++++++++++++++++++
> >>  1 file changed, 27 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/riscv/gf.yaml b/Documentation/devicetree/bindings/riscv/gf.yaml
> >> new file mode 100644
> >> index 0000000000000000000000000000000000000000..060910c9b04f482aee6f08f8f72232acbad118bb
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/riscv/gf.yaml
> >> @@ -0,0 +1,27 @@
> >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> >> +%YAML 1.2
> >> +---
> >> +$id: http://devicetree.org/schemas/riscv/gf.yaml#
> >> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> +
> >> +title: GlobalFoundries MIPS SoC-based boards
> >> +
> >> +maintainers:
> >> +  - Djordje Todorovic <djordje.todorovic@htecgroup.com>
> >> +  - Aleksa Paunovic <aleksa.paunovic@htecgroup.com>
> >> +
> >> +description:
> >> +  GlobalFoundries MIPS SoC-based boards
> >> +
> >> +properties:
> >> +  $nodename:
> >> +    const: '/'
> >> +  compatible:
> >> +    oneOf:
> >> +      - description: Boston FPGA development board with a MIPS P8700 bitfile
> > I'm not convinced that this is specific enough at all.
> > I have absolutely no idea from this description if there's even a
> > specific FPGA involved here - this could mean a bitstream used on an Altera
> > platform or a Xilinx one, with totally different contents.
> I'll document this in v2. FWIW it's the identical board as [1], just with a 
> different bitstream. 
> > I'm only happy with FPGA bitstream content being supported if it is
> > versioned strictly and matches with some clear and obvious releases from
> > the vendor.
> I'll see if I can find one for v2. A version identifier would also work
> as a SoC-specific fallback, since it's the SoC that's bitstream content in our case.
> I'm not sure anything's public though. If not, I'd keep the board compatible 
> without a fallback (if possible). 

It's worth mentioning that this is the standard that we've discussed for
platforms on riscv, because of the nature of riscv and the ability of
anyone to create bitstreams for custom "SoCs" running on FPGAs.
It doesn't have to be public what a version actually means, but it must
be there.

Thanks,
Conor.

> >  I cannot even find this board by googling it, let alone find
> > clear information about what this could correspond to.
> >
> >> +        items:
> >> +          - const: gf,mips-p8700-boston
> > "items: - const" is the same as just having "const".
> Will fix in v2.
> >  SoC-specific
> > fallback is also missing, although in this case it'll be tricky to have
> > a meaningful one.
> 
> Links:
> [1] https://github.com/torvalds/linux/blob/master/arch/mips/boot/dts/img/boston.dts
> 
> Best regards,
> Aleksa

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-10-14 16:33 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 13:55 [PATCH 0/9] Add support for MIPS P8700 Aleksa Paunovic via B4 Relay
2026-09-14 13:55 ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55 ` Aleksa Paunovic
2026-09-14 13:55 ` [PATCH 1/9] dt-bindings: vendor-prefixes: Add GlobalFoundries, Inc Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-15 17:23   ` Conor Dooley
2026-09-15 17:23     ` Conor Dooley
2026-09-17 11:50     ` Maciej W. Rozycki
2026-09-17 11:50       ` Maciej W. Rozycki
2026-10-14 12:54       ` Aleksa Paunovic
2026-10-14 12:54         ` Aleksa Paunovic
2026-10-14 13:02     ` Aleksa Paunovic
2026-10-14 13:02       ` Aleksa Paunovic
2026-09-14 13:55 ` [PATCH 2/9] dt-bindings: riscv: cpus: add gf,mips-p8700 Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-14 13:55 ` [PATCH 3/9] dt-bindings: riscv: Add MIPS Boston board compatible Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-15 17:58   ` Conor Dooley
2026-09-15 17:58     ` Conor Dooley
2026-09-17 13:23     ` Maciej W. Rozycki
2026-09-17 13:23       ` Maciej W. Rozycki
2026-10-14 13:17       ` Aleksa Paunovic
2026-10-14 13:17         ` Aleksa Paunovic
2026-10-14 13:16     ` Aleksa Paunovic
2026-10-14 13:16       ` Aleksa Paunovic
2026-10-14 16:33       ` Conor Dooley [this message]
2026-10-14 16:33         ` Conor Dooley
2026-09-14 13:55 ` [PATCH 4/9] dt-bindings: interrupt-controller: Add MIPS P8700 APLIC Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-15 18:16   ` Conor Dooley
2026-09-15 18:16     ` Conor Dooley
2026-10-14 13:25     ` Aleksa Paunovic
2026-10-14 13:25       ` Aleksa Paunovic
2026-09-14 13:55 ` [PATCH 5/9] dt-bindings: interrupt-controller: Add MIPS P8700 ACLINT MSWI Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-15 18:15   ` Conor Dooley
2026-09-15 18:15     ` Conor Dooley
2026-10-14 13:29     ` Aleksa Paunovic
2026-10-14 13:29       ` Aleksa Paunovic
2026-09-14 13:55 ` [PATCH 6/9] dt-bindings: timer: Add MIPS P8700 ACLINT MTIMER Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-21 18:21   ` Rob Herring
2026-09-21 18:21     ` Rob Herring
2026-10-14 13:30     ` Aleksa Paunovic
2026-10-14 13:30       ` Aleksa Paunovic
2026-09-14 13:55 ` [PATCH 7/9] dt-bindings: interrupt-controller: thead,c900-aclint-sswi: Add MIPS P8700 gf compatible Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-18 22:03   ` Rob Herring
2026-09-18 22:03     ` Rob Herring
2026-10-14 13:31     ` Aleksa Paunovic
2026-10-14 13:31       ` Aleksa Paunovic
2026-09-14 13:55 ` [PATCH 8/9] riscv: dts: gf: Initial support for the P8700 Boston board Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic
2026-09-14 15:08   ` sashiko-bot
2026-09-14 13:55 ` [PATCH 9/9] riscv: defconfig: Enable GF SoCs Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic via B4 Relay
2026-09-14 13:55   ` Aleksa Paunovic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261014-defection-tiny-3e653ce56e60@spud \
    --to=conor@kernel.org \
    --cc=Djordje.Todorovic@htecgroup.com \
    --cc=aleksa.paunovic@htecgroup.com \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=daniel.lezcano@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=inochiama@outlook.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=radu@rendec.net \
    --cc=robh@kernel.org \
    --cc=tglx@kernel.org \
    --cc=vladimir.kondratiev@mobileye.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.