Linux clock framework development
 help / color / mirror / Atom feed
From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
Cc: <andersson@kernel.org>, <mturquette@baylibre.com>,
	<sboyd@kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<quic_srichara@quicinc.com>
Subject: Re: [PATCH] clk: qcom: ipq5424: fix software and hardware flow control error of UART
Date: Thu, 23 Jan 2025 18:59:08 +0530	[thread overview]
Message-ID: <Z5JEJCJsYDz9b85b@hu-varada-blr.qualcomm.com> (raw)
In-Reply-To: <20250123111618.1048461-1-quic_mmanikan@quicinc.com>

On Thu, Jan 23, 2025 at 04:46:18PM +0530, Manikanta Mylavarapu wrote:
> The UART’s software and hardware flow control are currently not
> functioning correctly.
>
> For software flow control, the following error is encountered:
> qcom_geni_serial 1a80000.serial: Couldn't find suitable
> clock rate for 56000000, 3500000, 2500000, 1152000, 921600, 19200
>
> During hardware flow control testing, a “Retry 0: Got ZCAN error” is
> observed.
>
> To address these issues, update the UART frequency table to include all
> supported frequencies according to the frequency plan.

Would this need fixes tag?

-Varada

>
> Signed-off-by: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
> ---
>  drivers/clk/qcom/gcc-ipq5424.c | 16 +++++++++++-----
>  1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/clk/qcom/gcc-ipq5424.c b/drivers/clk/qcom/gcc-ipq5424.c
> index d5b218b76e29..37b1a3ff8f4e 100644
> --- a/drivers/clk/qcom/gcc-ipq5424.c
> +++ b/drivers/clk/qcom/gcc-ipq5424.c
> @@ -592,13 +592,19 @@ static struct clk_rcg2 gcc_qupv3_spi1_clk_src = {
>  };
>
>  static const struct freq_tbl ftbl_gcc_qupv3_uart0_clk_src[] = {
> -	F(960000, P_XO, 10, 2, 5),
> -	F(4800000, P_XO, 5, 0, 0),
> -	F(9600000, P_XO, 2, 4, 5),
> -	F(16000000, P_GPLL0_OUT_MAIN, 10, 1, 5),
> +	F(3686400,  P_GCC_GPLL0_OUT_MAIN_DIV_CLK_SRC, 1, 144, 15625),
> +	F(7372800,  P_GCC_GPLL0_OUT_MAIN_DIV_CLK_SRC, 1, 288, 15625),
> +	F(14745600, P_GCC_GPLL0_OUT_MAIN_DIV_CLK_SRC, 1, 576, 15625),
>  	F(24000000, P_XO, 1, 0, 0),
>  	F(25000000, P_GPLL0_OUT_MAIN, 16, 1, 2),
> -	F(50000000, P_GPLL0_OUT_MAIN, 16, 0, 0),
> +	F(32000000, P_GPLL0_OUT_MAIN, 1, 1, 25),
> +	F(40000000, P_GPLL0_OUT_MAIN, 1, 1, 20),
> +	F(46400000, P_GPLL0_OUT_MAIN, 1, 29, 500),
> +	F(48000000, P_GPLL0_OUT_MAIN, 1, 3, 50),
> +	F(51200000, P_GPLL0_OUT_MAIN, 1, 8, 125),
> +	F(56000000, P_GPLL0_OUT_MAIN, 1, 7, 100),
> +	F(58982400, P_GPLL0_OUT_MAIN, 1, 1152, 15625),
> +	F(60000000, P_GPLL0_OUT_MAIN, 1, 3, 40),
>  	F(64000000, P_GPLL0_OUT_MAIN, 12.5, 0, 0),
>  	{ }
>  };
>
> --
> 2.34.1
>

  reply	other threads:[~2025-01-23 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 11:16 [PATCH] clk: qcom: ipq5424: fix software and hardware flow control error of UART Manikanta Mylavarapu
2025-01-23 13:29 ` Varadarajan Narayanan [this message]
2025-01-24  5:55   ` Manikanta Mylavarapu

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=Z5JEJCJsYDz9b85b@hu-varada-blr.qualcomm.com \
    --to=quic_varada@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_mmanikan@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=sboyd@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