From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v3] serial: 8250: add gpio support to exar
Date: Mon, 21 Dec 2015 20:49:51 +0530 [thread overview]
Message-ID: <20151221151904.GA23780@sudip-pc> (raw)
In-Reply-To: <20151220174208.1447d2f3@lxorguk.ukuu.org.uk>
On Sun, Dec 20, 2015 at 05:42:08PM +0000, One Thousand Gnomes wrote:
> > So then should I rewrite it as MFD or should it be like the way you
> > suggested in the other mail to have it as bool in the Kconfig and combine
> > the file with 8250_pci.c when the symbol is selected?
>
> Yes although I'm really not sure which is the best approach of the two.
Hi Alan and Andy,
I was trying like:
diff --git a/drivers/tty/serial/8250/Kconfig b/drivers/tty/serial/8250/Kconfig
index 6412f14..ec3d287 100644
--- a/drivers/tty/serial/8250/Kconfig
+++ b/drivers/tty/serial/8250/Kconfig
@@ -378,3 +378,11 @@ config SERIAL_8250_MID
Selecting this option will enable handling of the extra features
present on the UART found on Intel Medfield SOC and various other
Intel platforms.
+
+config SERIAL_8250_EXAR_GPIO
+ bool "Support for GPIO pins on XR17V352/354/358"
+ depends on SERIAL_8250_PCI && GPIOLIB
+ select GPIO_SYSFS
+ help
+ Selecting this option will enable handling of GPIO pins present
+ on Exar XR17V352/354/358 chips.
diff --git a/drivers/tty/serial/8250/Makefile b/drivers/tty/serial/8250/Makefile
index e177f86..1d0fce0 100644
--- a/drivers/tty/serial/8250/Makefile
+++ b/drivers/tty/serial/8250/Makefile
@@ -28,5 +28,8 @@ obj-$(CONFIG_SERIAL_8250_MT6577) += 8250_mtk.o
obj-$(CONFIG_SERIAL_8250_UNIPHIER) += 8250_uniphier.o
obj-$(CONFIG_SERIAL_8250_INGENIC) += 8250_ingenic.o
obj-$(CONFIG_SERIAL_8250_MID) += 8250_mid.o
+obj-$(CONFIG_SERIAL_8250_EXAR_GPIO) += exar_gpio.o
+exar_gpio-y := 8250_pci.o 8250_gpio.o
+
CFLAGS_8250_ingenic.o += -I$(srctree)/scripts/dtc/libfdt
But I am getting:
ERROR: "xr17v35x_gpio_exit" [drivers/tty/serial/8250/8250_pci.ko] undefined!
ERROR: "xr17v35x_gpio_init" [drivers/tty/serial/8250/8250_pci.ko] undefined!
I will need little hint for the Makefile, please. Its clear that i have
messed up.
regards
sudip
next prev parent reply other threads:[~2015-12-21 15:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 13:24 [PATCH v3] serial: 8250: add gpio support to exar Sudip Mukherjee
2015-12-20 14:18 ` Andy Shevchenko
2015-12-20 14:47 ` Sudip Mukherjee
2015-12-20 15:05 ` Andy Shevchenko
2015-12-20 16:41 ` One Thousand Gnomes
2015-12-20 17:11 ` Sudip Mukherjee
2015-12-20 17:28 ` One Thousand Gnomes
2015-12-20 16:43 ` One Thousand Gnomes
2015-12-20 17:28 ` Sudip Mukherjee
2015-12-20 17:42 ` One Thousand Gnomes
2015-12-21 15:19 ` Sudip Mukherjee [this message]
2015-12-21 18:28 ` Andy Shevchenko
2015-12-22 4:27 ` Sudip Mukherjee
2015-12-22 9:58 ` Andy Shevchenko
2015-12-22 10:08 ` Sudip Mukherjee
2015-12-22 10:15 ` Andy Shevchenko
2015-12-22 10:37 ` Sudip Mukherjee
2015-12-20 17:46 ` Andy Shevchenko
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=20151221151904.GA23780@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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