From: <shubhrajyoti.datta@gmail.com>
To: <linux-serial@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <gregkh@linuxfoundation.org>, <jslaby@suse.com>,
<jacmet@sunsite.dk>,
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>,
Michal Simek <michal.simek@xilinx.com>
Subject: [LINUX PATCHv3 5/9] serial-uartlite: Fix the unbind path
Date: Tue, 16 Oct 2018 15:48:04 +0530 [thread overview]
Message-ID: <1539685088-13465-6-git-send-email-shubhrajyoti.datta@gmail.com> (raw)
In-Reply-To: <1539685088-13465-1-git-send-email-shubhrajyoti.datta@gmail.com>
From: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Currently the clocks are not enabled at probe but when the port is used.
Remove the unconditional disable at remove.
Fixes the below
[ 77.660196] ------------[ cut here ]------------
[ 77.664749] WARNING: CPU: 0 PID: 1992 at drivers/clk/clk.c:622
clk_core_disable+0x78/0x80
[ 77.672892] Modules linked in:
[ 77.675930] CPU: 0 PID: 1992 Comm: sh Not tainted 4.14.0 #23
[ 77.681570] Hardware name: xlnx,zynqmp (DT)
[ 77.685736] task: ffffffc879e2e580 task.stack: ffffff800be30000
[ 77.691641] PC is at clk_core_disable+0x78/0x80
Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Signed-off-by: Michal Simek <michal.simek@xilinx.com>
---
drivers/tty/serial/uartlite.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/uartlite.c b/drivers/tty/serial/uartlite.c
index 58296eb..4a7989d 100644
--- a/drivers/tty/serial/uartlite.c
+++ b/drivers/tty/serial/uartlite.c
@@ -857,7 +857,7 @@ static int ulite_remove(struct platform_device *pdev)
struct uartlite_data *pdata = port->private_data;
int rc;
- clk_disable_unprepare(pdata->clk);
+ clk_unprepare(pdata->clk);
rc = ulite_release(&pdev->dev);
pm_runtime_disable(&pdev->dev);
pm_runtime_set_suspended(&pdev->dev);
--
2.1.1
next prev parent reply other threads:[~2018-10-16 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 10:17 [LINUX PATCHv3 0/9] serial-uartlite: Add support for dynamic allocation shubhrajyoti.datta
2018-10-16 10:18 ` [LINUX PATCHv3 1/9] serial-uartlite: Move the uart register shubhrajyoti.datta
2018-10-16 10:18 ` [LINUX PATCHv3 2/9] serial-uartlite: Add get serial id if not provided shubhrajyoti.datta
2018-10-16 10:18 ` [LINUX PATCHv3 3/9] serial-uartlite: Do not use static struct uart_driver out of probe() shubhrajyoti.datta
2018-10-16 10:18 ` [LINUX PATCHv3 4/9] serial-uartlite: Add runtime support shubhrajyoti.datta
2018-10-16 10:18 ` shubhrajyoti.datta [this message]
2018-10-16 10:18 ` [LINUX PATCHv3 6/9] serial-uartlite: Change logic how console_port is setup shubhrajyoti.datta
2018-10-16 14:09 ` kbuild test robot
2018-10-16 10:18 ` [LINUX PATCHv3 7/9] serial-uartlite: Use allocated structure instead of static ones shubhrajyoti.datta
2018-10-16 10:18 ` [LINUX PATCHv3 8/9] serial-uartlite: Remove ULITE_NR_PORTS macro shubhrajyoti.datta
2018-10-16 10:18 ` [LINUX PATCHv3 9/9] serial-uartlite: Remove SERIAL_UARTLITE_NR_UARTS shubhrajyoti.datta
2018-11-09 16:45 ` [LINUX PATCHv3 0/9] serial-uartlite: Add support for dynamic allocation Greg KH
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=1539685088-13465-6-git-send-email-shubhrajyoti.datta@gmail.com \
--to=shubhrajyoti.datta@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacmet@sunsite.dk \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=shubhrajyoti.datta@xilinx.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).