From: Paul Walmsley <paul.walmsley@sifive.com>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
mturquette@baylibre.com
Subject: Re: [PATCH v3 0/3] clk: add driver for the SiFive FU540 PRCI and PLLs it controls
Date: Fri, 26 Apr 2019 10:01:23 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1904261000090.28496@viisi.sifive.com> (raw)
In-Reply-To: <155624271876.15276.8637203698438742304@swboyd.mtv.corp.google.com>
Hi Stephen,
On Thu, 25 Apr 2019, Stephen Boyd wrote:
> Quoting Paul Walmsley (2019-04-11 01:26:16)
> > clk: add driver for the SiFive FU540 PRCI and PLLs it controls
> >
> > Add a driver for the SiFive FU540 PRCI IP block, which handles clock and
> > some device reset control for the SiFive FU540 chip. Also add a driver-
> > independent library for the Analog Bits Wide-Range PLL (WRPLL), used by
> > the PRCI driver to monitor and control the WRPLL instances on the FU540
> > chip.
> >
> > Boot-tested on a SiFive HiFive Unleashed board, using BBL and the
> > open-source FSBL with a mainline-focused DTB.
> >
> > This third version incorporates changes requested by Stephen Boyd
> > <sboyd@kernel.org> and Rob Herring <robh@kernel.org>.
> >
> > This patch series is also available, along with the DT macro prerequisite
> > patch, at:
>
> Can you please send the dt macro patch along with the rest of the
> patches? I can't apply these patches and build them without it.
It's upstream now as commit 6ec4bae178d8 ("dt-bindings: clock: sifive: add
FU540-C000 PRCI clock constants")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6ec4bae178d8a1e9814eb3bfdd321b0475de0468
- Paul
next prev parent reply other threads:[~2019-04-26 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 8:26 Paul Walmsley
2019-04-26 1:38 ` Stephen Boyd
2019-04-26 17:01 ` Paul Walmsley [this message]
2019-04-26 17:17 ` 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=alpine.DEB.2.21.9999.1904261000090.28496@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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
all inboxes | Powered by JetHome®