linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: Conor Dooley <mail@conchuod.ie>
Cc: Ivan Bornyakov <i.bornyakov@metrotek.ru>,
	mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com,
	trix@redhat.com, linux-kernel@vger.kernel.org,
	linux-fpga@vger.kernel.org, system@metrotek.ru
Subject: Re: [PATCH v2] fpga: microsemi-spi: add Microsemi FPGA manager
Date: Tue, 15 Feb 2022 09:52:30 -0800	[thread overview]
Message-ID: <YgvoXgqM65M97qib@epycbox.lan> (raw)
In-Reply-To: <d0890e09-5d4a-5cce-832d-26e64b74ac54@conchuod.ie>

Hi Conor, Ivan,

On Tue, Feb 15, 2022 at 05:37:04PM +0000, Conor Dooley wrote:
> Hey Ivan,
> Firstly thanks for the patch(es), stumbled across them today.
> As you may know Microsemi has been acquired by Microchip, so
> s/microsemi/microchip/ please. This would make the correct vendor
> prefix for compatible strings "microchip". While you've said this is
> for the PolarFire FPGA, there is prescendent for using "mpfs" for the
> PolarFire SoC FPGA in the kernel - so if you could change the uses of
> "polarfire" to "mpf" that'd be great.

I personally don't have a strong opinion on hte microchip vs microsemi
here. We have precedent with intel/altera.

> 
> The current item on my own todo list is the opposite side of this,
> reprogramming the FPGA via the system controller acting as a SPI
> master for PolarFire SoC.
> I will get back to you when I have a better idea of what (if any) code
> can be made generic between both modes. In the meantime, I will get
> together a setup to test SPI slave reprogramming of the PolarFire (SoC)
> 
> Thanks,
> Conor <conor.dooley@microchip.com>

Thanks for chiming in. Always nice to have vendors help out reviewing.
> 
> > Add support to the FPGA manager for programming Microsemi Polarfire
> > FPGAs over slave SPI interface.
> >
> > Signed-off-by: Ivan Bornyakov <i.bornyakov@metrotek.ru>
> > ---
> > Changelog:
> >   v1 -> v2: fix printk formating
> >
> >  drivers/fpga/Kconfig         |   9 +
> >  drivers/fpga/Makefile        |   1 +
> >  drivers/fpga/microsemi-spi.c | 366 +++++++++++++++++++++++++++++++++++
> >  3 files changed, 376 insertions(+)
> >  create mode 100644 drivers/fpga/microsemi-spi.c
> >
> --<snip>--

I'll take a closer look once the bot's complaints are addressed.

Thanks,
Moritz

  reply	other threads:[~2022-02-15 17:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 13:38 [PATCH] fpga: microsemi-spi: add Microsemi FPGA manager Ivan Bornyakov
2022-02-14 19:22 ` kernel test robot
2022-02-14 20:34 ` kernel test robot
2022-02-15 11:58 ` [PATCH v2] " Ivan Bornyakov
2022-02-15 17:37   ` Conor Dooley
2022-02-15 17:52     ` Moritz Fischer [this message]
2022-02-15 18:05       ` Ivan Bornyakov
2022-02-16 12:55   ` Conor.Dooley
2022-02-16 15:56 ` [PATCH v3] fpga: microchip-spi: add Microchip " Ivan Bornyakov
2022-02-17 19:18 ` [PATCH v4] " Ivan Bornyakov
2022-02-18 15:22   ` Conor.Dooley
2022-02-19  5:45     ` Ivan Bornyakov
2022-02-18 16:05   ` Xu Yilun
2022-02-19  6:16     ` Ivan Bornyakov
2022-02-19 10:42       ` Ivan Bornyakov

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=YgvoXgqM65M97qib@epycbox.lan \
    --to=mdf@kernel.org \
    --cc=hao.wu@intel.com \
    --cc=i.bornyakov@metrotek.ru \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@conchuod.ie \
    --cc=system@metrotek.ru \
    --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).