From: Jon Mason <jonmason@broadcom.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
<linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: [PATCH 0/5] ARM: dts: add device tree support for NS, NSP, and NS2 clocks
Date: Tue, 13 Oct 2015 17:22:22 -0400 [thread overview]
Message-ID: <1444771347-11382-1-git-send-email-jonmason@broadcom.com> (raw)
This patch series adds device tree support for the Broadcom Northstar,
Northstar Plus, and Northstar 2 clocks. This is being sent as a
separate patch series due to the the clk maintainer(s) not wanting to
pull in device tree changes into the clk repo. This series is an RFC
due to a potential merge "race" between the device tree changes and the
clk changes. If the device tree changes go in before the clk changes,
there is a window where there are non-working clk entries in the device
tree. So, these patches will be officially pushed once the clk changes
are merged.
Thanks,
Jon
next reply other threads:[~2015-10-13 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 21:22 Jon Mason [this message]
2015-10-13 21:22 ` [RFC 1/5] clk: iproc: define Broadcom NSP iProc clock binding Jon Mason
2015-10-13 22:17 ` Ray Jui
2015-10-14 15:40 ` Jon Mason
2015-10-13 21:22 ` [RFC 2/5] ARM: dts: enable clock support for Broadcom NSP Jon Mason
2015-10-13 21:22 ` [RFC 3/5] ARM: dts: enable clock support for BCM5301X Jon Mason
2015-10-18 22:34 ` Hauke Mehrtens
2015-10-13 21:22 ` [RFC 4/5] clk: iproc: define Broadcom NS2 iProc clock binding Jon Mason
2015-10-13 22:24 ` Ray Jui
2015-10-14 15:44 ` Jon Mason
2015-10-14 16:53 ` Ray Jui
2015-10-16 22:11 ` Stephen Boyd
2015-10-13 21:22 ` [RFC 5/5] ARM: dts: enable clock support for Broadcom NS2 Jon Mason
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=1444771347-11382-1-git-send-email-jonmason@broadcom.com \
--to=jonmason@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=sboyd@codeaurora.org \
--cc=sbranden@broadcom.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
Powered by JetHome