Hello Simon,

> From: Simon Horman <ho...@verge.net.au>
> Sent: 17 January 2019 10:51
> 
> On Wed, Jan 16, 2019 at 06:37:45PM +0000, Fabrizio Castro wrote:
> > This patch adds board cat874 (powered by the RZ/G2E) and board
> > cat875 (that sits on top of cat874). Both boards are made by
> > Silicon Linux.
> >
> > Signed-off-by: Fabrizio Castro <fabrizio.cas...@bp.renesas.com>
> > Reviewed-by: Chris Paterson <chris.paters...@renesas.com>
> > ---
> >  Documentation/devicetree/bindings/arm/renesas.yaml | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/renesas.yaml
> b/Documentation/devicetree/bindings/arm/renesas.yaml
> > index 5e9d486..9e1e07b 100644
> > --- a/Documentation/devicetree/bindings/arm/renesas.yaml
> > +++ b/Documentation/devicetree/bindings/arm/renesas.yaml
> > @@ -108,6 +108,14 @@ properties:
> >
> >        - description: RZ/G2E (R8A774C0)
> >          items:
> > +          - enum:
> > +              - si-linux,cat874 # Silicon Linux RZ/G2E 96board platform 
> > (CAT874)
> 
> Can I confirm that "96board platform" is correct for this board - I don't
> see it in the documentation I have, but that may not mean much.

The board follows the extended version of the Linaro 96board consumer edition 
(CE) specification [1].

You can see a pretty picture of the board on the CIP Blog [2].

[1] https://www.96boards.org/specifications/
[2] 
https://www.cip-project.org/blog/2018/10/23/renesas-rz-g2m-96ce-board-adopted-as-arm64-reference-board-for-the-next-cip-slts-kernel

Kind regards, Chris

> 
> 
> That aside, I'd like to wait for Rob to indicate if he will accept
> patch 1, which adds si-linux as a vendor, before I apply this patch.
> 
> > +          - const: renesas,r8a774c0
> > +
> > +      - items:
> > +          - enum:
> > +              - si-linux,cat875 # Silicon Linux sub board for CAT874 
> > (CAT875)
> > +          - const: si-linux,cat874
> >            - const: renesas,r8a774c0
> >
> >        - description: R-Car M1A (R8A77781)
> > --
> > 2.7.4
> >

Reply via email to