linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Naveen Kumar Parna <pnaveenkos@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: PCIe: Xilinx: sdhci-pci: probe() issue
Date: Mon, 20 Jul 2015 08:33:18 -0500	[thread overview]
Message-ID: <CAErSpo5hak56Xm-AqHDM1D+gEiCi+a5r-9cA7bJZWpNO+2oZGw@mail.gmail.com> (raw)
In-Reply-To: <CAG0bkv+Sve7+XWtGk-kkQU=-64CPbpE=5RMbVq-RzWNgg--6ZQ@mail.gmail.com>

Hi Naveen,

On Mon, Jul 20, 2015 at 5:55 AM, Naveen Kumar Parna
<pnaveenkos@gmail.com> wrote:
> Hi ,
>
> I have a Verilog image & hardware which provides a PCIe interface with
> two BAR’s(BAR0 & BAR1) to host.
>
> BAR0 is having customized UART, GPIO and 1-wire prom modules. These
> modules are accessed via customized PCIe interface driver.
>
> BAR1 is having SD Host controller as per SD Specifications. Here
> requirement is such that we should use Linux kernel stack drivers
> (sdhci.ko & sdhci-pci.ko).
>
>
> Here the issue is only one driver’s probe() function gets executed
> i.e. either customized PCIe driver or sdhci-pci.ko.

The PCI infrastructure is designed such that a bus/device/function
address identifies a single device.  To that device, we can attach a
single driver, which manages all BARs on that device.  There is no
provision for attaching one driver to BAR0 and a different driver to
BAR1.

To manage the device you describe, you'd have to have a driver that
claims the entire PCI device, including both BARs.  That driver would
internally deal with the UART, GPIO, 1-wire prom, and SD host
controller modules.

Bjorn

  reply	other threads:[~2015-07-20 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 10:55 PCIe: Xilinx: sdhci-pci: probe() issue Naveen Kumar Parna
2015-07-20 13:33 ` Bjorn Helgaas [this message]
2015-07-20 14:16   ` Naveen Kumar Parna

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=CAErSpo5hak56Xm-AqHDM1D+gEiCi+a5r-9cA7bJZWpNO+2oZGw@mail.gmail.com \
    --to=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=pnaveenkos@gmail.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).