From: Geert Uytterhoeven <geert@linux-m68k.org> To: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Geert Uytterhoeven <geert+renesas@glider.be>, Magnus Damm <magnus.damm@gmail.com>, Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v2 3/4] arm64: dts: renesas: rcar-gen3: Add reset control properties for display Date: Wed, 19 Feb 2020 16:55:52 +0100 [thread overview] Message-ID: <CAMuHMdUjVqC=AsNjO1icMyNRrdeMVed_HxMzn6HY=fRt+LvUwQ@mail.gmail.com> (raw) In-Reply-To: <20200219153339.GT5070@pendragon.ideasonboard.com> Hi Laurent, On Wed, Feb 19, 2020 at 4:33 PM Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote: > On Tue, Feb 18, 2020 at 02:30:18PM +0100, Geert Uytterhoeven wrote: > > Add reset control properties to the device nodes for the Display Units > > on all supported R-Car Gen3 SoCs. Note that on these SoCs, there is > > only a single reset for each pair of DU channels. > > > > The display nodes on R-Car V3M and V3H already had "resets" properties, > > but lacked the corresponding "reset-names" properties. > > > > Join the clocks lines while at it, to increase uniformity. > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > > --- a/arch/arm64/boot/dts/renesas/r8a77965.dtsi > > +++ b/arch/arm64/boot/dts/renesas/r8a77965.dtsi > > @@ -2503,10 +2503,11 @@ > > interrupts = <GIC_SPI 256 IRQ_TYPE_LEVEL_HIGH>, > > <GIC_SPI 268 IRQ_TYPE_LEVEL_HIGH>, > > <GIC_SPI 270 IRQ_TYPE_LEVEL_HIGH>; > > - clocks = <&cpg CPG_MOD 724>, > > - <&cpg CPG_MOD 723>, > > + clocks = <&cpg CPG_MOD 724>, <&cpg CPG_MOD 723>, > > <&cpg CPG_MOD 721>; > > clock-names = "du.0", "du.1", "du.3"; > > + resets = <&cpg 724>, <&cpg 722>; > > + reset-names = "du.0", "du.3"; > > I wonder if this should be du.2, especially given that 722 corresponds > to the non-existing DU2 channel. It's a bit of a mess at the hardware Just following the bindings: "du.3" is the lowest channel that is affected by the reset. > level :-S Note that supporting R-Car H3-N will make your^H^H^H^Hthe rcar-du device driver writer's life even more miserable, as suddenly there is no longer a DU2, while the single unified Display Unit node prevents the DTS writer from not setting the DU2's status to "okay" in the board DTS file. But you might look at the ports submode? 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
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>, Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>, Magnus Damm <magnus.damm@gmail.com>, Linux ARM <linux-arm-kernel@lists.infradead.org>, Geert Uytterhoeven <geert+renesas@glider.be> Subject: Re: [PATCH v2 3/4] arm64: dts: renesas: rcar-gen3: Add reset control properties for display Date: Wed, 19 Feb 2020 16:55:52 +0100 [thread overview] Message-ID: <CAMuHMdUjVqC=AsNjO1icMyNRrdeMVed_HxMzn6HY=fRt+LvUwQ@mail.gmail.com> (raw) In-Reply-To: <20200219153339.GT5070@pendragon.ideasonboard.com> Hi Laurent, On Wed, Feb 19, 2020 at 4:33 PM Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote: > On Tue, Feb 18, 2020 at 02:30:18PM +0100, Geert Uytterhoeven wrote: > > Add reset control properties to the device nodes for the Display Units > > on all supported R-Car Gen3 SoCs. Note that on these SoCs, there is > > only a single reset for each pair of DU channels. > > > > The display nodes on R-Car V3M and V3H already had "resets" properties, > > but lacked the corresponding "reset-names" properties. > > > > Join the clocks lines while at it, to increase uniformity. > > > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > > --- a/arch/arm64/boot/dts/renesas/r8a77965.dtsi > > +++ b/arch/arm64/boot/dts/renesas/r8a77965.dtsi > > @@ -2503,10 +2503,11 @@ > > interrupts = <GIC_SPI 256 IRQ_TYPE_LEVEL_HIGH>, > > <GIC_SPI 268 IRQ_TYPE_LEVEL_HIGH>, > > <GIC_SPI 270 IRQ_TYPE_LEVEL_HIGH>; > > - clocks = <&cpg CPG_MOD 724>, > > - <&cpg CPG_MOD 723>, > > + clocks = <&cpg CPG_MOD 724>, <&cpg CPG_MOD 723>, > > <&cpg CPG_MOD 721>; > > clock-names = "du.0", "du.1", "du.3"; > > + resets = <&cpg 724>, <&cpg 722>; > > + reset-names = "du.0", "du.3"; > > I wonder if this should be du.2, especially given that 722 corresponds > to the non-existing DU2 channel. It's a bit of a mess at the hardware Just following the bindings: "du.3" is the lowest channel that is affected by the reset. > level :-S Note that supporting R-Car H3-N will make your^H^H^H^Hthe rcar-du device driver writer's life even more miserable, as suddenly there is no longer a DU2, while the single unified Display Unit node prevents the DTS writer from not setting the DU2's status to "okay" in the board DTS file. But you might look at the ports submode? 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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-19 15:56 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-18 13:30 [PATCH v2 0/4] arm: dts: renesas: Add reset control properties for display Geert Uytterhoeven 2020-02-18 13:30 ` Geert Uytterhoeven 2020-02-18 13:30 ` [PATCH v2 1/4] ARM: dts: rcar-gen2: " Geert Uytterhoeven 2020-02-18 13:30 ` Geert Uytterhoeven 2020-02-19 10:59 ` Ulrich Hecht 2020-02-19 10:59 ` Ulrich Hecht 2020-02-19 15:27 ` Laurent Pinchart 2020-02-19 15:27 ` Laurent Pinchart 2020-02-19 15:30 ` Geert Uytterhoeven 2020-02-19 15:30 ` Geert Uytterhoeven 2020-02-18 13:30 ` [PATCH v2 2/4] ARM: dts: rzg1: " Geert Uytterhoeven 2020-02-18 13:30 ` Geert Uytterhoeven 2020-02-19 10:59 ` Ulrich Hecht 2020-02-19 10:59 ` Ulrich Hecht 2020-02-19 15:28 ` Laurent Pinchart 2020-02-19 15:28 ` Laurent Pinchart 2020-02-18 13:30 ` [PATCH v2 3/4] arm64: dts: renesas: rcar-gen3: " Geert Uytterhoeven 2020-02-18 13:30 ` Geert Uytterhoeven 2020-02-19 11:00 ` Ulrich Hecht 2020-02-19 11:00 ` Ulrich Hecht 2020-02-19 15:33 ` Laurent Pinchart 2020-02-19 15:33 ` Laurent Pinchart 2020-02-19 15:55 ` Geert Uytterhoeven [this message] 2020-02-19 15:55 ` Geert Uytterhoeven 2020-02-19 16:06 ` Laurent Pinchart 2020-02-19 16:06 ` Laurent Pinchart 2020-02-18 13:30 ` [PATCH v2 4/4] arm64: dts: renesas: rzg2: " Geert Uytterhoeven 2020-02-18 13:30 ` Geert Uytterhoeven 2020-02-19 11:01 ` Ulrich Hecht 2020-02-19 11:01 ` Ulrich Hecht 2020-02-19 15:40 ` Laurent Pinchart 2020-02-19 15:40 ` Laurent Pinchart
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMuHMdUjVqC=AsNjO1icMyNRrdeMVed_HxMzn6HY=fRt+LvUwQ@mail.gmail.com' \ --to=geert@linux-m68k.org \ --cc=geert+renesas@glider.be \ --cc=kieran.bingham+renesas@ideasonboard.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=magnus.damm@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.