From: Stephen Boyd <sboyd@codeaurora.org>
To: Pramod Gurav <pramod.gurav@smartplayin.com>
Cc: David Brown <davidb@codeaurora.org>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
linux-arm-msm@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tty: serial: msm_serial: Remove duplicate code in msm_console_setup
Date: Thu, 08 Jan 2015 13:46:08 -0800 [thread overview]
Message-ID: <54AEFAA0.3010605@codeaurora.org> (raw)
In-Reply-To: <1420708545-6477-1-git-send-email-pramod.gurav@smartplayin.com>
On 01/08/2015 01:15 AM, Pramod Gurav wrote:
> drivers/tty/serial/msm_serial.c | 15 ---------------
> 1 file changed, 15 deletions(-)
>
> diff --git a/drivers/tty/serial/msm_serial.c b/drivers/tty/serial/msm_serial.c
> index c88b522..057008d 100644
> --- a/drivers/tty/serial/msm_serial.c
> +++ b/drivers/tty/serial/msm_serial.c
> @@ -932,27 +932,12 @@ static int __init msm_console_setup(struct console *co, char *options)
> if (unlikely(!port->membase))
> return -ENXIO;
>
> - msm_init_clock(port);
> -
Hm.. doesn't the console setup happen before the port is opened though?
I would think that we need to keep this around so that the clock is
actually enabled before we go and write to hardware registers.
> if (options)
> uart_parse_options(options, &baud, &parity, &bits, &flow);
>
> bits = 8;
> parity = 'n';
> flow = 'n';
I wonder if we should leave this here? Maybe we can rely on the user
specifying the right values on the command line?
> - msm_write(port, UART_MR2_BITS_PER_CHAR_8 | UART_MR2_STOP_BIT_LEN_ONE,
> - UART_MR2); /* 8N1 */
> -
> - if (baud < 300 || baud > 115200)
> - baud = 115200;
> - msm_set_baud_rate(port, baud);
> -
> - msm_reset(port);
> -
> - if (msm_port->is_uartdm) {
msm_port is unused now. Please remove it in the same patch.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-01-08 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 9:15 [PATCH v2] tty: serial: msm_serial: Remove duplicate code in msm_console_setup Pramod Gurav
2015-01-08 21:46 ` Stephen Boyd [this message]
2015-01-09 6:16 ` Pramod Gurav
2015-01-12 12:46 ` Pramod Gurav
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=54AEFAA0.3010605@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=dwalker@fifo99.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=pramod.gurav@smartplayin.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).