Hi Geert, > Subject: Re: [PATCH 1/4] arm64: dts: renesas: rzg2l-smarc: Add common dtsi > file > > Hi Biju, > > On Tue, Feb 1, 2022 at 6:10 PM Biju Das <biju.das.jz@xxxxxxxxxxxxxx> > wrote: > > > Subject: Re: [PATCH 1/4] arm64: dts: renesas: rzg2l-smarc: Add > > > common dtsi file On Wed, Jan 19, 2022 at 10:52 AM Biju Das > > > <biju.das.jz@xxxxxxxxxxxxxx> > > > wrote: > > > > RZ/G2L and RZ/G2LC SoC use the same carrier board, but the SoM is > > > > different. > > > > > > > > Different pin mapping is possible on SoM. For eg:- RZ/G2L SMARC > > > > EVK uses SCIF2, whereas RZ/G2LC uses SCIF1 for the serial > > > > interface available on PMOD1. > > > > > > > > This patch adds support for handling the pin mapping differences > > > > by moving definitions common to RZ/G2L and RZ/G2LC to a common dtsi > file. > > > > > > > > Signed-off-by: Biju Das <biju.das.jz@xxxxxxxxxxxxxx> > > > > Reviewed-by: Lad Prabhakar > > > > <prabhakar.mahadev-lad.rj@xxxxxxxxxxxxxx> > > > > > --- a/arch/arm64/boot/dts/renesas/rzg2l-smarc.dtsi > > > > +++ b/arch/arm64/boot/dts/renesas/rzg2l-smarc.dtsi > > > > @@ -1,6 +1,6 @@ > > > > // SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > > > /* > > > > - * Device Tree Source for the RZ/G2L SMARC EVK common parts > > > > + * Device Tree Source for the RZ/G2L SMARC EVK parts > > > > * > > > > * Copyright (C) 2021 Renesas Electronics Corp. > > > > */ > > > > > > Note that the above conflicts with "[PATCH v2 11/12] arm64: dts: > > > renesas: Add initial device tree for RZ/V2L SMARC EVK"[1], which I > > > had queued in renesas-devel, but dropped again due to a missing > > > dependency on the clock bindings include file. In the meantime, the > > > updated clock bindings include file is ready. > > > > > > So, which one has the highest priority: this series, or RZ/V2L? > > > > V2L is higher priority. I will rebase and send V2. > > OK, I will make a renesas-devel release tomorrow morning, so you'll have a > fresh base. Thanks. > > Note that the RZ/V2L clock driver is still missing, but that driver will > follow a different upstream path anyway, so it can be done in parallel. Will do. Cheers, Biju
