From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: 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>,
linux-hwmon@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] intel-m10-bmc: Manage register access to control delay during sec update
Date: Mon, 17 Apr 2023 12:19:29 +0300 (EEST) [thread overview]
Message-ID: <53d2d5eb-26e-d017-41cc-60292a6f33a6@linux.intel.com> (raw)
In-Reply-To: <20230417091619.14134-1-ilpo.jarvinen@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
On Mon, 17 Apr 2023, Ilpo Järvinen wrote:
> 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.
>
> 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(-)
>
>
Please disregard v2. I'll send v3 shortly.
(I managed to add the tags into wrong files so they're not correctly
here in v2).
--
i.
prev parent reply other threads:[~2023-04-17 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 9:16 [PATCH v2 0/4] intel-m10-bmc: Manage register access to control delay during sec update Ilpo Järvinen
2023-04-17 9:16 ` [PATCH v2 1/4] mfd: intel-m10-bmc: Move core symbols to own namespace Ilpo Järvinen
2023-04-17 9:16 ` [PATCH v2 2/4] mfd: intel-m10-bmc: Create m10bmc_sys_update_bits() Ilpo Järvinen
2023-04-17 9:16 ` [PATCH v2 3/4] mfd: intel-m10-bmc: Move m10bmc_sys_read() away from header Ilpo Järvinen
2023-04-17 9:16 ` [PATCH v2 4/4] mfd: intel-m10-bmc: Manage access to MAX 10 fw handshake registers Ilpo Järvinen
2023-04-17 9:19 ` Ilpo Järvinen [this message]
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=53d2d5eb-26e-d017-41cc-60292a6f33a6@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 NNTP newsgroup(s).