linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: abhijit naik <abhijitnaik27@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: Doubt on first access for PCIe device
Date: Fri, 21 Apr 2017 16:59:00 +0100	[thread overview]
Message-ID: <20170421155900.GA19059@red-moon> (raw)
In-Reply-To: <CANaY3hNcB0Yk=2f7S+J2r+wtd6T7mLd+ZNprNHFkMegZzvx7pQ@mail.gmail.com>

On Fri, Apr 21, 2017 at 03:33:45PM +0530, abhijit naik wrote:
>    Hi Lorenzo,
>    Thank you very much for reply.
>    As you mentioned I noted that, "If a Function must generate a Completion
>    prior to the initial device Configuration Write Request, 0's must be
>    entered into the Bus Number and Device Number fields"
>    By above statement this means that completion ID will be 0x0000. For the
>    first device on any bus,  device number will be 0 and function number will
>    be 0.
>    Isn't completer (for configuration read) packet will be addressing itself
>    instead of root complex with bus, device and function number 0?

I don't understand what you are asking. The completion (containing
the read data) is routed back to the initiator via ID (of the requester)
routing.

2.2.4.2
2.2.9

Lorenzo

>    On Wed, Apr 19, 2017 at 3:56 PM, Lorenzo Pieralisi
>    <lorenzo.pieralisi@arm.com> wrote:
> 
>      On Tue, Apr 11, 2017 at 07:45:40PM +0530, abhijit wrote:
>      >
>      > Hi All,
>      >
>      > I was referring Linux code for PCIe enumeration and I have one doubt
>      > w.r.t to very first operation that must be done on device.
>      >
>      > Currently while scanning for device, we directly read vendor ID from
>      > device. But PCIE base specification
>      > "CB-PCI_Express_Base_4.0r0.7_November-11-2016.pdf" section 2.2.6.2
>      > specifies that,
>      >
>      > "Functions must capture the Bus and Device Numbers supplied with all
>      > Type 0 Configuration Write Requests completed by the Function and
>      > supply these numbers in the Bus and Device Number fields of the
>      > Requester ID for all Requests initiated by the Device/Function."
> 
>      Please note:
>      "for all Requests initiated by the Device/Function".
>                        ^^^^^^^^^
>      > Here I am assuming, the completer ID will be device number and
>      > function number that will eventually programmed in to  device. In
>      > that case, my question is, without first write, how read
>      > request(VENDOR ID read) is serviced/routed?
> 
>      That's not initiated by the endpoint device, it is routed by
>      requester ID, which is the requester ID of the configuration
>      request - ie master (ie root complex) requester ID.
> 
>      Read 2.2.9 - Completion rules
> 
>      HTH,
>      Lorenzo
> 
>    --
>    Best wishes,
>    Abhijit Naik

  parent reply	other threads:[~2017-04-21 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 14:15 Doubt on first access for PCIe device abhijit
2017-04-19  5:00 ` Jon Masters
2017-04-19 10:26 ` Lorenzo Pieralisi
     [not found]   ` <CANaY3hNcB0Yk=2f7S+J2r+wtd6T7mLd+ZNprNHFkMegZzvx7pQ@mail.gmail.com>
2017-04-21 15:59     ` Lorenzo Pieralisi [this message]
2017-04-24  6:22       ` abhijit
2017-04-24 10:01         ` Lorenzo Pieralisi
2017-04-24 11:15           ` abhijit
2017-04-21 10:07 ` abhijit

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=20170421155900.GA19059@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --cc=abhijitnaik27@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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).