From: "Ivan T. Ivanov" <iivanov@suse.de>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Stefan Wahren <stefan.wahren@i2se.com>,
Phil Elwell <phil@raspberrypi.org>,
kernel test robot <lkp@intel.com>,
linux-clk@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3] clk: bcm2835: Round UART input clock up
Date: Wed, 24 Aug 2022 10:44:43 +0300 [thread overview]
Message-ID: <20220824074443.nvrnqhpvqrtn72p4@suse> (raw)
In-Reply-To: <20220823230842.AB8BAC433C1@smtp.kernel.org>
On 08-23 16:08, Stephen Boyd wrote:
> Date: Tue, 23 Aug 2022 16:08:40 -0700
> From: Stephen Boyd <sboyd@kernel.org>
> To: Albert Ou <aou@eecs.berkeley.edu>, Broadcom internal kernel review list
> <bcm-kernel-feedback-list@broadcom.com>, Florian Fainelli
> <f.fainelli@gmail.com>, "Ivan T. Ivanov" <iivanov@suse.de>, Michael
> Turquette <mturquette@baylibre.com>, Nicolas Saenz Julienne
> <nsaenz@kernel.org>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley
> <paul.walmsley@sifive.com>, Ray Jui <rjui@broadcom.com>, Scott Branden
> <sbranden@broadcom.com>, Stefan Wahren <stefan.wahren@i2se.com>
> Cc: "Ivan T. Ivanov" <iivanov@suse.de>, Phil Elwell <phil@raspberrypi.org>,
> kernel test robot <lkp@intel.com>, linux-clk@vger.kernel.org,
> linux-rpi-kernel@lists.infradead.org,
> linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
> linux-riscv@lists.infradead.org
> Subject: Re: [PATCH v3] clk: bcm2835: Round UART input clock up
> Message-Id: <20220823230842.AB8BAC433C1@smtp.kernel.org>
>
> Quoting Ivan T. Ivanov (2022-05-27 03:29:00)
> > It was reported that RPi3[1] and RPi Zero 2W boards have issues with
> > the Bluetooth. It turns out that when switching from initial to
> > operation speed host and device no longer can talk each other because
> > host uses incorrect UART baud rate.
> >
> > The UART driver used in this case is amba-pl011. Original fix, see
> > below Github link[2], was inside pl011 module, but somehow it didn't
> > look as the right place to fix. Beside that this original rounding
> > function is not exactly perfect for all possible clock values. So I
> > deiced to move the hack to the platform which actually need it.
> >
> > The UART clock is initialised to be as close to the requested
> > frequency as possible without exceeding it. Now that there is a
> > clock manager that returns the actual frequencies, an expected
> > 48MHz clock is reported as 47999625. If the requested baud rate
> > == requested clock/16, there is no headroom and the slight
> > reduction in actual clock rate results in failure.
> >
> > If increasing a clock by less than 0.1% changes it from ..999..
> > to ..000.., round it up.
> >
> > [1] https://bugzilla.suse.com/show_bug.cgi?id=1188238
> > [2] https://github.com/raspberrypi/linux/commit/ab3f1b39537f6d3825b8873006fbe2fc5ff057b7
> >
> > Cc: Phil Elwell <phil@raspberrypi.org>
> > Signed-off-by: Ivan T. Ivanov <iivanov@suse.de>
> > ---
>
> This is waiting for someone like Stefan to review. It's customary to
> include previous reviewers on new versions of patches.
Thanks for fixing me mistake.
Regards,
Ivan
next prev parent reply other threads:[~2022-08-24 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:29 Ivan T. Ivanov
[not found] ` <20220823230842.AB8BAC433C1@smtp.kernel.org>
2022-08-24 7:44 ` Ivan T. Ivanov [this message]
2022-08-24 7:52 ` Phil Elwell
2022-08-24 10:04 ` Stefan Wahren
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=20220824074443.nvrnqhpvqrtn72p4@suse \
--to=iivanov@suse.de \
--cc=aou@eecs.berkeley.edu \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=mturquette@baylibre.com \
--cc=nsaenz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.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
all inboxes | Powered by JetHome®