Hi Geert-san, > From: Geert Uytterhoeven, Sent: Wednesday, December 18, 2019 3:39 AM > > Hi all, > > Despite using the same compatible values ("r8a7795"-based) because of > historical reasons, R-Car H3 ES1.x (R8A77950) and R-Car H3 ES2.0+ > (R8A77951) are really different SoCs, with different part numbers. > > Hence this patch series splits the config symbols for R-Car H3, and > renames the related DTS files, to maintain a clear separation between > early (ES1.x) and later (ES2.0+) SoC revisions. This will pave the way > for configuring out support for early SoC revisions, which can reduce > kernel size, especially in the pin control subsystem. > This is similar to the recent split of R8A7796 symbols for R-Car M3-W > (R8A77960) and M3-W+ (R8A77961)[1], and the related DTS file renames[2], > but different due to the sharing of compatible values between R-Car H3 > ES1.x and H3 ES2.0+. > > This series also includes the rename/cleanup of the ULCB DTS file names, > as suggested by Eugeniu Rosca. As DTS files are already being renamed > for v5.6[2], it makes sense to combine them with other renames, to avoid > inconveniencing the user with multiple renames in multiple kernel > versions. > > The pin control part will be handled in a separate patch. > > For your convenience, all of this is available in the > topic/r8a7795-rename-v1 branch of my renesas-drivers git repository at > git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git. > > Thanks for your comments! Thank you for the patches! Reviewed-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@xxxxxxxxxxx> Also I tested on both R-Car H3 ES1.1 Salvator-X and R-Car H3 ES3.0 Salvator-XS, and the kernel can boot on these boards. So, Tested-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@xxxxxxxxxxx> Best regards, Yoshihiro Shimoda