linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 0/4] add support for Socionext SynQuacer I2C controller
Date: Tue,  3 Apr 2018 21:11:47 +0200	[thread overview]
Message-ID: <20180403191151.14924-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.

v7;
- remove recovery and suspend/resume support for now
- add myself as maintainer for this driver
- use WARN_ON() in i2c_transfer() sanity check

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 (4):
  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()
  MAINTAINERS: add Ard as Socionext SynQuacer I2C driver maintainer

 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt |  29 +
 MAINTAINERS                                             |   6 +
 drivers/i2c/busses/Kconfig                              |  10 +
 drivers/i2c/busses/Makefile                             |   1 +
 drivers/i2c/busses/i2c-synquacer.c                      | 669 ++++++++++++++++++++
 drivers/i2c/i2c-core-base.c                             |   3 +
 6 files changed, 718 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt
 create mode 100644 drivers/i2c/busses/i2c-synquacer.c

-- 
2.15.1

             reply	other threads:[~2018-04-03 19:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 19:11 Ard Biesheuvel [this message]
2018-04-03 19:11 ` [PATCH v7 1/4] dt-bindings: i2c: add binding for Socionext SynQuacer I2C Ard Biesheuvel
2018-04-04 18:35   ` Wolfram Sang
2018-04-03 19:11 ` [PATCH v7 2/4] i2c: add support for Socionext SynQuacer I2C controller Ard Biesheuvel
2018-04-04 18:35   ` Wolfram Sang
2018-04-03 19:11 ` [PATCH v7 3/4] i2c: add param sanity check to i2c_transfer() Ard Biesheuvel
2018-04-04 18:38   ` Wolfram Sang
2018-04-04 21:01     ` Ard Biesheuvel
2018-04-03 19:11 ` [PATCH v7 4/4] MAINTAINERS: add Ard as Socionext SynQuacer I2C driver maintainer Ard Biesheuvel
2018-04-04 18:37   ` Wolfram Sang

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=20180403191151.14924-1-ard.biesheuvel@linaro.org \
    --to=ard.biesheuvel@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).