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
Cc: Asmaa Mnebhi <asmaa@nvidia.com>
Subject: [PATCH v3 0/9] i2c-mlxbf.c: bug fixes and new feature support
Date: Thu, 8 Sep 2022 13:35:35 -0400 [thread overview]
Message-ID: <20220908173544.32615-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) Update SPDX license
7) Support multi slave functionality
8) Support BlueField-3 SoC
9) Update binding devicetree
What has changed from v1->v2:
- moved all the bug fixes to the top commits and left the features for last
- split the BlueField-3 SoC patch into 2: one for the driver code and another
patch for the device tree binding yaml documentation file
- keep the device tree/acpi tables backward compatible. So add the new resources at the
end of the enum.
- update the license in a separate patch
In v3, updated the cover letter to reflect changes made from v1->v2 and add Rev-by
Asmaa Mnebhi (9):
i2c-mlxbf.c: Fix frequency calculation
i2c-mlxbf.c: remove IRQF_ONESHOT
i2c-mlxbf.c: incorrect base address passed during io write
i2c-mlxbf: prevent stack overflow in
mlxbf_i2c_smbus_start_transaction()
i2c-mlxbf.c: support lock mechanism
i2c-mlxbf.c: Update SPDX license
i2c-mlxbf: add multi slave functionality
i2c-mlxbf.c: support BlueField-3 SoC
i2c-mlxbf.c: Update binding devicetree
.../bindings/i2c/mellanox,i2c-mlxbf.yaml | 49 +-
MAINTAINERS | 1 +
drivers/i2c/busses/i2c-mlxbf.c | 872 ++++++++++--------
3 files changed, 525 insertions(+), 397 deletions(-)
--
2.30.1
next reply other threads:[~2022-09-08 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 17:35 Asmaa Mnebhi [this message]
2022-09-08 17:35 ` [PATCH v3 1/9] i2c-mlxbf.c: Fix frequency calculation Asmaa Mnebhi
2022-09-17 18:07 ` Wolfram Sang
2022-09-08 17:35 ` [PATCH v3 2/9] i2c-mlxbf.c: remove IRQF_ONESHOT Asmaa Mnebhi
2022-09-17 18:21 ` Wolfram Sang
2022-09-08 17:35 ` [PATCH v3 3/9] i2c-mlxbf.c: incorrect base address passed during io write Asmaa Mnebhi
2022-09-17 18:12 ` Wolfram Sang
2022-09-08 17:35 ` [PATCH v3 4/9] i2c-mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() Asmaa Mnebhi
2022-09-17 18:14 ` Wolfram Sang
2022-09-08 17:35 ` [PATCH v3 5/9] i2c-mlxbf.c: support lock mechanism Asmaa Mnebhi
2022-09-17 18:25 ` Wolfram Sang
2022-09-19 12:50 ` Asmaa Mnebhi
2022-09-08 17:35 ` [PATCH v3 6/9] i2c-mlxbf.c: Update SPDX license Asmaa Mnebhi
2022-09-17 18:30 ` Wolfram Sang
2022-09-19 12:51 ` Asmaa Mnebhi
2022-09-08 17:35 ` [PATCH v3 7/9] i2c-mlxbf: add multi slave functionality Asmaa Mnebhi
2022-09-08 17:35 ` [PATCH v3 8/9] i2c-mlxbf.c: support BlueField-3 SoC Asmaa Mnebhi
2022-09-08 17:35 ` [PATCH v3 9/9] i2c-mlxbf.c: Update binding devicetree Asmaa Mnebhi
2022-09-17 18:34 ` 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=20220908173544.32615-1-asmaa@nvidia.com \
--to=asmaa@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox