From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: wsa@the-dreams.de
Cc: andy.shevchenko@gmail.com, jassisinghbrar@gmail.com,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH v6 0/3] add support for Socionext SynQuacer I2C controller
Date: Sun, 25 Mar 2018 12:07:44 +0100 [thread overview]
Message-ID: <20180325110747.8852-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.
v6:
- use i2c_8bit_addr_from_msg() instead of open coding the address generation
- switch to generic recovery using minimal helpers to drive the SDA/SCL lines
directly
- use reinit_completion() and move init_completion() to probe function
- replace bus free detection at the end of a transfer with a simple udelay()
for 2 clock periods
- don't recover on every error
- don't call synquacer_i2c_hw_init() from synquacer_i2c_hw_reset(), since it
will be always called twice in that case
- add patch to sanity check i2c_transfer() arguments in core code (#3)
v5:
- add Rob's ack to #1
- drop unnecessary 'platform_set_drvdata(pdev, NULL)' in remove path (#2)
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 (3):
dt-bindings: i2c: add binding for Socionext SynQuacer I2C
i2c: add support for Socionext SynQuacer I2C controller
i2c: add param sanity check to i2c_transfer()
Documentation/devicetree/bindings/i2c/i2c-synquacer.txt | 29 +
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-synquacer.c | 739 ++++++++++++++++++++
drivers/i2c/i2c-core-base.c | 3 +
5 files changed, 782 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt
create mode 100644 drivers/i2c/busses/i2c-synquacer.c
--
2.15.1
next reply other threads:[~2018-03-25 11:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-25 11:07 Ard Biesheuvel [this message]
2018-03-25 11:07 ` [PATCH v6 1/3] dt-bindings: i2c: add binding for Socionext SynQuacer I2C Ard Biesheuvel
2018-04-04 18:33 ` Wolfram Sang
2018-04-04 18:34 ` Wolfram Sang
2018-03-25 11:07 ` [PATCH v6 2/3] i2c: add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-04-04 18:34 ` Wolfram Sang
2018-04-04 18:35 ` Wolfram Sang
2018-03-25 11:07 ` [PATCH v6 3/3] i2c: add param sanity check to i2c_transfer() Ard Biesheuvel
2018-04-03 15:03 ` Wolfram Sang
2018-04-03 16:56 ` Ard Biesheuvel
2018-03-30 14:13 ` [PATCH v6 0/3] add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-04-03 15:01 ` Wolfram Sang
2018-04-03 18:05 ` Ard Biesheuvel
2018-04-03 18:12 ` Wolfram Sang
2018-04-03 18:14 ` Ard Biesheuvel
2018-04-03 18:32 ` Wolfram Sang
2018-04-03 18:35 ` Ard Biesheuvel
[not found] ` <20180403184559.z5lixuheqd4ojoti@ninjato>
2018-04-03 18:56 ` Ard Biesheuvel
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=20180325110747.8852-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.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).