From: Yu Tu <yu.tu@amlogic.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
linux-amlogic <linux-amlogic@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Jiri Slaby <jirislaby@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH V2 1/2] tty: serial: meson: Add a 12MHz internal clock rate to calculate baud rate in order to meet the baud rate requirements of special BT modules
Date: Thu, 21 Apr 2022 17:46:08 +0800 [thread overview]
Message-ID: <b6067d55-4800-b533-2ec7-02166977c825@amlogic.com> (raw)
In-Reply-To: <ea86eee0-409c-2d19-3669-35a8eaded53e@baylibre.com>
Hi Neil,
On 2022/4/21 16:46, Neil Armstrong wrote:
> [ EXTERNAL EMAIL ]
>
> Hi Andy,
>
> On 18/04/2022 14:09, Andy Shevchenko wrote:
>> On Mon, Apr 18, 2022 at 8:50 AM Yu Tu <yu.tu@amlogic.com> wrote:
>>>
>>> A /2 divider over XTAL was introduced since G12A, and is preferred
>>> to be used over the still present /3 divider since it provides much
>>> closer frequencies vs the request baudrate.Especially the BT module
>>
>> 'e. E' (mind the space)
>>
>>> uses 3Mhz baud rate. 8Mhz calculations can lead to baud rate bias,
>>> causing some problems.
>>
>> ...
>>
>>> +struct meson_uart_data {
>>> + bool has_xtal_div2;
>>
>> I would prefer to see this as an unsigned int and with a less
>> particular name, e.g. xtal_div would suffice.
>>
>>> +};
>>
>> ...
>>
>>> + unsigned int xtal_div = 3;
>>
>>> + if (private_data && private_data->has_xtal_div2) {
>>> + xtal_div = 2;
>>
>> Better to define privata data always
>
> While I'm in favor of defining private data, here 3 and 2 are actually
> the values
> 2 and 3 used to divide.
>
> The code is easy to read and we quickly understand this value is the
> clock divider.
>
Therefore, this place should be modified according to your previous
suggestion.I will prepare the next version.
>>
>>
>>> + val |= AML_UART_BAUD_XTAL_DIV2;
>>> + }
>>> + val |= DIV_ROUND_CLOSEST(port->uartclk / xtal_div,
>>> baud) - 1;
>>
>>
>
> .
next prev parent reply other threads:[~2022-04-21 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 5:32 [PATCH V2 0/2] Add q 12MHz internal clock rate to calculate Yu Tu
2022-04-18 5:32 ` [PATCH V2 1/2] tty: serial: meson: Add a 12MHz internal clock rate to calculate baud rate in order to meet the baud rate requirements of special BT modules Yu Tu
2022-04-18 12:09 ` Andy Shevchenko
2022-04-19 7:29 ` Yu Tu
2022-04-19 7:38 ` Jiri Slaby
2022-04-19 8:21 ` Andy Shevchenko
2022-04-21 8:44 ` Neil Armstrong
2022-04-19 8:43 ` Yu Tu
2022-04-21 8:46 ` Neil Armstrong
2022-04-21 9:46 ` Yu Tu [this message]
2022-04-18 5:32 ` [PATCH V2 2/2] tty: serial: meson: Added S4 SOC compatibility Yu Tu
2022-04-21 8:49 ` Neil Armstrong
2022-04-21 9:47 ` Yu Tu
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=b6067d55-4800-b533-2ec7-02166977c825@amlogic.com \
--to=yu.tu@amlogic.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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