From: Peter Hurley <peter@hurleysoftware.com>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH 2/3] tty/serial: of_serial: add support for PXA/MMP uarts
Date: Wed, 28 Jan 2015 12:37:43 -0500 [thread overview]
Message-ID: <54C91E67.2070501@hurleysoftware.com> (raw)
In-Reply-To: <CAL_Jsq+wxY0=S1ff-Fk0xDBxHdhBvNopLpjfCETVoo_mou658w@mail.gmail.com>
On 01/27/2015 11:44 AM, Rob Herring wrote:
> On Tue, Jan 27, 2015 at 9:09 AM, Peter Hurley <peter@hurleysoftware.com> wrote:
[...]
>> Maybe Kconfig should warn if they're both built-in or both modules?
>
> Is there a way to do that?
Well, it's not what I had in mind originally, but the diff below
generates a broken dependencies warning without causing build problems:
$ scripts/kconfig/mconf Kconfig
warning: (SERIAL_PXA) selects TTYS_DRIVER_PXA which has unmet direct dependencies (TTY && HAS_IOMEM && !TTYS_DRIVER)
(My original idea was thwarted by the requirement that choice/endchoice
requires prompts).
That said, for PXA, I think we agree splitting out a standalone 8250 platform
driver is the solution.
Regards,
Peter Hurley
--
diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig
index 0fcbcd2..c367542 100644
--- a/drivers/tty/serial/8250/Kconfig
+++ b/drivers/tty/serial/8250/Kconfig
@@ -6,6 +6,7 @@
config SERIAL_8250
tristate "8250/16550 and compatible serial support"
select SERIAL_CORE
+ select TTYS_DRIVER
---help---
This selects whether you want to include the driver for the standard
serial ports. The standard answer is Y. People who might say N
diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
index c79b43c..10c3e27 100644
--- a/drivers/tty/serial/Kconfig
+++ b/drivers/tty/serial/Kconfig
@@ -7,6 +7,13 @@ if TTY
menu "Serial drivers"
depends on HAS_IOMEM
+config TTYS_DRIVER
+ tristate
+
+config TTYS_DRIVER_PXA
+ tristate
+ depends on !TTYS_DRIVER
+
config SERIAL_EARLYCON
bool
help
@@ -438,6 +445,7 @@ config SERIAL_PXA
bool "PXA serial port support"
depends on ARCH_PXA || ARCH_MMP
select SERIAL_CORE
+ select TTYS_DRIVER_PXA
help
If you have a machine based on an Intel XScale PXA2xx CPU you
can enable its onboard serial ports by enabling this option.
next prev parent reply other threads:[~2015-01-28 17:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 4:50 [PATCH 1/3] tty/serial: of_serial: add DT alias ID handling Rob Herring
2015-01-27 4:50 ` [PATCH 2/3] tty/serial: of_serial: add support for PXA/MMP uarts Rob Herring
2015-01-27 12:44 ` Peter Hurley
2015-01-27 14:30 ` Rob Herring
2015-01-27 15:09 ` Peter Hurley
2015-01-27 16:44 ` Rob Herring
2015-01-27 19:43 ` Peter Hurley
2015-01-28 14:21 ` Rob Herring
2015-01-28 17:06 ` Peter Hurley
2015-01-28 17:37 ` Peter Hurley [this message]
2015-01-30 19:51 ` Rob Herring
2015-01-30 20:24 ` Peter Hurley
2015-02-01 17:07 ` Peter Hurley
2015-01-27 4:50 ` [PATCH 3/3] tty/serial: 8250_early: Add support for PXA UARTs Rob Herring
2015-01-27 13:10 ` Peter Hurley
2015-01-27 14:05 ` Rob Herring
2015-01-27 14:25 ` Peter Hurley
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=54C91E67.2070501@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@kernel.org \
/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).