Re: [PATCH v7 09/15] ACPI: platform-msi: retrieve dev id from IORT

2017-01-16 Thread Hanjun Guo
On 2017/1/16 19:25, Lorenzo Pieralisi wrote: > On Sat, Jan 14, 2017 at 12:28:35PM +0800, Hanjun Guo wrote: >> Hi Lorenzo, >> >> On 2017/1/13 20:11, Lorenzo Pieralisi wrote: >>> On Wed, Jan 11, 2017 at 11:06:33PM +0800, Hanjun Guo wrote: For devices connecting to ITS, it needs dev id to identif

Re: [PATCH v7 09/15] ACPI: platform-msi: retrieve dev id from IORT

2017-01-16 Thread Lorenzo Pieralisi
On Sat, Jan 14, 2017 at 12:28:35PM +0800, Hanjun Guo wrote: > Hi Lorenzo, > > On 2017/1/13 20:11, Lorenzo Pieralisi wrote: > > On Wed, Jan 11, 2017 at 11:06:33PM +0800, Hanjun Guo wrote: > >> For devices connecting to ITS, it needs dev id to identify itself, and > >> this dev id is represented in

Re: [PATCH v7 09/15] ACPI: platform-msi: retrieve dev id from IORT

2017-01-13 Thread Hanjun Guo
Hi Lorenzo, On 2017/1/13 20:11, Lorenzo Pieralisi wrote: > On Wed, Jan 11, 2017 at 11:06:33PM +0800, Hanjun Guo wrote: >> For devices connecting to ITS, it needs dev id to identify itself, and >> this dev id is represented in the IORT table in named component node >> [1] for platform devices, so i

Re: [PATCH v7 09/15] ACPI: platform-msi: retrieve dev id from IORT

2017-01-13 Thread Lorenzo Pieralisi
On Wed, Jan 11, 2017 at 11:06:33PM +0800, Hanjun Guo wrote: > For devices connecting to ITS, it needs dev id to identify itself, and > this dev id is represented in the IORT table in named component node > [1] for platform devices, so in this patch we will scan the IORT to > retrieve device's dev i

[PATCH v7 09/15] ACPI: platform-msi: retrieve dev id from IORT

2017-01-11 Thread Hanjun Guo
For devices connecting to ITS, it needs dev id to identify itself, and this dev id is represented in the IORT table in named component node [1] for platform devices, so in this patch we will scan the IORT to retrieve device's dev id. For named components we know that there are always two steps inv