devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Khalil Blaiech <kblaiech@mellanox.com>
To: Rob Herring <robh@kernel.org>, Wolfram Sang <wsa@the-dreams.de>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	David Woods <dwoods@mellanox.com>
Cc: Khalil Blaiech <kblaiech@mellanox.com>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
	arm-soc <arm@kernel.org>
Subject: [PATCH v4 0/2] i2c: added driver for Mellanox BlueField SoC
Date: Tue, 19 Feb 2019 18:45:44 -0500	[thread overview]
Message-ID: <cover.1550618900.git.kblaiech@mellanox.com> (raw)

Added I2C SMBus driver and device tree bindings documentation.

Changes since v3:

Device bindings documentation:

   - Re-order property descriptions.
   - Remove useless register addresses from the resource
     description.
   - Mention default clock-frequency value.
   - Fix format issues; remove spaces.
   - Omit "aliases" from Example section.
   - Rename device instance node in Example section.

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

 .../devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt |   29 +
 drivers/i2c/busses/Kconfig                         |   13 +
 drivers/i2c/busses/Makefile                        |    1 +
 drivers/i2c/busses/i2c-mlx.c                       | 2512 ++++++++++++++++++++
 4 files changed, 2555 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
 create mode 100644 drivers/i2c/busses/i2c-mlx.c

--
2.1.2

             reply	other threads:[~2019-02-19 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 23:45 Khalil Blaiech [this message]
2019-02-19 23:45 ` [PATCH v4 2/2] dt-bindings: i2c: I2C binding for Mellanox BlueField SoC Khalil Blaiech
2019-02-22 16:56   ` Rob Herring

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.1550618900.git.kblaiech@mellanox.com \
    --to=kblaiech@mellanox.com \
    --cc=arm@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dwoods@mellanox.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --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).