From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: wsa@the-dreams.de, robh+dt@kernel.org, mark.rutland@arm.com,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jassisinghbrar@gmail.com,
andy.shevchenko@gmail.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH v4 0/2] add support for Socionext SynQuacer I2C controller
Date: Thu, 1 Mar 2018 16:38:13 +0000 [thread overview]
Message-ID: <20180301163815.30595-1-ard.biesheuvel@linaro.org> (raw)
Add a binding and a driver for the I2C IP found in the Socionext SynQuacer
SoC, which is essentially a rebranded version of the Fujitsu F_I2C controller.
v4:
- clarify binding that only a single interrupt specifier is expected (#1)
- check return value of clk_prepare_enable() on probe path (#2)
- add Andy's R-b to patch #2
v3:
- incorporate more of Andy's review comments (#2), especially regarding the
bus speed and clock source handling for ACPI
- patch #1 unchanged.
v2:
- incorporate Andy's review comments (#2)
- patch #1 unchanged.
Ard Biesheuvel (2):
dt-bindings: i2c: add binding for Socionext SynQuacer I2C
i2c: add support for Socionext SynQuacer I2C controller
Documentation/devicetree/bindings/i2c/i2c-synquacer.txt | 29 +
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-synquacer.c | 792 ++++++++++++++++++++
4 files changed, 832 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt
create mode 100644 drivers/i2c/busses/i2c-synquacer.c
--
2.11.0
next reply other threads:[~2018-03-01 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 16:38 Ard Biesheuvel [this message]
2018-03-01 16:38 ` [PATCH v4 1/2] dt-bindings: i2c: add binding for Socionext SynQuacer I2C Ard Biesheuvel
2018-03-01 16:44 ` Rob Herring
2018-03-01 16:38 ` [PATCH v4 2/2] i2c: add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-03-01 18:32 ` Andy Shevchenko
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=20180301163815.30595-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--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).