linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: krzk@kernel.org, mdf@kernel.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: trix@redhat.com, yilun.xu@intel.com, lgoncalv@redhat.com
Subject: [PATCH v3] add the FPGA Device Feature List (DFL) EMIF support
Date: Mon, 21 Sep 2020 13:31:19 +0800	[thread overview]
Message-ID: <1600666280-25651-1-git-send-email-yilun.xu@intel.com> (raw)

The driver supports the EMIF controller on Intel Programmable
Acceleration Card (PAC). The controller manages the on-board memory of
the PCIe card.


Hi Moritz:

I have sent 2 versions of the patch to Krzysztof who maintains the
drivers/memory folder. And because this patch depends on the previous
fpga patchset "Modularization of DFL private feature drivers" &
"add dfl bus support to MODULE_DEVICE_TABLE()", it cannot be applied
independently to Krzysztof's branch until next cycle. So he suggests,
"please send a v3 of this patch with the fix above and let's apply it
via Moritz's tree."

So could you help do that? After it got the acked-by from Krzysztof.

Thanks,
Yilun


Xu Yilun (1):
  memory: dfl-emif: add the DFL EMIF private feature driver

 .../ABI/testing/sysfs-bus-dfl-devices-emif         |  25 +++
 drivers/memory/Kconfig                             |   9 +
 drivers/memory/Makefile                            |   2 +
 drivers/memory/dfl-emif.c                          | 207 +++++++++++++++++++++
 4 files changed, 243 insertions(+)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-dfl-devices-emif
 create mode 100644 drivers/memory/dfl-emif.c

-- 
2.7.4


             reply	other threads:[~2020-09-21  5:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  5:31 Xu Yilun [this message]
2020-09-21  5:31 ` [PATCH v3] memory: dfl-emif: add the DFL EMIF private feature driver Xu Yilun
2020-09-21  7:23   ` Krzysztof Kozlowski
2020-09-21 20:31     ` Moritz Fischer
2020-09-21 20:46       ` Krzysztof Kozlowski
2020-09-22  3:17         ` Moritz Fischer

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=1600666280-25651-1-git-send-email-yilun.xu@intel.com \
    --to=yilun.xu@intel.com \
    --cc=krzk@kernel.org \
    --cc=lgoncalv@redhat.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=trix@redhat.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).