From: Jan Kotas <jank@cadence.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>
Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Jan Kotas <jank@cadence.com>
Subject: [PATCH v2 0/2] clk: Add driver and bindings for Fixed MMIO clock
Date: Thu, 13 Dec 2018 12:49:27 +0000 [thread overview]
Message-ID: <20181213124929.32736-1-jank@cadence.com> (raw)
This patchset adds a driver support for Fixed Memory Mapped IO clock.
The driver reads a clock frequency value from a single 32-bit memory
mapped register and registers it as a fixed rate clock.
It can be useful for prototyping Linux on various hardware platforms.
It is not intended to be used on finished, complete SoCs.
Changes since V1:
Added platform driver support.
Removed unnecessary messages.
Jan Kotas (2):
dt-bindings: clk: Add bindings for Fixed MMIO clock
clk: Add Fixed MMIO clock driver
.../devicetree/bindings/clock/fixed-mmio-clock.txt | 24 +++++
drivers/clk/Kconfig | 6 ++
drivers/clk/Makefile | 1 +
drivers/clk/clk-fixed-mmio.c | 109 +++++++++++++++++++++
4 files changed, 140 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/fixed-mmio-clock.txt
create mode 100644 drivers/clk/clk-fixed-mmio.c
--
2.15.0
next reply other threads:[~2018-12-13 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 12:49 Jan Kotas [this message]
2018-12-13 12:49 ` [PATCH v2 1/2] dt-bindings: clk: Add bindings for Fixed MMIO clock Jan Kotas
2019-01-09 19:42 ` Stephen Boyd
2018-12-13 12:49 ` [PATCH v2 2/2] clk: Add Fixed MMIO clock driver Jan Kotas
2019-01-09 19:42 ` Stephen Boyd
2019-01-09 19:42 ` 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=20181213124929.32736-1-jank@cadence.com \
--to=jank@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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).