linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Xu Yilun <yilun.xu@intel.com>
Cc: gregkh@linuxfoundation.org, linux-fpga@vger.kernel.org,
	hao.wu@intel.com, mdf@kernel.org
Subject: Re: [PATCH 1/1] fpga: m10bmc-sec: Add support for N6000
Date: Tue, 31 Jan 2023 09:08:35 +0000	[thread overview]
Message-ID: <Y9jak/PLJLfDY1Pl@google.com> (raw)
In-Reply-To: <20230131024121.940195-2-yilun.xu@intel.com>

On Tue, 31 Jan 2023, Xu Yilun wrote:

> From: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> 
> Add support for PMCI-based flash access path and N6000 sec update
> support. Access to flash staging area is different for N6000 from that
> of the SPI interfaced counterparts.
> 
> Introduce intel_m10bmc_flash_bulk_ops to allow interface specific
> differentiations for the flash access path for sec update and make
> m10bmc_sec_read/write() in sec update driver to use the new operations.
> The .flash_mutex serializes read/read. Flash update (erase+write) must
> use ->lock/unlock_write() to prevent reads during update (reads would
> timeout on setting flash MUX as BMC will prevent it).
> 
> Create a type specific RSU status reg handler for N6000 because the
> field has moved from doorbell to auth result register.
> 
> If a failure is detected while altering the flash MUX, it seems safer
> to try to set it back and doesn't seem harmful. Likely there are enough
> troubles in that case anyway so setting it back fails too (which is
> harmless sans the small extra delay) or just confirms that the value
> wasn't changed.
> 
> Co-developed-by: Tianfei zhang <tianfei.zhang@intel.com>
> Signed-off-by: Tianfei zhang <tianfei.zhang@intel.com>
> Co-developed-by: Russ Weight <russell.h.weight@intel.com>
> Signed-off-by: Russ Weight <russell.h.weight@intel.com>
> Acked-by: Xu Yilun <yilun.xu@intel.com>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Signed-off-by: Lee Jones <lee@kernel.org>
> Link: https://lore.kernel.org/r/20230116100845.6153-12-ilpo.jarvinen@linux.intel.com
> ---
>  drivers/fpga/intel-m10-bmc-sec-update.c |  51 ++++-
>  drivers/mfd/intel-m10-bmc-pmci.c        | 242 +++++++++++++++++++++++-
>  include/linux/mfd/intel-m10-bmc.h       |  51 +++++
>  3 files changed, 336 insertions(+), 8 deletions(-)

I'm confused, what are you trying to achieve?

Who are you sending this to?

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2023-01-31  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  2:41 [PATCH 0/1] A missing FPGA patch for v6.3-rc1 Xu Yilun
2023-01-31  2:41 ` [PATCH 1/1] fpga: m10bmc-sec: Add support for N6000 Xu Yilun
2023-01-31  9:08   ` Lee Jones [this message]
2023-01-31  9:57     ` Xu Yilun
2023-01-31 10:58       ` Lee Jones
2023-01-31 11:40         ` Greg KH
2023-01-31 12:16           ` Lee Jones
2023-01-31 15:34             ` Xu Yilun
2023-01-31 17:13               ` Lee Jones
2023-02-01  1:58                 ` Xu Yilun

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=Y9jak/PLJLfDY1Pl@google.com \
    --to=lee@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=mdf@kernel.org \
    --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).