Add the SiFive FU740-C000 PLIC compatible string to the binding
documentation.

This follows the SiFive IP versioning scheme which requires SoC-specific
compatible strings for proper hardware identification, even when the IP
blocks are functionally identical.

Signed-off-by: Max Hsu <max.hsu@sifive.com>
---
 .../devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml      | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
index e0267223887e..351d26ab1956 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
@@ -63,6 +63,7 @@ properties:
               - eswin,eic7700-plic
               - microchip,pic64gx-plic
               - sifive,fu540-c000-plic
+              - sifive,fu740-c000-plic
               - spacemit,k1-plic
               - starfive,jh7100-plic
               - starfive,jh7110-plic

-- 
2.43.0

On Fri, Feb 20, 2026 at 04:27:06PM +0800, Max Hsu wrote:
> Add the SiFive FU740-C000 PLIC compatible string to the binding
> documentation.
> 
> This follows the SiFive IP versioning scheme which requires SoC-specific
> compatible strings for proper hardware identification, even when the IP
> blocks are functionally identical.

So do the general rules for devicetree bindings, that's not something
SiFive specific FWIW.
Acked-by: Conor Dooley <conor.dooley@microchip.com>

> 
> Signed-off-by: Max Hsu <max.hsu@sifive.com>
> ---
>  .../devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml      | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> index e0267223887e..351d26ab1956 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> @@ -63,6 +63,7 @@ properties:
>                - eswin,eic7700-plic
>                - microchip,pic64gx-plic
>                - sifive,fu540-c000-plic
> +              - sifive,fu740-c000-plic
>                - spacemit,k1-plic
>                - starfive,jh7100-plic
>                - starfive,jh7110-plic
> 
> -- 
> 2.43.0
> 

On Fri, Feb 20, 2026 at 09:23:18 +0000, Conor Dooley wrote:
> So do the general rules for devicetree bindings, that's not something
> SiFive specific FWIW.
> Acked-by: Conor Dooley <conor.dooley@microchip.com>

Thanks for the review and the ack, Conor.

I'll update the commit message in v2 to reference the general device
tree conventions.

Thanks,
Max Hsu

On Fri, Feb 20, 2026 at 5:23 PM Conor Dooley <conor@kernel.org> wrote:
>
> On Fri, Feb 20, 2026 at 04:27:06PM +0800, Max Hsu wrote:
> > Add the SiFive FU740-C000 PLIC compatible string to the binding
> > documentation.
> >
> > This follows the SiFive IP versioning scheme which requires SoC-specific
> > compatible strings for proper hardware identification, even when the IP
> > blocks are functionally identical.
>
> So do the general rules for devicetree bindings, that's not something
> SiFive specific FWIW.
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> >
> > Signed-off-by: Max Hsu <max.hsu@sifive.com>
> > ---
> >  .../devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml      | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> > index e0267223887e..351d26ab1956 100644
> > --- a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> > +++ b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> > @@ -63,6 +63,7 @@ properties:
> >                - eswin,eic7700-plic
> >                - microchip,pic64gx-plic
> >                - sifive,fu540-c000-plic
> > +              - sifive,fu740-c000-plic
> >                - spacemit,k1-plic
> >                - starfive,jh7100-plic
> >                - starfive,jh7110-plic
> >
> > --
> > 2.43.0
> >

On Sat, Feb 21, 2026 at 02:49:19AM +0800, Max Hsu wrote:
> On Fri, Feb 20, 2026 at 09:23:18 +0000, Conor Dooley wrote:
> > So do the general rules for devicetree bindings, that's not something
> > SiFive specific FWIW.
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> 
> Thanks for the review and the ack, Conor.
> 
> I'll update the commit message in v2 to reference the general device
> tree conventions.

It's fine as-is, was just pointing out that this is a general guideline.
The SiFive document is mostly about the naming of the fallback
compatibles etc that represent the IP core, rather than the soc-specific
part.