From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Xu Yilun <yilun.xu@intel.com>, Wu Hao <hao.wu@intel.com>,
Tom Rix <trix@redhat.com>, Moritz Fischer <mdf@kernel.org>,
linux-fpga@vger.kernel.org, Lee Jones <lee@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Russ Weight <russell.h.weight@intel.com>
Cc: linux-hwmon@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH v3 0/4] intel-m10-bmc: Manage register access to control delay during sec update
Date: Mon, 17 Apr 2023 12:26:49 +0300 [thread overview]
Message-ID: <20230417092653.16487-1-ilpo.jarvinen@linux.intel.com> (raw)
Manage handshake register access on Max 10 FPGA cards that have a major
slowdown on reading handshake registers during secure update prepare and
write phases. The problem does not occur with PMCI-based cards.
The first patch which moves Max M10 symbols into own namespace is
otherwise independent of the other changes but it would conflict with
this series if sent as separate change. Thus, it's part of this series
to give the patches a well-defined order.
v3:
- Add tags properly & include series version history
v2:
- Add also m10bmc_dev_init() to SYMBOL NS
- Keep bmcfw_state only when handshake_sys_reg_nranges > 0
- Drop zero initializations for handshake_sys_reg*
Ilpo Järvinen (4):
mfd: intel-m10-bmc: Move core symbols to own namespace
mfd: intel-m10-bmc: Create m10bmc_sys_update_bits()
mfd: intel-m10-bmc: Move m10bmc_sys_read() away from header
mfd: intel-m10-bmc: Manage access to MAX 10 fw handshake registers
drivers/fpga/intel-m10-bmc-sec-update.c | 47 +++++++------
drivers/hwmon/intel-m10-bmc-hwmon.c | 1 +
drivers/mfd/intel-m10-bmc-core.c | 90 ++++++++++++++++++++++++-
drivers/mfd/intel-m10-bmc-pmci.c | 1 +
drivers/mfd/intel-m10-bmc-spi.c | 15 +++++
include/linux/mfd/intel-m10-bmc.h | 43 ++++++++----
6 files changed, 163 insertions(+), 34 deletions(-)
--
2.30.2
next reply other threads:[~2023-04-17 9:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 9:26 Ilpo Järvinen [this message]
2023-04-17 9:26 ` [PATCH v3 1/4] mfd: intel-m10-bmc: Move core symbols to own namespace Ilpo Järvinen
2023-04-20 16:08 ` Xu Yilun
2023-04-27 15:05 ` Lee Jones
2023-04-17 9:26 ` [PATCH v3 2/4] mfd: intel-m10-bmc: Create m10bmc_sys_update_bits() Ilpo Järvinen
2023-04-20 16:09 ` Xu Yilun
2023-04-21 9:52 ` Xu Yilun
2023-04-27 15:05 ` Lee Jones
2023-04-17 9:26 ` [PATCH v3 3/4] mfd: intel-m10-bmc: Move m10bmc_sys_read() away from header Ilpo Järvinen
2023-04-20 16:10 ` Xu Yilun
2023-04-27 15:06 ` Lee Jones
2023-04-17 9:26 ` [PATCH v3 4/4] mfd: intel-m10-bmc: Manage access to MAX 10 fw handshake registers Ilpo Järvinen
2023-04-20 16:07 ` Xu Yilun
2023-04-20 11:13 ` Lee Jones
2023-04-21 9:52 ` Xu Yilun
2023-04-27 15:07 ` Lee Jones
2023-05-10 11:51 ` Ilpo Järvinen
2023-05-15 10:06 ` Lee Jones
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=20230417092653.16487-1-ilpo.jarvinen@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hao.wu@intel.com \
--cc=jdelvare@suse.com \
--cc=lee@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).