From: Geert Uytterhoeven <geert@linux-m68k.org> To: Wolfram Sang <wsa@kernel.org> Cc: Magnus Damm <magnus.damm@gmail.com>, Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>, linux-renesas-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64: dts: renesas: r8a779g0: Fix HSCIF0 "brg_int" clock Date: Mon, 10 Oct 2022 13:12:05 +0200 [thread overview] Message-ID: <CAMuHMdUBJi9kgbXKLzmz51u-46sXk2gh-mbcPZ0-vpvANDLCOg@mail.gmail.com> (raw) In-Reply-To: <Y0PQDVzGj8O4oZZY@shikoro> Hi Wolfram, On Mon, Oct 10, 2022 at 9:56 AM Wolfram Sang <wsa@kernel.org> wrote: > On Fri, Oct 07, 2022 at 05:20:03PM +0200, Geert Uytterhoeven wrote: > > As serial communication requires a clock signal, the High Speed Serial > > Communication Interfaces with FIFO (HSCIF) are clocked by a clock that > > is not affected by Spread Spectrum or Fractional Multiplication. > > > > Hence change the clock input for the HSCIF0 Baud Rate Generator internal > > clock from the S0D3_PER clock to the SASYNCPERD1 clock (which has the > > same clock rate), cfr. R-Car V4H Hardware User's Manual rev. 0.54. > > > > Fixes: 987da486d84a5643 ("arm64: dts: renesas: Add Renesas R8A779G0 SoC support") > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > > Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Thanks! > Do we need to wait for the clarification about the docs mentioned in > another thread? This one matches the docs ;-) It's the module clock's parent in the clock driver which doesn't seem to match actual hardware. 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: Wolfram Sang <wsa@kernel.org> Cc: Magnus Damm <magnus.damm@gmail.com>, Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>, linux-renesas-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] arm64: dts: renesas: r8a779g0: Fix HSCIF0 "brg_int" clock Date: Mon, 10 Oct 2022 13:12:05 +0200 [thread overview] Message-ID: <CAMuHMdUBJi9kgbXKLzmz51u-46sXk2gh-mbcPZ0-vpvANDLCOg@mail.gmail.com> (raw) In-Reply-To: <Y0PQDVzGj8O4oZZY@shikoro> Hi Wolfram, On Mon, Oct 10, 2022 at 9:56 AM Wolfram Sang <wsa@kernel.org> wrote: > On Fri, Oct 07, 2022 at 05:20:03PM +0200, Geert Uytterhoeven wrote: > > As serial communication requires a clock signal, the High Speed Serial > > Communication Interfaces with FIFO (HSCIF) are clocked by a clock that > > is not affected by Spread Spectrum or Fractional Multiplication. > > > > Hence change the clock input for the HSCIF0 Baud Rate Generator internal > > clock from the S0D3_PER clock to the SASYNCPERD1 clock (which has the > > same clock rate), cfr. R-Car V4H Hardware User's Manual rev. 0.54. > > > > Fixes: 987da486d84a5643 ("arm64: dts: renesas: Add Renesas R8A779G0 SoC support") > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > > Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Thanks! > Do we need to wait for the clarification about the docs mentioned in > another thread? This one matches the docs ;-) It's the module clock's parent in the clock driver which doesn't seem to match actual hardware. 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:[~2022-10-10 11:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-07 15:20 [PATCH] arm64: dts: renesas: r8a779g0: Fix HSCIF0 "brg_int" clock Geert Uytterhoeven 2022-10-07 15:20 ` Geert Uytterhoeven 2022-10-10 7:55 ` Wolfram Sang 2022-10-10 7:55 ` Wolfram Sang 2022-10-10 11:12 ` Geert Uytterhoeven [this message] 2022-10-10 11:12 ` Geert Uytterhoeven
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=CAMuHMdUBJi9kgbXKLzmz51u-46sXk2gh-mbcPZ0-vpvANDLCOg@mail.gmail.com \ --to=geert@linux-m68k.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=magnus.damm@gmail.com \ --cc=wsa@kernel.org \ --cc=yoshihiro.shimoda.uh@renesas.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.