From: Stephen Boyd <sboyd@codeaurora.org>
To: Pramod Gurav <gpramod@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, bryanh@codeaurora.org, jslaby@suse.cz
Subject: Re: [PATCH] tty: serial: msm: Fix mask value of RFR level
Date: Tue, 07 Apr 2015 16:07:35 -0700 [thread overview]
Message-ID: <55246337.2000804@codeaurora.org> (raw)
In-Reply-To: <1428414446-21282-1-git-send-email-gpramod@codeaurora.org>
On 04/07/15 06:47, Pramod Gurav wrote:
> According to documents The RFR_LEVEL1 in UART_DM_MR1 can be
That is UART_DM_MR1
> programmed in bits 31:8 but the masks only bits 17:8.
> Correct the same.
>
> Signed-off-by: Pramod Gurav <gpramod@codeaurora.org>
> ---
> drivers/tty/serial/msm_serial.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/msm_serial.h b/drivers/tty/serial/msm_serial.h
> index 8f7806d..5ff9ebf 100644
> --- a/drivers/tty/serial/msm_serial.h
> +++ b/drivers/tty/serial/msm_serial.h
> @@ -19,7 +19,7 @@
> #define UART_MR1 0x0000
>
> #define UART_MR1_AUTO_RFR_LEVEL0 0x3F
> -#define UART_MR1_AUTO_RFR_LEVEL1 0x3FF00
> +#define UART_MR1_AUTO_RFR_LEVEL1 0xFFFFFF00
But this is UART_MR1. The two hardware cores share the same driver
because the DM hardware is based on the non-DM hardware. I suppose we
need to make another #define UART_DM_MR1_AUTO_RFR_LEVEL1 and then have
an if (msm_port->is_uartdm) in msm_startup() path to handle the
differences here.
> #define UART_MR1_RX_RDY_CTL (1 << 7)
> #define UART_MR1_CTS_CTL (1 << 6)
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-04-07 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 13:47 [PATCH] tty: serial: msm: Fix mask value of RFR level Pramod Gurav
2015-04-07 23:07 ` Stephen Boyd [this message]
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=55246337.2000804@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=gpramod@codeaurora.org \
--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 \
/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).