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>,
Andy Gross <andy.gross@linaro.org>,
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 v3 0/2] i2c: added driver for Mellanox BlueField SoC
Date: Wed, 30 Jan 2019 13:01:30 -0500 [thread overview]
Message-ID: <cover.1548866223.git.kblaiech@mellanox.com> (raw)
Added I2C SMBus driver and device tree bindings documentation.
Changes since v2:
1) Device bindings documentation:
- Omit shared resources from the controller instance.
- Update the 'compatible' property and support the second
generation of the Mellanox BlueField SoC.
- Fix file format; replace spaces with tabs.
2) Device driver source:
- Provide common register definition.
- Update the "compatible" string and add a new entry to
the mlx_i2c_dt_ids array.
- Add a new entry to the mlx_i2c_acpi_ids array tosupport
a new device _HID.
- Update the device probe routines to derive the device
type based on the instance property described in either
devicetree or ACPI.
- Define new handlers to request and release the shared
resources. These handlers relies on the device type.
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 | 71 +
drivers/i2c/busses/Kconfig | 13 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-mlx.c | 2512 ++++++++++++++++++++
4 files changed, 2597 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/mellanox,i2c-mlxbf.txt
create mode 100644 drivers/i2c/busses/i2c-mlx.c
--
2.1.2
next reply other threads:[~2019-01-30 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 18:01 Khalil Blaiech [this message]
2019-01-30 18:01 ` [PATCH v3 2/2] dt-bindings: i2c: I2C binding for Mellanox BlueField SoC Khalil Blaiech
2019-02-13 22:23 ` 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.1548866223.git.kblaiech@mellanox.com \
--to=kblaiech@mellanox.com \
--cc=andy.gross@linaro.org \
--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).