Message ID | cover.1706194617.git.geert+renesas@glider.be (mailing list archive) |
---|---|
Headers | show |
Series | arm64: renesas: Add R-Car V4M and Gray Hawk Single support | expand |
On Thu, 25 Jan 2024 at 16:34, Geert Uytterhoeven <geert+renesas@glider.be> wrote: > > Hi all, > > This patch series adds initial support for the Renesas R-Car V4M > (R8A779G0) SoC and the Renesas Gray Hawk Single development board. > > As both driver code and DTS have hard dependencies on DT binding > definitions, most patches in this series are supposed to go in through > the renesas-devel and/or renesas-clk trees, using a shared branch for DT > binding definitions, as usual. For the PM domain patches (03, 04, 09), > Ulf already offered to apply these to his pmdomain tree, and provide an > immutable "dt" branch, to be pulled in my renesas-devel tree. Patch 3,4 and 9 (I dropped the copyright line in patch9, as pointed out by Niklas) applied for next, thanks! Patch 3,4 are also available at the immutable dt branch for you to pull in. Kind regards Uffe > > Changes compared to v1[1]: > - Add Acked-by, Reviewed-by, > - Add vendor-prefix to DT binding definition header file names and > update include guards, > - Add "board" to compatible comment, > - Add missing CP core clock, > - Add SoC name to top-level comment. > > For testing, this series can be found at > https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/v4m-gray-hawk-single-v2 > > Thanks for your comments! > > [1] "[PATCH 00/15] arm64: renesas: Add R-Car V4M and Gray Hawk Single > support" > https://lore.kernel.org/linux-renesas-soc/cover.1704726960.git.geert+renesas@glider.be > > Cong Dang (1): > clk: renesas: cpg-mssr: Add support for R-Car V4M > > Duy Nguyen (6): > dt-bindings: clock: Add R8A779H0 V4M CPG Core Clock Definitions > dt-bindings: power: renesas,rcar-sysc: Document R-Car V4M support > dt-bindings: power: Add r8a779h0 SYSC power domain definitions > pmdomain: renesas: r8a779h0-sysc: Add r8a779h0 support > soc: renesas: Identify R-Car V4M > soc: renesas: rcar-rst: Add support for R-Car V4M > > Geert Uytterhoeven (6): > dt-bindings: clock: renesas,cpg-mssr: Document R-Car V4M support > dt-bindings: reset: renesas,rst: Document R-Car V4M support > dt-bindings: soc: renesas: Document R-Car V4M Gray Hawk Single > clk: renesas: rcar-gen4: Add support for FRQCRC1 > soc: renesas: Introduce ARCH_RCAR_GEN4 > arm64: dts: renesas: Add Gray Hawk Single board support > > Hai Pham (1): > arm64: dts: renesas: Add Renesas R8A779H0 SoC support > > Linh Phung (1): > arm64: defconfig: Enable R8A779H0 SoC > > .../bindings/clock/renesas,cpg-mssr.yaml | 1 + > .../bindings/power/renesas,rcar-sysc.yaml | 1 + > .../bindings/reset/renesas,rst.yaml | 1 + > .../bindings/soc/renesas/renesas.yaml | 6 + > arch/arm64/boot/dts/renesas/Makefile | 2 + > .../dts/renesas/r8a779h0-gray-hawk-single.dts | 52 ++++ > arch/arm64/boot/dts/renesas/r8a779h0.dtsi | 121 +++++++++ > arch/arm64/configs/defconfig | 1 + > drivers/clk/renesas/Kconfig | 5 + > drivers/clk/renesas/Makefile | 1 + > drivers/clk/renesas/r8a779h0-cpg-mssr.c | 241 ++++++++++++++++++ > drivers/clk/renesas/rcar-gen4-cpg.c | 10 +- > drivers/clk/renesas/renesas-cpg-mssr.c | 6 + > drivers/clk/renesas/renesas-cpg-mssr.h | 1 + > drivers/pmdomain/renesas/Kconfig | 4 + > drivers/pmdomain/renesas/Makefile | 1 + > drivers/pmdomain/renesas/r8a779h0-sysc.c | 55 ++++ > drivers/pmdomain/renesas/rcar-gen4-sysc.c | 3 + > drivers/pmdomain/renesas/rcar-gen4-sysc.h | 1 + > drivers/soc/renesas/Kconfig | 17 +- > drivers/soc/renesas/rcar-rst.c | 1 + > drivers/soc/renesas/renesas-soc.c | 8 + > .../clock/renesas,r8a779h0-cpg-mssr.h | 96 +++++++ > .../dt-bindings/power/renesas,r8a779h0-sysc.h | 49 ++++ > 24 files changed, 679 insertions(+), 5 deletions(-) > create mode 100644 arch/arm64/boot/dts/renesas/r8a779h0-gray-hawk-single.dts > create mode 100644 arch/arm64/boot/dts/renesas/r8a779h0.dtsi > create mode 100644 drivers/clk/renesas/r8a779h0-cpg-mssr.c > create mode 100644 drivers/pmdomain/renesas/r8a779h0-sysc.c > create mode 100644 include/dt-bindings/clock/renesas,r8a779h0-cpg-mssr.h > create mode 100644 include/dt-bindings/power/renesas,r8a779h0-sysc.h > > -- > 2.34.1 > > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds
Hi Ulf, On Tue, Jan 30, 2024 at 2:11 PM Ulf Hansson <ulf.hansson@linaro.org> wrote: > On Thu, 25 Jan 2024 at 16:34, Geert Uytterhoeven > <geert+renesas@glider.be> wrote: > > This patch series adds initial support for the Renesas R-Car V4M > > (R8A779G0) SoC and the Renesas Gray Hawk Single development board. > > > > As both driver code and DTS have hard dependencies on DT binding > > definitions, most patches in this series are supposed to go in through > > the renesas-devel and/or renesas-clk trees, using a shared branch for DT > > binding definitions, as usual. For the PM domain patches (03, 04, 09), > > Ulf already offered to apply these to his pmdomain tree, and provide an > > immutable "dt" branch, to be pulled in my renesas-devel tree. > > Patch 3,4 and 9 (I dropped the copyright line in patch9, as pointed > out by Niklas) applied for next, thanks! > > Patch 3,4 are also available at the immutable dt branch for you to pull in. Thank you! I have pulled the immutable branch, added the remaining DT binding definitions, and queued all remaining patches. Gr{oetje,eeting}s, Geert
Hi Ulf, On Wed, Jan 31, 2024 at 3:56 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > On Tue, Jan 30, 2024 at 2:11 PM Ulf Hansson <ulf.hansson@linaro.org> wrote: > > On Thu, 25 Jan 2024 at 16:34, Geert Uytterhoeven > > <geert+renesas@glider.be> wrote: > > > This patch series adds initial support for the Renesas R-Car V4M > > > (R8A779G0) SoC and the Renesas Gray Hawk Single development board. > > > > > > As both driver code and DTS have hard dependencies on DT binding > > > definitions, most patches in this series are supposed to go in through > > > the renesas-devel and/or renesas-clk trees, using a shared branch for DT > > > binding definitions, as usual. For the PM domain patches (03, 04, 09), > > > Ulf already offered to apply these to his pmdomain tree, and provide an > > > immutable "dt" branch, to be pulled in my renesas-devel tree. > > > > Patch 3,4 and 9 (I dropped the copyright line in patch9, as pointed > > out by Niklas) applied for next, thanks! > > > > Patch 3,4 are also available at the immutable dt branch for you to pull in. > > Thank you! > > I have pulled the immutable branch, added the remaining DT binding > definitions, and queued all remaining patches. It looks like you have applied copies of all commits on the "dt" branch to the "next" branch, so now there are two copies? See the output of "git range-diff v6.8-rc1..pmdomain/dt v6.8-rc4..pmdomain/next". Gr{oetje,eeting}s, Geert
On Wed, 14 Feb 2024 at 09:35, Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > Hi Ulf, > > On Wed, Jan 31, 2024 at 3:56 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > On Tue, Jan 30, 2024 at 2:11 PM Ulf Hansson <ulf.hansson@linaro.org> wrote: > > > On Thu, 25 Jan 2024 at 16:34, Geert Uytterhoeven > > > <geert+renesas@glider.be> wrote: > > > > This patch series adds initial support for the Renesas R-Car V4M > > > > (R8A779G0) SoC and the Renesas Gray Hawk Single development board. > > > > > > > > As both driver code and DTS have hard dependencies on DT binding > > > > definitions, most patches in this series are supposed to go in through > > > > the renesas-devel and/or renesas-clk trees, using a shared branch for DT > > > > binding definitions, as usual. For the PM domain patches (03, 04, 09), > > > > Ulf already offered to apply these to his pmdomain tree, and provide an > > > > immutable "dt" branch, to be pulled in my renesas-devel tree. > > > > > > Patch 3,4 and 9 (I dropped the copyright line in patch9, as pointed > > > out by Niklas) applied for next, thanks! > > > > > > Patch 3,4 are also available at the immutable dt branch for you to pull in. > > > > Thank you! > > > > I have pulled the immutable branch, added the remaining DT binding > > definitions, and queued all remaining patches. > > It looks like you have applied copies of all commits on the "dt" > branch to the "next" > branch, so now there are two copies? > > See the output of "git range-diff v6.8-rc1..pmdomain/dt > v6.8-rc4..pmdomain/next". I screwed up - and thanks for pointing this out! Problem is taken care of now. Kind regards Uffe