linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mturquette@baylibre.com (Michael Turquette)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 0/3] arm64: amlogic: support gxbb clock controller
Date: Wed, 22 Jun 2016 19:12:20 -0700	[thread overview]
Message-ID: <1466647943-23193-1-git-send-email-mturquette@baylibre.com> (raw)

This series breaks out some clean-up patches and the changes to dts from
v1 of the meson8b[0] and gxbb[1] clk driver series. This was done to
make it easy for the AmLogic maintainers to take only these patches if
they want. Additionally there is a shared, immutable branch with the
gxbb clk driver if the amlogic maintainers wish to merge that into their
tree:

git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-s905

The only functional change was to nest the clock-controller node inside
of the hiubus node, as suggested by Kevin.

[0] Link: lkml.kernel.org/g/1465518467-23939-1-git-send-email-mturquette at baylibre.com
[1] Link: lkml.kernel.org/g/1465518774-26924-1-git-send-email-mturquette at baylibre.com

Michael Turquette (3):
  arm: meson: explicitly select clk drivers
  arm64: amlogic: select gxbb clk driver
  arm64: dts: gxbb clock controller

 arch/arm/mach-meson/Kconfig                 | 3 +++
 arch/arm64/Kconfig.platforms                | 2 ++
 arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 6 ++++++
 3 files changed, 11 insertions(+)

-- 
2.1.4

             reply	other threads:[~2016-06-23  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  2:12 Michael Turquette [this message]
2016-06-23  2:12 ` [PATCH v2 1/3] arm: meson: explicitly select clk drivers Michael Turquette
2016-06-23  2:12 ` [PATCH v2 2/3] arm64: amlogic: select gxbb clk driver Michael Turquette
2016-06-23  2:12 ` [PATCH v2 3/3] arm64: dts: gxbb clock controller Michael Turquette
2016-06-23 23:05 ` [PATCH v2 0/3] arm64: amlogic: support " Kevin Hilman
2016-06-24  4:40   ` Michael Turquette

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=1466647943-23193-1-git-send-email-mturquette@baylibre.com \
    --to=mturquette@baylibre.com \
    --cc=linus-amlogic@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).