All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khalil Blaiech <kblaiech@nvidia.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Rob Herring <robh@kernel.org>,
	linux-i2c@vger.kernel.org
Cc: Khalil Blaiech <kblaiech@mellanox.com>,
	Vadim Pasternak <vadimp@mellanox.com>
Subject: [PATCH v11 0/2] i2c: add driver for Mellanox BlueField SoC
Date: Tue, 22 Sep 2020 18:49:36 -0400	[thread overview]
Message-ID: <cover.1600804577.git.kblaiech@mellanox.com> (raw)

From: Khalil Blaiech <kblaiech@mellanox.com>


Add I2C SMBus driver and device tree bindings documentation.

The Mellanox BlueField is a System-on-Chip (SoC) that combines
Arm cores and ConnectX network adapter technology intended to
accelerate storage network solutions. The Mellanox BlueField
incorporates various I2C devices that are accessed using SMBus
protocol, a variant of the I2C protocol. On storage controllers,
the BlueField SoC is connected to a management controller board,
e.g., BMC via an I2C bus.

An I2C driver running on the Arm side is needed to manage the
hardware I2C controllers. The driver enables a master function
to transfer data back and forth from/to I2C devices, such as
EEPROM parts and implements a slave function to handle the BMC
controller requests.
---
v10->v11:
	- Fixing checkpatch (--strict) warnings.
	- Fixing sparse warnings.
v9->v10:
	- Fixing compile issue when building with gcc 9.3.0
	and Werror enabled; remove unused variable in
	mlxbf_slave_enable().
v8->v9:
	- Fixing implicit declaration of devm_ioremap_nocache
	and ioremap_nocache build error.
v7->v8:
	- Updating the dependency expression in Kconfig.
	- Fixing an implicit fallthrough build error.
v6->v7:
	- Fixing kernel coding style issues as suggested by
	Mellanox internal code reviewers.
	- Updating the dependency expression in Kconfig.
	- Fixing various device driver bugs.
	- Adding an entry to MAINTAINERS file.
v5->v6:
	- Fixing kernel coding style issues detected using
	'--strict' flag.
	- Updating the device binding documentation to add
	support for BlueField-2 SoCs.
v4->v5:
	- Fixing device driver bug.
v3->v4:
	- Review of the device binding documentation to
	fix format issue and miscellaneous cleanup.
v2->v3:
	- Various device driver changes and bug fixes.
	- Updating the device property in the device binding
	documentation and file format review.
v1->v2:
	- Various device driver changes and bug fixes.
	- Cleanup of the device binding documentation.

Khalil Blaiech (2):
  i2c: i2c-mlxbf: I2C SMBus driver for Mellanox BlueField SoC
  dt-bindings: i2c: I2C binding for Mellanox BlueField SoC

 .../devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt |   42 +
 MAINTAINERS                                        |    6 +
 drivers/i2c/busses/Kconfig                         |   13 +
 drivers/i2c/busses/Makefile                        |    1 +
 drivers/i2c/busses/i2c-mlxbf.c                     | 2506 ++++++++++++++++++++
 5 files changed, 2568 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
 create mode 100644 drivers/i2c/busses/i2c-mlxbf.c

-- 
2.1.2


             reply	other threads:[~2020-09-22 22:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 22:49 Khalil Blaiech [this message]
2020-09-22 22:49 ` [PATCH v11 1/2] i2c: i2c-mlxbf: I2C SMBus driver for Mellanox BlueField SoC Khalil Blaiech
2020-09-27 13:54   ` Wolfram Sang
2020-09-29 22:45     ` Khalil Blaiech
2020-09-30  5:41       ` Wolfram Sang
2020-10-05 23:54         ` Khalil Blaiech
2020-10-22 14:45           ` Khalil Blaiech
2020-09-22 22:49 ` [PATCH v11 2/2] dt-bindings: i2c: I2C binding " Khalil Blaiech
2020-09-22 23:05   ` Rob Herring
2020-09-29 22:59     ` Khalil Blaiech
2020-09-27 13:57   ` Wolfram Sang
2020-09-29 22:58     ` Khalil Blaiech
2020-09-30  5:44       ` 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=cover.1600804577.git.kblaiech@mellanox.com \
    --to=kblaiech@nvidia.com \
    --cc=kblaiech@mellanox.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=vadimp@mellanox.com \
    --cc=wsa+renesas@sang-engineering.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.