From: Luiz Capitulino <luizcap@redhat.com>
To: ilpo.jarvinen@linux.intel.com, shravankr@nvidia.com
Cc: davthompson@nvidia.com, ndalvi@redhat.com,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Luiz Capitulino <luizcap@redhat.com>
Subject: [PATCH 0/2] platform/mellanox: mlxbf-pmc: Fix module loading
Date: Thu, 22 Feb 2024 15:57:28 -0500 [thread overview]
Message-ID: <cover.1708635408.git.luizcap@redhat.com> (raw)
Hi,
The mlxbf-pmc driver fails to load when the firmware reports a new but not
yet implemented performance block. I can reproduce this today with a
Bluefield-3 card and UEFI version 4.6.0-18-g7d063bb-BId13035, since this
reports the new clock_measure performance block.
This[1] patch from Shravan implements the clock_measure support and will
solve the issue. But this series avoids the situation by ignoring and
logging unsupported performance blocks.
NOTE: This series is based on latest linux-next which contains new changes
to mlxbf-pmc.
[1] https://lore.kernel.org/lkml/1c2f1b6da51523fe0f338f9ddce9e3903148f604.1707808180.git.shravankr@nvidia.com/
Luiz Capitulino (2):
platform/mellanox: mlxbf-pmc: mlxbf_pmc_event_list(): make size ptr
optional
platform/mellanox: mlxbf-pmc: Ignore unsupported performance blocks
drivers/platform/mellanox/mlxbf-pmc.c | 56 +++++++++++++++++----------
1 file changed, 36 insertions(+), 20 deletions(-)
--
2.43.1
next reply other threads:[~2024-02-22 20:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 20:57 Luiz Capitulino [this message]
2024-02-22 20:57 ` [PATCH 1/2] platform/mellanox: mlxbf-pmc: mlxbf_pmc_event_list(): make size ptr optional Luiz Capitulino
2024-02-26 10:49 ` Hans de Goede
2024-02-22 20:57 ` [PATCH 2/2] platform/mellanox: mlxbf-pmc: Ignore unsupported performance blocks Luiz Capitulino
2024-02-26 10:49 ` Hans de Goede
2024-02-26 13:27 ` [PATCH 0/2] platform/mellanox: mlxbf-pmc: Fix module loading Ilpo Järvinen
2024-02-26 15:49 ` Luiz Capitulino
2024-02-26 16:04 ` Ilpo Järvinen
2024-02-26 16:10 ` Luiz Capitulino
2024-02-26 16:57 ` Hans de Goede
2024-02-26 17:05 ` Luiz Capitulino
2024-02-27 13:18 ` Ilpo Järvinen
2024-02-27 18:28 ` Luiz Capitulino
2024-02-26 16:59 ` Ilpo Järvinen
2024-02-26 17:07 ` Luiz Capitulino
2024-02-27 13:20 ` Ilpo Järvinen
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.1708635408.git.luizcap@redhat.com \
--to=luizcap@redhat.com \
--cc=davthompson@nvidia.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ndalvi@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=shravankr@nvidia.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