From: Asmaa Mnebhi <asmaa@nvidia.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
robh@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: Asmaa Mnebhi <asmaa@nvidia.com>
Subject: [PATCH v4 0/8] i2c: i2c-mlxbf.c: bug fixes and new feature support
Date: Mon, 19 Sep 2022 17:34:23 -0400 [thread overview]
Message-ID: <20220919213431.8045-1-asmaa@nvidia.com> (raw)
This is a series of patches fixing several bugs and implementing
new features.
Bug fixes:
1) Fix the frequency calculation
2) Fix incorrect base address passed during io write
3) prevent stack overflow in mlxbf_i2c_smbus_start_transaction()
4) Support lock mechanism to avoid race condition between entities
using the i2c bus
Cleanup:
5) remove IRQF_ONESHOT flag as it is no longer needed.
Features:
6) Support multi slave functionality
7) Support BlueField-3 SoC
8) Update binding devicetree
What has changed from v3->v4:
- moved the patch related to updating the SPDX licence out of this series.
This will be submitted as a separate patch later and will need approval
from all contributors.
- fixed build error in the frequency calculation patch. The name
of the frequency functions changed but that was not reflected
when they were called.
- Fixed the prefix in $subject as "i2c: <driver>:"
- Use kernel multiline comment style in the "support lock mechanism" patch
- instead of calling mlxbf_i2c_smbus_master_unlock multiple times, use the
"goto out_unlock" style.
- Added the devicetree reviewers
Asmaa Mnebhi (8):
i2c: i2c-mlxbf.c: Fix frequency calculation
i2c: i2c-mlxbf.c: remove IRQF_ONESHOT
i2c: i2c-mlxbf.c: incorrect base address passed during io write
i2c: i2c-mlxbf: prevent stack overflow in
mlxbf_i2c_smbus_start_transaction()
i2c: i2c-mlxbf.c: support lock mechanism
i2c: i2c-mlxbf: add multi slave functionality
i2c: i2c-mlxbf.c: support BlueField-3 SoC
i2c: i2c-mlxbf.c: Update binding devicetree
.../bindings/i2c/mellanox,i2c-mlxbf.yaml | 49 +-
MAINTAINERS | 1 +
drivers/i2c/busses/i2c-mlxbf.c | 862 ++++++++++--------
3 files changed, 522 insertions(+), 390 deletions(-)
--
2.30.1
next reply other threads:[~2022-09-19 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 21:34 Asmaa Mnebhi [this message]
2022-09-19 21:34 ` [PATCH v4 1/8] i2c: i2c-mlxbf.c: Fix frequency calculation Asmaa Mnebhi
2022-09-19 21:34 ` [PATCH v4 2/8] i2c: i2c-mlxbf.c: remove IRQF_ONESHOT Asmaa Mnebhi
2022-09-19 21:34 ` [PATCH v4 3/8] i2c: i2c-mlxbf.c: incorrect base address passed during io write Asmaa Mnebhi
2022-09-19 21:34 ` [PATCH v4 4/8] i2c: i2c-mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() Asmaa Mnebhi
2022-09-19 21:34 ` [PATCH v4 5/8] i2c: i2c-mlxbf.c: support lock mechanism Asmaa Mnebhi
2022-09-19 21:34 ` [PATCH v4 6/8] i2c: i2c-mlxbf: add multi slave functionality Asmaa Mnebhi
2022-09-19 21:34 ` [PATCH v4 7/8] i2c: i2c-mlxbf.c: support BlueField-3 SoC Asmaa Mnebhi
2022-09-19 21:34 ` [PATCH v4 8/8] i2c: i2c-mlxbf.c: Update binding devicetree Asmaa Mnebhi
2022-09-20 8:18 ` Krzysztof Kozlowski
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=20220919213431.8045-1-asmaa@nvidia.com \
--to=asmaa@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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.