linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Ley Foon Tan <ley.foon.tan@intel.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org, lftan.linux@gmail.com
Subject: Re: [PATCH] PCI: altera: Allow building as module
Date: Tue, 4 Jun 2019 08:18:48 -0500	[thread overview]
Message-ID: <20190604131848.GA40122@google.com> (raw)
In-Reply-To: <1556081835-12921-1-git-send-email-ley.foon.tan@intel.com>

On Wed, Apr 24, 2019 at 12:57:14PM +0800, Ley Foon Tan wrote:
> Altera PCIe Rootport IP is a soft IP and is only available after
> FPGA image is programmed.
> 
> Make driver modulable to support use case FPGA image is programmed
> after kernel is booted. User proram FPGA image in kernel then only load
> PCIe driver module.

I'm not objecting to these patches, but help me understand how this
works.  The "usual" scenario is that if a driver is loaded before a
matching device is available, i.e., either the driver is built
statically or it is loaded before a device is hot-added, the event of
the device being available causes the driver's probe method to be
called.

This seems to be a more manual process of programming the FPGA which
results in a new "altera-pcie" platform device.  And then apparently
you need to load the appropriate module by hand?  Is there no
"hot-add" type of event for this platform device that automatically
looks for the driver?

Bjorn

  parent reply	other threads:[~2019-06-04 13:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  4:57 [PATCH] PCI: altera: Allow building as module Ley Foon Tan
2019-04-24  4:57 ` [PATCH] PCI: altera-msi: " Ley Foon Tan
2019-05-14  5:35   ` Ley Foon Tan
2019-05-15 13:59     ` Lorenzo Pieralisi
2019-05-16  2:12       ` Ley Foon Tan
2019-05-30 15:08   ` Lorenzo Pieralisi
2019-05-14  5:35 ` [PATCH] PCI: altera: " Ley Foon Tan
2019-05-30 15:07   ` Lorenzo Pieralisi
2019-06-04 13:18 ` Bjorn Helgaas [this message]
2019-06-11  7:22   ` Ley Foon Tan

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=20190604131848.GA40122@google.com \
    --to=helgaas@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ley.foon.tan@intel.com \
    --cc=lftan.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.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).