From: Parthiban Nallathambi <pn@denx.de>
To: manivannan.sadhasivam@linaro.org, afaerber@suse.de,
robh+dt@kernel.org, mark.rutland@arm.com, wsa@the-dreams.de
Cc: linux-arm-kernel@lists.infradead.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@cubietech.com, thomas.liau@actions-semi.com,
linux-actions@lists.infradead.org,
Parthiban Nallathambi <pn@denx.de>
Subject: [PATCH v3 0/4] Add Actions Semi Owl family S700 I2C support
Date: Tue, 11 Dec 2018 09:04:44 +0100 [thread overview]
Message-ID: <20181211080448.24007-1-pn@denx.de> (raw)
This patch series adds support for Actions Semi Owl SoC family S700
I2C controller. S700 provides 4 I2C masters and with cubieboard7
2 (I2C0 and I2C1) are exposed.
Added pinctrl definition for I2C controllers in cubieboard7. This patch
depends on s700 pinctrl driver support (yet to be merged),
https://lkml.org/lkml/2018/11/19/514
https://lore.kernel.org/patchwork/patch/1012859/
Changelog in v3:
- re-ordering I2C and pinctrl nodes alphabetically in board DTS
- re-orderng of patch
- Typo and nitpick corrections
Changelog in v2:
- Initial version https://lore.kernel.org/patchwork/patch/1011911/ only
added the I2C nodes using s900 compatible property. Now, new s700
compatiable string is added and used for S700
- Device tree bindings added with s700 compatible string
- pinctrl definition for cubieboard7
Parthiban Nallathambi (4):
dt-bindings: i2c: Add S700 support for Actions Semi Soc's
arm64: dts: actions: s700: Add I2C controller nodes
i2c: Add Actions Semiconductor Owl family S700 I2C support
arm64: dts: actions: s700-cubieboard7: Enable I2C0 and I2C1
.../devicetree/bindings/i2c/i2c-owl.txt | 4 +-
.../boot/dts/actions/s700-cubieboard7.dts | 53 +++++++++++++++++++
arch/arm64/boot/dts/actions/s700.dtsi | 40 ++++++++++++++
drivers/i2c/busses/i2c-owl.c | 1 +
4 files changed, 97 insertions(+), 1 deletion(-)
--
2.17.2
next reply other threads:[~2018-12-11 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 8:04 Parthiban Nallathambi [this message]
2018-12-11 8:04 ` [PATCH v3 1/4] dt-bindings: i2c: Add S700 support for Actions Semi Soc's Parthiban Nallathambi
2018-12-17 22:17 ` Rob Herring
2019-01-03 19:13 ` Wolfram Sang
2018-12-11 8:04 ` [PATCH v3 2/4] arm64: dts: actions: s700: Add I2C controller nodes Parthiban Nallathambi
2019-01-05 17:58 ` Manivannan Sadhasivam
2018-12-11 8:04 ` [PATCH v3 3/4] i2c: Add Actions Semiconductor Owl family S700 I2C support Parthiban Nallathambi
2018-12-11 20:54 ` Wolfram Sang
2019-01-03 19:13 ` Wolfram Sang
2018-12-11 8:04 ` [PATCH v3 4/4] arm64: dts: actions: s700-cubieboard7: Enable I2C0 and I2C1 Parthiban Nallathambi
2018-12-13 3:47 ` kbuild test robot
2019-01-05 17:59 ` Manivannan Sadhasivam
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=20181211080448.24007-1-pn@denx.de \
--to=pn@denx.de \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@cubietech.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=thomas.liau@actions-semi.com \
--cc=wsa@the-dreams.de \
/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).