From: geert+renesas@glider.be (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] clk: Use of_clk_get_parent_count() instead of open coding
Date: Fri, 29 May 2015 11:25:44 +0200 [thread overview]
Message-ID: <1432891549-23295-1-git-send-email-geert+renesas@glider.be> (raw)
Hi all,
In several places, the functionality of of_clk_get_parent_count() is open
coded. Replace them by of_clk_get_parent_count() to reduce code size.
The first 3 patches can be applied independently, as the affected clock
drivers are used with CONFIG_COMMON_CLK=y and CONFIG_OF=y only.
Patch 4 adds dummy implementations of of_clk_get_parent_count() for the
cases where CONFIG_OF or CONFIG_COMMON_CLK are not set.
This is an RFC, as
1. Dummies are needed in two places,
2. We don't have any dummies yet for the !CCF case.
Patch 5 depends on patch 4, since the arm,sp804 timer is also used on
platforms where CONFIG_OF or CONFIG_COMMON_CLK are not set.
This was compile-tested using:
- multi_v7_defconfig (CCF, OF)
- realview_defconfig (CCF, no OF)
- versatile_defconfig (no CCF, no OF)
- bcm2835_defconfig (CCF, OF)
- axm55xx_defconfig (CCF, OF)
- at91_dt_defconfig (CCF, OF)
- omap2plus_defconfig (CCF, OF)
Thanks!
Geert Uytterhoeven (5):
clk: at91: Use of_clk_get_parent_count() instead of open coding
clk: st: Use of_clk_get_parent_count() instead of open coding
clk: ti: Use of_clk_get_parent_count() instead of open coding
[RFC] clk: Provide dummy of_clk_get_parent_count() for !OF/!CCF
[RFC] ARM: timer-sp: Use of_clk_get_parent_count() instead of open
coding
arch/arm/common/timer-sp.c | 3 ++-
drivers/clk/at91/clk-main.c | 2 +-
drivers/clk/at91/clk-master.c | 2 +-
drivers/clk/at91/clk-programmable.c | 2 +-
drivers/clk/at91/clk-slow.c | 4 ++--
drivers/clk/at91/clk-smd.c | 2 +-
drivers/clk/at91/clk-usb.c | 2 +-
drivers/clk/st/clk-flexgen.c | 2 +-
drivers/clk/st/clkgen-mux.c | 2 +-
drivers/clk/ti/clockdomain.c | 2 +-
include/linux/clk-provider.h | 11 ++++++++++-
11 files changed, 22 insertions(+), 12 deletions(-)
--
1.9.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2015-05-29 9:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 9:25 Geert Uytterhoeven [this message]
2015-05-29 9:25 ` [PATCH 1/5] clk: at91: Use of_clk_get_parent_count() instead of open coding Geert Uytterhoeven
2015-05-30 7:43 ` Boris Brezillon
2015-06-04 20:52 ` Stephen Boyd
2015-05-29 9:25 ` [PATCH 2/5] clk: st: " Geert Uytterhoeven
2015-06-04 20:53 ` Stephen Boyd
2015-05-29 9:25 ` [PATCH 3/5] clk: ti: " Geert Uytterhoeven
2015-06-04 20:53 ` Stephen Boyd
2015-05-29 9:25 ` [PATCH 4/5] [RFC] clk: Provide dummy of_clk_get_parent_count() for !OF/!CCF Geert Uytterhoeven
2015-05-29 9:25 ` [PATCH 5/5] [RFC] ARM: timer-sp: Use of_clk_get_parent_count() instead of open coding Geert Uytterhoeven
2015-06-03 23:44 ` Stephen Boyd
2015-06-04 7:26 ` Geert Uytterhoeven
2015-06-04 18:14 ` Stephen Boyd
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=1432891549-23295-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.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).