From: Maxime Ripard <mripard@kernel.org>
To: Samuel Holland <samuel@sholland.org>
Cc: Chen-Yu Tsai <wens@csie.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH 0/3] A64/H3/H6 R_CCU clock fixes
Date: Thu, 2 Jan 2020 10:28:58 +0100 [thread overview]
Message-ID: <20200102092858.6n5uqymglia4t7lk@gilmour.lan> (raw)
In-Reply-To: <20191229025922.46899-1-samuel@sholland.org>
[-- Attachment #1: Type: text/plain, Size: 557 bytes --]
On Sat, Dec 28, 2019 at 08:59:19PM -0600, Samuel Holland wrote:
> Hi all,
>
> I was examining the H6 BSP clock driver[1] for guidance when porting an
> AR100 firmware[2] to the H6 SoC. I found some inconsistencies between
> that code and the sunxi-ng driver.
>
> I don't have a good way to verify the first patch. Someone with an
> oscilloscope could set the divider and check the I2C/RSB frequency.
>
> Patch 2 should have no functional change.
>
> Patch 3 was verified by benchmarking. Details are in the commit message.
Applied all three, thanks
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2020-01-02 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 2:59 [PATCH 0/3] A64/H3/H6 R_CCU clock fixes Samuel Holland
2019-12-29 2:59 ` [PATCH 1/3] clk: sunxi-ng: sun8i-r: Fix divider on APB0 clock Samuel Holland
2019-12-29 2:59 ` [PATCH 2/3] clk: sunxi-ng: h6-r: Simplify R_APB1 clock definition Samuel Holland
2019-12-29 2:59 ` [PATCH 3/3] clk: sunxi-ng: h6-r: Fix AR100/R_APB2 parent order Samuel Holland
2020-01-02 9:28 ` Maxime Ripard [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=20200102092858.6n5uqymglia4t7lk@gilmour.lan \
--to=mripard@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mturquette@baylibre.com \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=wens@csie.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).