From: Joshua Henderson <joshua.henderson@microchip.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
Joshua Henderson <joshua.henderson@microchip.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
Purna Chandra Mandal <purna.mandal@microchip.com>,
Rob Herring <robh@kernel.org>,
Sandeep Sheriker <sandeepsheriker.mallikarjun@microchip.com>
Subject: [PATCH v8 0/3] PIC32MZDA Clock Driver
Date: Wed, 24 Feb 2016 09:07:14 -0700 [thread overview]
Message-ID: <1456330090-27226-1-git-send-email-joshua.henderson@microchip.com> (raw)
Clock bindings got acked and then essentially unacked, while the clock
driver never made it upstream. In the meantime, the initial DTS file
made it upstream. This latest patch series includes a patch to go back
and correct the DTS files to reflect the new clock bindings in this
patch series.
This series still uses the CLK_OF_DECLARE approach despite not being
regarded as the best approach. On MIPS/PIC32 the first call of clk_get()
happens from "start_kernel -> time_init() -> plat_time_init()" which is
very early in boot sequence even before execution of early_initcall().
In short, by platform_driver way I was not able to register clock(s)
before the first clock user becomes ready. With CLK_OF_DECLARE() I can
explicitly call of_clk_init() in plat_time_init() just before calling
clk_get().
Purna Chandra Mandal (3):
dt/bindings: Add PIC32 clock binding documentation
clk: clk-pic32: Add PIC32 clock driver
MIPS: dts: pic32: Update dts to reflect new PIC32MZDA clk binding
.../devicetree/bindings/clock/microchip,pic32.txt | 39 +
arch/mips/boot/dts/pic32/pic32mzda-clk.dtsi | 236 -----
arch/mips/boot/dts/pic32/pic32mzda.dtsi | 63 +-
arch/mips/boot/dts/pic32/pic32mzda_sk.dts | 5 +-
drivers/clk/Kconfig | 3 +
drivers/clk/Makefile | 1 +
drivers/clk/microchip/Makefile | 2 +
drivers/clk/microchip/clk-core.c | 954 ++++++++++++++++++++
drivers/clk/microchip/clk-core.h | 78 ++
drivers/clk/microchip/clk-pic32mzda.c | 214 +++++
include/dt-bindings/clock/microchip,pic32-clock.h | 42 +
11 files changed, 1378 insertions(+), 259 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/microchip,pic32.txt
delete mode 100644 arch/mips/boot/dts/pic32/pic32mzda-clk.dtsi
create mode 100644 drivers/clk/microchip/Makefile
create mode 100644 drivers/clk/microchip/clk-core.c
create mode 100644 drivers/clk/microchip/clk-core.h
create mode 100644 drivers/clk/microchip/clk-pic32mzda.c
create mode 100644 include/dt-bindings/clock/microchip,pic32-clock.h
next reply other threads:[~2016-02-24 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:07 Joshua Henderson [this message]
2016-02-24 16:07 ` [PATCH v8 1/3] dt/bindings: Add PIC32 clock binding documentation Joshua Henderson
2016-02-24 20:57 ` Michael Turquette
2016-02-24 16:07 ` [PATCH v8 3/3] MIPS: dts: pic32: Update dts to reflect new PIC32MZDA clk binding Joshua Henderson
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=1456330090-27226-1-git-send-email-joshua.henderson@microchip.com \
--to=joshua.henderson@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=purna.mandal@microchip.com \
--cc=ralf@linux-mips.org \
--cc=robh@kernel.org \
--cc=sandeepsheriker.mallikarjun@microchip.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;
as well as URLs for NNTP newsgroup(s).