Re: Doubt on first access for PCIe device

2017-04-24 Thread abhijit
Hi Lorenzo, I think, you are referring to statement, "The Completion ID field is not meaningful prior to the software initialization and configuration of the completing device (using at least one Configuration Write Request), and for this case the Requester must ignore the value returned in

Re: Doubt on first access for PCIe device

2017-04-24 Thread abhijit
Hi Lorenzo, I think, you are referring to statement, "The Completion ID field is not meaningful prior to the software initialization and configuration of the completing device (using at least one Configuration Write Request), and for this case the Requester must ignore the value returned in

Re: Doubt on first access for PCIe device

2017-04-24 Thread Lorenzo Pieralisi
On Mon, Apr 24, 2017 at 11:52:27AM +0530, abhijit wrote: > Hi Lorenzo, > > Yes that's true.. > > My question is: what if EP function default completer ID means BDF > has values = 0(meaning B = 0, D = 0, f = 0) and Root complex > requester ID also has same BDF, that is 0. > > Is that valid case

Re: Doubt on first access for PCIe device

2017-04-24 Thread Lorenzo Pieralisi
On Mon, Apr 24, 2017 at 11:52:27AM +0530, abhijit wrote: > Hi Lorenzo, > > Yes that's true.. > > My question is: what if EP function default completer ID means BDF > has values = 0(meaning B = 0, D = 0, f = 0) and Root complex > requester ID also has same BDF, that is 0. > > Is that valid case

Re: Doubt on first access for PCIe device

2017-04-24 Thread abhijit
Hi Lorenzo, Yes that's true.. My question is: what if EP function default completer ID means BDF has values = 0(meaning B = 0, D = 0, f = 0) and Root complex requester ID also has same BDF, that is 0. Is that valid case as per PCIe standard, as in this case, requester ID and completion ID

Re: Doubt on first access for PCIe device

2017-04-24 Thread abhijit
Hi Lorenzo, Yes that's true.. My question is: what if EP function default completer ID means BDF has values = 0(meaning B = 0, D = 0, f = 0) and Root complex requester ID also has same BDF, that is 0. Is that valid case as per PCIe standard, as in this case, requester ID and completion ID

Re: Doubt on first access for PCIe device

2017-04-21 Thread Lorenzo Pieralisi
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

Re: Doubt on first access for PCIe device

2017-04-21 Thread Lorenzo Pieralisi
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

Re: Doubt on first access for PCIe device

2017-04-21 Thread abhijit
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

Re: Doubt on first access for PCIe device

2017-04-21 Thread abhijit
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

Re: Doubt on first access for PCIe device

2017-04-19 Thread Lorenzo Pieralisi
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

Re: Doubt on first access for PCIe device

2017-04-19 Thread Lorenzo Pieralisi
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

Re: Doubt on first access for PCIe device

2017-04-18 Thread Jon Masters
On 04/11/2017 10:15 AM, abhijit wrote: > 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? You'll want to

Re: Doubt on first access for PCIe device

2017-04-18 Thread Jon Masters
On 04/11/2017 10:15 AM, abhijit wrote: > 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? You'll want to

Doubt on first access for PCIe device

2017-04-11 Thread abhijit
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

Doubt on first access for PCIe device

2017-04-11 Thread abhijit
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