From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Cc: linux-sh@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/9] ARM: shmobile: dts: Enable SCIF_CLK frequency and pins
Date: Mon, 14 Dec 2015 19:58:15 +0100 [thread overview]
Message-ID: <1450119504-1517-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Simon, Magnus,
This patch series adds support for the external crystal feeding SCIF_CLK
to (H)SCIF on the various R-Car Gen1, Gen2, and Gen3 development boards.
This increases the range and accuracy of supported baud rates.
This series is an updated version of a part of a series I sent before as
"[PATCH v2 00/16] serial: sh-sci: Clock Cleanups"
(http://www.spinics.net/lists/linux-serial/msg19762.html). To reduce
(cross) dependencies, I split off the core patches and some DT parts
into separate series.
Changes compared to previous submission:
- Add support for r8a7778/bockw, r8a7779/marzen, r8a7790/lager,
r8a7791/porter, r8a7793/gose, r8a7794/alt, and r8a7794/silk,
- Add Reviewed-by.
Dependencies:
- This series is against renesas-devel-20151214-v4.4-rc5, with the
following applied on top:
- "[PATCH 0/7] ARM: shmobile: dtsi: Add SCIF fallback
compatibility strings",
- "[PATCH v3 00/12] ARM: shmobile: dtsi: Rename the serial port
clock to fck",
- "[PATCH v2 0/7] ARM: shmobile: dtsi: Add BRG support for
(H)SCIF",
- This has runtime dependencies on:
- "[PATCH 0/2] pinctrl: sh-pfc: r8a7791/r8a7795: Add SCIF_CLK
support",
- "[PATCH 0/3] pinctrl: sh-pfc: r8a7779/r8a7790/r8a7794: Add
SCIF_CLK support",
unless you want to depend on pinctrl as configured by U-Boot (on
most, but not all R-Car Gen2 boards).
Note that I plan to get the pinctrl dependencies in v4.5, so this
series should be OK to queue for v4.6.
Note that the bockw pinctrl support is already upstream.
Testing:
- This was tested locally on r8a7791/koelsch and r8a7795/salvator-x,
- This was tested remotely on r8a7778/bockw and r8a7779/marzen,
- Testing on other boards would be highly appreciated!
- Hints for various levels of testing:
- Change the "dev_dbg" after "done:" in
drivers/tty/serial/sh-sci.c to "dev_info" to print clock and bit
rate,
- "yes U | tr -d '\n' > /dev/ttySCx" outputs a square wave with a
frequency of half the bit rate on TXD,
- Modifying the frequency of SCIF_CLK causes garbage on the serial
console, unless you compensate by changing the bit rate in
/chosen/stdout-path,
- If you disable the SCIF_CLK, the brg_int clock will be used. If
you change that clock, you'll get garbage again,
- renesas-drivers-2015-12-14-v4.4-rc5 has all dependencies
https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git
Thanks!
Geert Uytterhoeven (9):
ARM: shmobile: alt dts: Enable SCIF_CLK frequency and pins
ARM: shmobile: bockw dts: Enable SCIF_CLK frequency and pins
ARM: shmobile: gose dts: Enable SCIF_CLK frequency and pins
ARM: shmobile: koelsch dts: Enable SCIF_CLK frequency and pins
ARM: shmobile: lager dts: Enable SCIF_CLK frequency and pins
ARM: shmobile: marzen dts: Enable SCIF_CLK frequency and pins
ARM: shmobile: porter dts: Enable SCIF_CLK frequency and pins
ARM: shmobile: silk dts: Enable SCIF_CLK frequency and pins
arm64: renesas: salvator-x dts: Enable SCIF_CLK frequency and pins
arch/arm/boot/dts/r8a7778-bockw.dts | 13 +++++++++++++
arch/arm/boot/dts/r8a7779-marzen.dts | 13 +++++++++++++
arch/arm/boot/dts/r8a7790-lager.dts | 13 +++++++++++++
arch/arm/boot/dts/r8a7791-koelsch.dts | 13 +++++++++++++
arch/arm/boot/dts/r8a7791-porter.dts | 13 +++++++++++++
arch/arm/boot/dts/r8a7793-gose.dts | 13 +++++++++++++
arch/arm/boot/dts/r8a7794-alt.dts | 13 +++++++++++++
arch/arm/boot/dts/r8a7794-silk.dts | 13 +++++++++++++
arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 12 ++++++++++++
9 files changed, 116 insertions(+)
--
1.9.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
next reply other threads:[~2015-12-14 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 18:58 Geert Uytterhoeven [this message]
2015-12-14 18:58 ` [PATCH v2 1/9] ARM: shmobile: alt dts: Enable SCIF_CLK frequency and pins Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v2 2/9] ARM: shmobile: bockw " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v2 3/9] ARM: shmobile: gose " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v2 5/9] ARM: shmobile: lager " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v2 6/9] ARM: shmobile: marzen " Geert Uytterhoeven
[not found] ` <1450119504-1517-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2015-12-14 18:58 ` [PATCH v2 4/9] ARM: shmobile: koelsch " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v2 7/9] ARM: shmobile: porter " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v2 8/9] ARM: shmobile: silk " Geert Uytterhoeven
2015-12-14 18:58 ` [PATCH v2 9/9] arm64: renesas: salvator-x " 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=1450119504-1517-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).