linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Xu Yilun <yilun.xu@intel.com>,
	mdf@kernel.org, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: trix@redhat.com, lgoncalv@redhat.com
Subject: Re: [PATCH v2 0/4] Modularization of DFL private feature drivers
Date: Thu, 23 Jul 2020 20:03:52 -0700	[thread overview]
Message-ID: <7ff4653b-dcf0-e7d4-9d09-a30a9f857661@infradead.org> (raw)
In-Reply-To: <1595556555-9903-1-git-send-email-yilun.xu@intel.com>

On 7/23/20 7:09 PM, Xu Yilun wrote:
> This patchset makes it possible to develop independent driver modules
> for DFL private features. It also helps to leverage existing kernel
> drivers to enable some IP blocks in DFL.
> 
> Patch #1: An improvement of feature id definition. The feature id will be used
> 	  as the key field for dfl device/driver matching.
> Patch #2: Release the dfl mmio regions after enumeration, so that private
> 	  feature drivers could request mmio region in their own drivers.
> Patch #3: Introduce the dfl bus, then dfl devices could be supported by
> 	  independent dfl drivers.
> Patch #4: An example of the dfl driver for N3000 nios private feature.
> 

Hi,
What is "nios"?  Is that explained or described anywhere?

> 
> Main changes from v1:
> - Add the new Patch #1, to improve the feature id definition.
> - Change the dfl bus uevent format.
> - Change the dfl device's sysfs name format.
> - refactor dfl_dev_add()
> - Add the Patch #4 as an example of the dfl driver.
> - A lot of minor fixes for comments from Hao and Tom.

thanks.
-- 
~Randy


  parent reply	other threads:[~2020-07-24  3:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24  2:09 [PATCH v2 0/4] Modularization of DFL private feature drivers Xu Yilun
2020-07-24  2:09 ` [PATCH v2 1/4] fpga: dfl: change data type of feature id to u16 Xu Yilun
2020-07-25 13:29   ` Tom Rix
2020-07-31  7:48     ` Xu Yilun
2020-08-01 15:40       ` Tom Rix
2020-07-24  2:09 ` [PATCH v2 2/4] fpga: dfl: map feature mmio resources in their own feature drivers Xu Yilun
2020-08-01 15:43   ` Tom Rix
2020-07-24  2:09 ` [PATCH v2 3/4] fpga: dfl: create a dfl bus type to support DFL devices Xu Yilun
2020-08-01 15:47   ` Tom Rix
2020-07-24  2:09 ` [PATCH v2 4/4] fpga: dfl: add support for N3000 nios private feature Xu Yilun
2020-07-25 14:53   ` Tom Rix
2020-07-31  8:56     ` Xu Yilun
2020-08-01 15:35       ` Tom Rix
2020-07-24  3:03 ` Randy Dunlap [this message]
2020-07-24  3:30   ` [PATCH v2 0/4] Modularization of DFL private feature drivers 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=7ff4653b-dcf0-e7d4-9d09-a30a9f857661@infradead.org \
    --to=rdunlap@infradead.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 \
    --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).