From: Tushar Behera <tushar.behera@linaro.org>
To: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Cc: jslaby@suse.cz, gregkh@linuxfoundation.org,
linux@arm.linux.org.uk, ben.dooks@codethink.co.uk,
broonie@kernel.org
Subject: [PATCH 1/2] serial: samsung: Move uart_register_driver call to device probe
Date: Mon, 20 Jan 2014 14:32:34 +0530 [thread overview]
Message-ID: <1390208555-27770-2-git-send-email-tushar.behera@linaro.org> (raw)
In-Reply-To: <1390208555-27770-1-git-send-email-tushar.behera@linaro.org>
uart_register_driver call binds the driver to a specific device
node through tty_register_driver call. This should typically happen
during device probe call.
In a multiplatform scenario, it is possible that multiple serial
drivers are part of the kernel. Currently the driver registration fails
if multiple serial drivers with same default major/minor numbers are
included in the kernel.
A typical case is observed with amba-pl011 and samsung-uart drivers.
Signed-off-by: Tushar Behera <tushar.behera@linaro.org>
---
drivers/tty/serial/samsung.c | 40 +++++++++++-----------------------------
1 file changed, 11 insertions(+), 29 deletions(-)
diff --git a/drivers/tty/serial/samsung.c b/drivers/tty/serial/samsung.c
index c1af04d..f8f41dc 100644
--- a/drivers/tty/serial/samsung.c
+++ b/drivers/tty/serial/samsung.c
@@ -1283,6 +1283,14 @@ static int s3c24xx_serial_probe(struct platform_device *pdev)
if (ret < 0)
goto probe_err;
+ if (!s3c24xx_uart_drv.state) {
+ ret = uart_register_driver(&s3c24xx_uart_drv);
+ if (ret < 0) {
+ pr_err("Failed to register Samsung UART driver\n");
+ return ret;
+ }
+ }
+
dbg("%s: adding port\n", __func__);
uart_add_one_port(&s3c24xx_uart_drv, &ourport->port);
platform_set_drvdata(pdev, &ourport->port);
@@ -1315,6 +1323,8 @@ static int s3c24xx_serial_remove(struct platform_device *dev)
uart_remove_one_port(&s3c24xx_uart_drv, port);
}
+ uart_unregister_driver(&s3c24xx_uart_drv);
+
return 0;
}
@@ -1814,35 +1824,7 @@ static struct platform_driver samsung_serial_driver = {
},
};
-/* module initialisation code */
-
-static int __init s3c24xx_serial_modinit(void)
-{
- int ret;
-
- ret = uart_register_driver(&s3c24xx_uart_drv);
- if (ret < 0) {
- pr_err("Failed to register Samsung UART driver\n");
- return ret;
- }
-
- ret = platform_driver_register(&samsung_serial_driver);
- if (ret < 0) {
- pr_err("Failed to register platform driver\n");
- uart_unregister_driver(&s3c24xx_uart_drv);
- }
-
- return ret;
-}
-
-static void __exit s3c24xx_serial_modexit(void)
-{
- platform_driver_unregister(&samsung_serial_driver);
- uart_unregister_driver(&s3c24xx_uart_drv);
-}
-
-module_init(s3c24xx_serial_modinit);
-module_exit(s3c24xx_serial_modexit);
+module_platform_driver(samsung_serial_driver);
MODULE_ALIAS("platform:samsung-uart");
MODULE_DESCRIPTION("Samsung SoC Serial port driver");
--
1.7.9.5
next prev parent reply other threads:[~2014-01-20 9:07 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 9:02 [PATCH 0/2] serial: Move uart_register_driver call to device probe Tushar Behera
2014-01-20 9:02 ` Tushar Behera [this message]
2014-01-20 10:05 ` [PATCH 1/2] serial: samsung: " Russell King - ARM Linux
2014-01-20 11:53 ` Tushar Behera
2014-01-20 12:26 ` Russell King - ARM Linux
2014-01-20 21:43 ` Alan Cox
2014-01-20 23:14 ` Mark Brown
2014-01-20 23:21 ` Russell King - ARM Linux
2014-01-20 23:35 ` Alan Cox
2014-01-20 23:52 ` Greg Kroah-Hartman
2014-01-20 23:47 ` Alan Cox
2014-01-21 0:16 ` Russell King - ARM Linux
2014-01-21 9:03 ` Alan Cox
2014-01-21 9:49 ` Russell King - ARM Linux
[not found] ` <50b66ac6-1150-4ad7-aeaf-3d0dce77334d@email.android.com>
2014-01-26 11:54 ` Russell King - ARM Linux
2014-01-27 4:30 ` Nicolas Pitre
2014-01-27 10:07 ` Alan Cox
2014-01-27 12:32 ` Russell King - ARM Linux
2014-01-27 15:03 ` Nicolas Pitre
2014-01-21 16:59 ` Mark Brown
2014-01-21 18:30 ` Russell King - ARM Linux
2014-01-23 18:04 ` Alan Cox
2014-01-23 18:40 ` Mark Brown
2014-01-23 18:47 ` Tomasz Figa
2014-01-23 19:36 ` Mark Brown
2014-01-23 19:51 ` Alan Cox
2014-01-23 20:05 ` Mark Brown
2014-01-23 21:33 ` Alan Cox
2014-01-24 12:03 ` Mark Brown
2014-01-24 14:38 ` Alan Cox
2014-01-27 0:15 ` Mark Brown
2014-01-26 21:09 ` Pavel Machek
2014-01-27 0:04 ` Alan Cox
2014-01-20 21:16 ` Greg KH
2014-01-20 21:32 ` Russell King - ARM Linux
2014-01-20 23:11 ` Greg KH
2014-01-20 23:16 ` Russell King - ARM Linux
2014-01-20 23:51 ` Greg KH
2014-01-21 0:07 ` Russell King - ARM Linux
2014-01-21 0:26 ` Greg KH
2014-01-21 0:38 ` Russell King - ARM Linux
2014-01-21 9:25 ` One Thousand Gnomes
2014-01-21 9:45 ` Russell King - ARM Linux
2014-01-20 9:02 ` [PATCH 2/2] serial: pl011: " Tushar Behera
2014-01-20 10:04 ` Russell King - ARM Linux
2014-02-13 18:12 ` Greg KH
2014-02-13 18:15 ` Russell King - ARM Linux
2014-02-13 18:27 ` Greg KH
2014-02-13 18:42 ` Russell King - ARM Linux
2014-02-13 23:26 ` Greg KH
2014-02-14 0:07 ` Russell King - ARM Linux
2014-02-14 0:14 ` Greg KH
2014-02-14 0:38 ` Russell King - ARM Linux
2014-02-17 15:35 ` One Thousand Gnomes
2014-02-17 15:54 ` One Thousand Gnomes
2014-02-17 23:50 ` Mark Brown
2014-02-18 10:09 ` Etched Pixels
2014-02-19 13:57 ` Mark Brown
2014-02-19 14:47 ` One Thousand Gnomes
2014-02-19 15:53 ` Mark Brown
2014-02-19 0:47 ` One Thousand Gnomes
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=1390208555-27770-2-git-send-email-tushar.behera@linaro.org \
--to=tushar.behera@linaro.org \
--cc=ben.dooks@codethink.co.uk \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).