From: Jerome Brunet <jbrunet@baylibre.com>
To: Alexandre Mergnat <amergnat@baylibre.com>
Cc: narmstrong@baylibre.com, sboyd@kernel.org, khilman@baylibre.com,
Alexandre Mergnat <amergnat@baylibre.com>,
linux-kernel@vger.kernel.org, baylibre-upstreaming@groups.io,
linux-amlogic@lists.infradead.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/4] clk: meson: ao: use the new parent description method
Date: Mon, 29 Jul 2019 12:53:38 +0200 [thread overview]
Message-ID: <1j36ip9knh.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20190725164126.27919-1-amergnat@baylibre.com>
On Thu 25 Jul 2019 at 18:41, Alexandre Mergnat <amergnat@baylibre.com> wrote:
> Meson SoCs clock controllers use the string comparison method to describe
> parent relation between the clocks, which is not optimized.
>
> Its also use bypass clock made from device-tree clock to provide an input
> clock which can be access through global name, but it still not optimal.
>
> A recent patch [0] allows parents to be directly specified with
> device-tree clock name or without string names from localy declared clocks.
>
> This patchset replaces clock string names by clock pointers (as possible),
> removes bypass clocks and uses directly device-tree clock names in parent
> assignment.
>
> Tested on GXL, GXBB, Meson8b, AXG SoCs by comparing the clock summary
> (orphan too) before and after migration.
>
> [0] commit fc0c209c147f ("clk: Allow parents to be specified without string names")
>
> Change since v1:
> - Improve clock parent assignment for "fixme" using name instead of fw_name.
>
> Alexandre Mergnat (4):
> clk: meson: g12a-aoclk: migrate to the new parent description method
> clk: meson: gxbb-aoclk: migrate to the new parent description method
> clk: meson: axg-aoclk: migrate to the new parent description method
> clk: meson: remove ao input bypass clocks
>
> drivers/clk/meson/Kconfig | 1 -
> drivers/clk/meson/axg-aoclk.c | 63 ++++++++++++++-----------
> drivers/clk/meson/g12a-aoclk.c | 81 ++++++++++++++++++++-------------
> drivers/clk/meson/gxbb-aoclk.c | 55 +++++++++++-----------
> drivers/clk/meson/meson-aoclk.c | 37 ---------------
> drivers/clk/meson/meson-aoclk.h | 8 ----
> 6 files changed, 114 insertions(+), 131 deletions(-)
>
Applied
Thanks !
> --
> 2.17.1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-07-29 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 16:41 Alexandre Mergnat
2019-07-25 16:41 ` [PATCH v2 1/4] clk: meson: g12a-aoclk: migrate to " Alexandre Mergnat
2019-07-25 16:41 ` [PATCH v2 2/4] clk: meson: gxbb-aoclk: " Alexandre Mergnat
2019-07-25 16:41 ` [PATCH v2 3/4] clk: meson: axg-aoclk: " Alexandre Mergnat
2019-07-25 16:41 ` [PATCH v2 4/4] clk: meson: remove ao input bypass clocks Alexandre Mergnat
2019-07-29 10:53 ` Jerome Brunet [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=1j36ip9knh.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=amergnat@baylibre.com \
--cc=baylibre-upstreaming@groups.io \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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
all inboxes | Powered by JetHome®