linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>
Cc: Jiri Slaby <jslaby@suse.com>,
	linux-serial@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	uclinux-h8-devel@lists.sourceforge.jp, linux-sh@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 4/5] tty: serial: sh-sci: Hide DMA config question
Date: Thu, 30 Nov 2017 13:12:01 +0000	[thread overview]
Message-ID: <1512047522-16312-5-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1512047522-16312-1-git-send-email-geert+renesas@glider.be>

On most Renesas ARM platforms, the SCIF serial ports can be used with
DMA, so most users will want DMA support to be enabled.

On SuperH platforms, SCI(F) serial ports cannot be used with DMA yet
(see also commit 219fb0c1436e4893 ("serial: sh-sci: Remove the platform
data dma slave rx/tx channel IDs")), so users will want it disabled to
reduce kernel size.

Hence follow the above rationale to configure the default, unless
CONFIG_EXPERT is enabled.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
 drivers/tty/serial/Kconfig | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index 952a2c6a9da08fdd..4e6dfb0a762b5807 100644
--- a/drivers/tty/serial/Kconfig
+++ b/drivers/tty/serial/Kconfig
@@ -781,8 +781,9 @@ config SERIAL_SH_SCI_EARLYCON
 	default ARCH_RENESAS || H8300
 
 config SERIAL_SH_SCI_DMA
-	bool "DMA support"
+	bool "DMA support" if EXPERT
 	depends on SERIAL_SH_SCI && DMA_ENGINE
+	default ARCH_RENESAS
 
 config SERIAL_PNX8XXX
 	bool "Enable PNX8XXX SoCs' UART Support"
-- 
2.7.4


  parent reply	other threads:[~2017-11-30 13:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 13:11 [PATCH 0/5] tty: serial: sh-sci: Hide driver specific config questions Geert Uytterhoeven
2017-11-30 13:11 ` [PATCH 1/5] tty: serial: sh-sci: Hide number of ports config question Geert Uytterhoeven
2017-11-30 13:11 ` [PATCH 2/5] tty: serial: sh-sci: Hide serial console " Geert Uytterhoeven
2017-11-30 13:12 ` [PATCH 3/5] tty: serial: sh-sci: Hide earlycon " Geert Uytterhoeven
2018-04-15  0:34   ` Rich Felker
2018-04-15 18:58     ` Geert Uytterhoeven
2018-04-15 19:09       ` Rich Felker
2018-05-02  2:32         ` Rob Herring
2018-05-04  7:35           ` Geert Uytterhoeven
2017-11-30 13:12 ` Geert Uytterhoeven [this message]
2017-11-30 13:12 ` [PATCH/RFC 5/5] ARM: shmobile: defconfig: Disable CONFIG_EMBEDDED Geert Uytterhoeven
2017-12-01  8:33   ` Simon Horman
2017-12-04  9:46     ` Geert Uytterhoeven
2017-12-05  8:28       ` Simon Horman
2017-12-09  2:18         ` Rob Landley
2017-12-09  8:54           ` 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=1512047522-16312-5-git-send-email-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=dalias@libc.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@verge.net.au \
    --cc=jslaby@suse.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=uclinux-h8-devel@lists.sourceforge.jp \
    --cc=ysato@users.sourceforge.jp \
    /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).