From: Tero Kristo <t-kristo@ti.com>
To: <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <sboyd@kernel.org>,
<mturquette@baylibre.com>
Subject: [PATCH 0/3] clk: keystone: sci-clk: perf improvements
Date: Fri, 12 Apr 2019 21:22:19 +0300 [thread overview]
Message-ID: <1555093342-428-1-git-send-email-t-kristo@ti.com> (raw)
Hi,
After some thinking, I decided to switch the clock scan method for
the sci-clk completely over to DT based scan. For example, on am65xx,
the boot time improvement for the clock probe is from 398ms down to
7.3ms. I retained the full firmware scan code behind a separate
Kconfig option; this can be useful for some debugging purposes if
someone needs to see all the clocks in a device.
Also, added patch #1 for cropping down the registered clock names,
currently they are pretty long forms containing the full interconnect
node paths, which makes the debugfs sort of un-usable.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-04-12 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 18:22 Tero Kristo [this message]
2019-04-12 18:22 ` [PATCH 1/3] clk: keystone: sci-clk: cut down the clock name length Tero Kristo
2019-04-12 18:22 ` [PATCH 2/3] clk: keystone: sci-clk: split out the fw clock parsing to own function Tero Kristo
2019-04-12 18:22 ` [PATCH 3/3] clk: keystone: sci-clk: probe clocks from DT instead of firmware Tero Kristo
2019-04-17 11:14 ` [PATCH 0/3] clk: keystone: sci-clk: perf improvements Tero Kristo
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=1555093342-428-1-git-send-email-t-kristo@ti.com \
--to=t-kristo@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@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;
as well as URLs for NNTP newsgroup(s).