From: Eugeniu Rosca <roscaeugeniu@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>,
Chris Brandt <chris.brandt@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "George G . Davis" <george_davis@mentor.com>,
Andy Lowe <andy_lowe@mentor.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: [PATCH 0/6] Zap SCIF2 DMA configuration in R-Car Gen3 DTS
Date: Sat, 4 May 2019 02:42:52 +0200 [thread overview]
Message-ID: <20190504004258.23574-1-erosca@de.adit-jv.com> (raw)
This series is triggered by a regression on M3 targets caused by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=703db5d1b175
("arm64: dts: renesas: r8a7796: Enable DMA for SCIF2"), when applied
on top of rcar-3.9.x Renesas official kernel.
This collection of patches attempts to consistently propagate the fix
across the existing R-Car3 DTS. Full story is placed into
commit ("Revert "arm64: dts: renesas: r8a7796: Enable DMA for SCIF2"").
While debugging drivers/tty/serial/sh-sci.c, a minor update avoiding
__ptrval__ in dev_dbg() is included here as well.
Tested using v5.1-rc7-131-gea9866793d1e on:
- H3-ES2.0-ULCB
- M3N-ES1.1-ULCB
- M3-ES1.1-Salvator-XS
Eugeniu Rosca (6):
serial: sh-sci: Reveal ptrval in dev_dbg
Revert "arm64: dts: renesas: r8a7796: Enable DMA for SCIF2"
arm64: dts: renesas: r8a7795: zap dma configuration in scif2
Revert "arm64: dts: renesas: r8a77965: Enable DMA for SCIF2"
Revert "arm64: dts: renesas: r8a77990: Enable DMA for SCIF2"
Revert "arm64: dts: renesas: r8a77995: add DMA for SCIF2"
arch/arm64/boot/dts/renesas/r8a7795.dtsi | 3 ---
arch/arm64/boot/dts/renesas/r8a7796.dtsi | 3 ---
arch/arm64/boot/dts/renesas/r8a77965.dtsi | 3 ---
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 4 +---
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 3 ---
drivers/tty/serial/sh-sci.c | 8 ++++----
6 files changed, 5 insertions(+), 19 deletions(-)
--
2.21.0
next reply other threads:[~2019-05-04 0:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 0:42 Eugeniu Rosca [this message]
2019-05-04 0:42 ` [PATCH 1/6] serial: sh-sci: Reveal ptrval in dev_dbg Eugeniu Rosca
2019-05-06 13:47 ` Simon Horman
2019-05-06 15:24 ` Eugeniu Rosca
2019-05-06 16:46 ` Geert Uytterhoeven
2019-05-06 17:12 ` Eugeniu Rosca
2019-05-04 0:42 ` [PATCH 2/6] Revert "arm64: dts: renesas: r8a7796: Enable DMA for SCIF2" Eugeniu Rosca
2019-05-06 10:02 ` Geert Uytterhoeven
2019-05-06 19:42 ` Eugeniu Rosca
[not found] ` <1557413011-1662-1-git-send-email-george_davis@mentor.com>
2019-05-10 17:10 ` [PATCH] serial: sh-sci: disable DMA for uart_console Eugeniu Rosca
2019-05-10 18:38 ` George G. Davis
2019-05-13 10:28 ` Eugeniu Rosca
2019-05-13 11:13 ` Geert Uytterhoeven
2019-05-13 11:42 ` Simon Horman
2019-05-13 13:51 ` Wolfram Sang
2019-05-13 15:43 ` George G. Davis
2019-05-20 2:18 ` [PATCH 2/6] Revert "arm64: dts: renesas: r8a7796: Enable DMA for SCIF2" Yoshihiro Shimoda
2019-05-20 7:37 ` Geert Uytterhoeven
2019-05-20 9:52 ` Yoshihiro Shimoda
2019-05-04 0:42 ` [PATCH 3/6] arm64: dts: renesas: r8a7795: zap dma configuration in scif2 Eugeniu Rosca
2019-05-04 0:42 ` [PATCH 4/6] Revert "arm64: dts: renesas: r8a77965: Enable DMA for SCIF2" Eugeniu Rosca
2019-05-04 0:42 ` [PATCH 5/6] Revert "arm64: dts: renesas: r8a77990: " Eugeniu Rosca
2019-05-04 0:42 ` [PATCH 6/6] Revert "arm64: dts: renesas: r8a77995: add " Eugeniu Rosca
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=20190504004258.23574-1-erosca@de.adit-jv.com \
--to=roscaeugeniu@gmail.com \
--cc=andy_lowe@mentor.com \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=erosca@de.adit-jv.com \
--cc=geert+renesas@glider.be \
--cc=george_davis@mentor.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=ulrich.hecht+renesas@gmail.com \
--cc=wsa+renesas@sang-engineering.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).