From: Jerome Brunet <jbrunet@baylibre.com>
To: Kevin Hilman <khilman@baylibre.com>,
Carlo Caione <carlo@caione.org>,
Stephen Boyd <sboyd@codeaurora.org>,
devicetree@vger.kernel.org
Cc: Jerome Brunet <jbrunet@baylibre.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Neil Armstrong <narmstrong@baylibre.com>,
linux-clk@vger.kernel.org
Subject: [PATCH 0/4] ARM: amlogic: add i2c support to Amlogic's gxbb family
Date: Wed, 14 Sep 2016 12:06:04 +0200 [thread overview]
Message-ID: <1473847568-20163-1-git-send-email-jbrunet@baylibre.com> (raw)
Add support for the meson i2c controller found on the gxbb SoC family
This patchset adds 1 i2c in the AO domain and 3 in the EE domain (A,B,C).
There is 1 last i2c in the EE domain (D) but it is actually not connected
to the pad of the SoC, so there is no point in adding it here.
Patches for the i2c [0] driver and pinctrl [1] have been sent in
dedicated series
[0]: http://lkml.kernel.org/r/1473846557-18123-1-git-send-email-jbrunet@baylibre.com
[1]: http://lkml.kernel.org/r/1473846328-17339-1-git-send-email-jbrunet@baylibre.com
Jerome Brunet (3):
clk: gxbb: expose i2c clocks
ARM64: dts: meson-gxbb: add pins for I2C
ARM64: dts: gxbb: add i2c bus
Neil Armstrong (1):
ARM64: dts: meson-gxbb: add I2C nodes
.../arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 6 ++
arch/arm64/boot/dts/amlogic/meson-gxbb-p200.dts | 6 ++
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 72 ++++++++++++++++++++++
drivers/clk/meson/gxbb.h | 4 +-
include/dt-bindings/clock/gxbb-clkc.h | 2 +
5 files changed, 88 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-14 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 10:06 Jerome Brunet [this message]
2016-09-14 10:06 ` [PATCH 1/4] clk: gxbb: expose i2c clocks Jerome Brunet
2016-09-14 18:25 ` 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=1473847568-20163-1-git-send-email-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=sboyd@codeaurora.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).