From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: linux-i2c@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Baruch Siach <baruch@tkos.co.il>,
Wolfram Sang <wsa@the-dreams.de>,
Andrew Bresticker <abrestic@chromium.org>,
Sachin Kamat <sachin.kamat@samsung.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
David Box <david.e.box@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Xudong Chen <xudong.chen@mediatek.com>,
Kamal Dasu <kdasu.kdev@gmail.com>,
Subhendu Sekhar Behera <sbehera@broadcom.com>,
Wei Yan <sledge.yanwei@huawei.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Neelesh Gupta <neelegup@linux.vnet.ibm.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Laurentiu Palcu <laurentiu.palcu@intel.com>,
devicetree@vger.kernel.org,
Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Ray Jui <rjui@broadcom.com>,
Beniamino Galvani <b.galvani@gmail.com>,
Rob
Subject: [PATCH 0/3] i2c: uniphier: add two I2C controller drivers for UniPhier SoC platform
Date: Thu, 30 Jul 2015 17:12:19 +0900 [thread overview]
Message-ID: <1438243942-26401-1-git-send-email-yamada.masahiro@socionext.com> (raw)
This series adds two I2C controller drivers.
(they are completely different IPs.)
The first one is a very simple FIFO-less I2C controller,
which is used on some older UniPhier SoCs.
The other one is higher-performance I2C controller with TX/RX FIFO,
used on newer UniPhier SoCs.
Masahiro Yamada (3):
i2c: uniphier: add UniPhier FIFO-less I2C driver
i2c: uniphier_f: add UniPhier FIFO-builtin I2C driver
i2c: uniphier: add bindings for UniPhier I2C controllers
.../devicetree/bindings/i2c/i2c-uniphier.txt | 46 ++
drivers/i2c/busses/Kconfig | 16 +
drivers/i2c/busses/Makefile | 2 +
drivers/i2c/busses/i2c-uniphier-f.c | 589 +++++++++++++++++++++
drivers/i2c/busses/i2c-uniphier.c | 446 ++++++++++++++++
5 files changed, 1099 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-uniphier.txt
create mode 100644 drivers/i2c/busses/i2c-uniphier-f.c
create mode 100644 drivers/i2c/busses/i2c-uniphier.c
--
1.9.1
next reply other threads:[~2015-07-30 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 8:12 Masahiro Yamada [this message]
[not found] ` <1438243942-26401-1-git-send-email-yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>
2015-07-30 8:12 ` [PATCH 3/3] i2c: uniphier: add bindings for UniPhier I2C controllers Masahiro Yamada
2015-10-22 21:00 ` Wolfram Sang
2015-10-23 10:54 ` Masahiro Yamada
2015-09-25 2:12 ` [PATCH 0/3] i2c: uniphier: add two I2C controller drivers for UniPhier SoC platform Masahiro Yamada
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=1438243942-26401-1-git-send-email-yamada.masahiro@socionext.com \
--to=yamada.masahiro@socionext.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=abrestic@chromium.org \
--cc=b.galvani@gmail.com \
--cc=baruch@tkos.co.il \
--cc=david.e.box@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kdasu.kdev@gmail.com \
--cc=laurentiu.palcu@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=neelegup@linux.vnet.ibm.com \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=sachin.kamat@samsung.com \
--cc=sbehera@broadcom.com \
--cc=sledge.yanwei@huawei.com \
--cc=wsa@the-dreams.de \
--cc=xudong.chen@mediatek.com \
--cc=zhangfei.gao@linaro.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