public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bence Csókás" <bence98@sch.bme.hu>
To: <linux-i2c@vger.kernel.org>
Cc: "Bence Csókás" <bence98@sch.bme.hu>, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] Add i2c-cp2615
Date: Thu, 18 Mar 2021 11:52:08 +0000	[thread overview]
Message-ID: <20210318115210.2014204-1-bence98@sch.bme.hu> (raw)

For a hardware project, I need the I2C master of SiLabs' CP2615 chip
to be visible from under Linux. This patchset adds i2c-cp2615, a
driver which sets up an i2c_adapter for said chip.

Changes in v3:
* Fixed SPDX header
* Added I2C_AQ_NO_REP_START adapter quirk to i2c.h
* Added I2C_AQ_NO_ZERO_LEN | I2C_AQ_NO_REP_START to CP2615's quirk flags
* Made the driver only bind to the IOP interface
* Return -ENXIO instead of -ECOMM when the device does not ACK
* Formatting, fix almost all warnings and checks from `checkpatch --strict`
  * CamelCase checks remain. These identifiers were taken from SiLabs'
    Application Note, I thought it made sense to preserve these as-is.

Bence Csókás (2):
  i2c: Add I2C_AQ_NO_REP_START adapter quirk
  Adding i2c-cp2615: i2c support for Silicon Labs' CP2615 Digital Audio
    Bridge

 drivers/i2c/busses/Kconfig      |  10 ++
 drivers/i2c/busses/Makefile     |   1 +
 drivers/i2c/busses/i2c-cp2615.c | 279 ++++++++++++++++++++++++++++++++
 include/linux/i2c.h             |   2 +
 4 files changed, 292 insertions(+)
 create mode 100644 drivers/i2c/busses/i2c-cp2615.c

-- 
2.31.0


             reply	other threads:[~2021-03-18 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 11:52 Bence Csókás [this message]
2021-03-18 11:52 ` [PATCH v3 1/2] i2c: Add I2C_AQ_NO_REP_START adapter quirk Bence Csókás
2021-03-18 11:52 ` [PATCH v3 2/2] Adding i2c-cp2615: i2c support for Silicon Labs' CP2615 Digital Audio Bridge Bence Csókás
2021-03-20  2:30   ` kernel test robot
2021-03-31  7:09   ` Wolfram Sang
2021-03-31  9:58   ` Wolfram Sang
2021-03-31 18:17     ` Bence Csókás
2021-03-31 20:55       ` 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=20210318115210.2014204-1-bence98@sch.bme.hu \
    --to=bence98@sch.bme.hu \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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