linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: fu.wei@linaro.org (Fu Wei)
To: linux-arm-kernel@lists.infradead.org
Subject: [Linaro-acpi] [PATCH V8 1/8] ACPI: I/O Remapping Table (IORT) initial support
Date: Mon, 5 Sep 2016 23:31:32 +0800	[thread overview]
Message-ID: <CADyBb7uT3sOsnQmWTYDsBXBt+D60PgECxsCaziTb9Zw0bigHpg@mail.gmail.com> (raw)
In-Reply-To: <e287da4e-63bd-2d90-4fdd-dccce9b86459@semihalf.com>

Hi Tomasz,

On 5 September 2016 at 14:12, Tomasz Nowicki <tn@semihalf.com> wrote:
> On 02.09.2016 13:52, Fu Wei wrote:
>>
>> Hi Tomasz,
>>
>> On 11 August 2016 at 18:06, Tomasz Nowicki <tn@semihalf.com> wrote:
>>>
>>> IORT shows representation of IO topology for ARM based systems.
>>> It describes how various components are connected together on
>>> parent-child basis e.g. PCI RC -> SMMU -> ITS. Also see IORT spec.
>>>
>>> http://infocenter.arm.com/help/topic/com.arm.doc.den0049b/DEN0049B_IO_Remapping_Table.pdf
>>>
>>> Initial support allows to detect IORT table presence and save its
>>> root pointer obtained through acpi_get_table(). The pointer validity
>>> depends on acpi_gbl_permanent_mmap because if acpi_gbl_permanent_mmap
>>> is not set while using IORT nodes we would dereference unmapped pointers.
>>>
>>> For the aforementioned reason call iort_table_detect() from acpi_init()
>>> which guarantees acpi_gbl_permanent_mmap to be set at that point.
>>>
>>> Add generic helpers which are helpful for scanning and retrieving
>>> information from IORT table content. List of the most important helpers:
>>> - iort_find_dev_node() finds IORT node for a given device
>>> - iort_node_map_rid() maps device RID and returns IORT node which
>>> provides
>>>   final translation
>>>
>>> IORT support is placed under drivers/acpi/arm64/ new directory due to its
>>> ARM64 specific nature. The code there is considered only for ARM64.
>>> The long term plan is to keep all ARM64 specific tables support
>>> in this place e.g. GTDT table.
>>>
>>> Signed-off-by: Tomasz Nowicki <tn@semihalf.com>
>>> Reviewed-by: Hanjun Guo <hanjun.guo@linaro.org>
>>> ---
>>>  drivers/acpi/Kconfig        |   5 +
>>>  drivers/acpi/Makefile       |   2 +
>>>  drivers/acpi/arm64/Kconfig  |   6 ++
>>>  drivers/acpi/arm64/Makefile |   1 +
>>>  drivers/acpi/arm64/iort.c   | 218
>>> ++++++++++++++++++++++++++++++++++++++++++++
>>>  drivers/acpi/bus.c          |   2 +
>>>  include/linux/iort.h        |  30 ++++++
>>>  7 files changed, 264 insertions(+)
>>>  create mode 100644 drivers/acpi/arm64/Kconfig
>>>  create mode 100644 drivers/acpi/arm64/Makefile
>>>  create mode 100644 drivers/acpi/arm64/iort.c
>>>  create mode 100644 include/linux/iort.h
>>>
>>> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>>> index 445ce28..6cef2d1 100644
>>> --- a/drivers/acpi/Kconfig
>>> +++ b/drivers/acpi/Kconfig
>>> @@ -521,4 +521,9 @@ config ACPI_CONFIGFS
>>>           userspace. The configurable ACPI groups will be visible under
>>>           /config/acpi, assuming configfs is mounted under /config.
>>>
>>> +if ARM64
>>> +source "drivers/acpi/arm64/Kconfig"
>>> +
>>> +endif
>>> +
>>>  endif  # ACPI
>>> diff --git a/drivers/acpi/Makefile b/drivers/acpi/Makefile
>>> index 5ae9d85..e5ada78 100644
>>> --- a/drivers/acpi/Makefile
>>> +++ b/drivers/acpi/Makefile
>>> @@ -105,3 +105,5 @@ obj-$(CONFIG_ACPI_CONFIGFS) += acpi_configfs.o
>>>
>>>  video-objs                     += acpi_video.o video_detect.o
>>>  obj-y                          += dptf/
>>> +
>>> +obj-$(CONFIG_ARM64)            += arm64/
>>> diff --git a/drivers/acpi/arm64/Kconfig b/drivers/acpi/arm64/Kconfig
>>> new file mode 100644
>>> index 0000000..fc818dc
>>> --- /dev/null
>>> +++ b/drivers/acpi/arm64/Kconfig
>>> @@ -0,0 +1,6 @@
>>> +#
>>> +# ACPI Configuration for ARM64
>>> +#
>>> +
>>> +config IORT_TABLE
>>
>>
>> Sorry for nit-picking, but is that better to use ACPI_IORT
>> or maybe ARM64__IORT ??
>
>
> ACPI_IORT sounds good.

Thanks, Tomasz :-)
I have rebaseed my GTDT patchset on your v8 patchset,
But before I post my new patchset, I  hope we can harmonize with each
other on these:

1. ACPI_IORT --  ACPI_GTDT
2. for the file name,  maybe can follow "/drivers/acpi/acpi_*.c" like
acpi_iort.c and acpi_gtdt.c
or  follow "/drivers/acpi/apei/*.c" like iort.c and gtdt.c.

looking forward to you new patchset :-)
Thanks :-)

>
> Tomasz



-- 
Best regards,

Fu Wei
Software Engineer
Red Hat

  reply	other threads:[~2016-09-05 15:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 10:06 [PATCH V8 0/8] Introduce ACPI world to ITS irqchip Tomasz Nowicki
2016-08-11 10:06 ` [PATCH V8 1/8] ACPI: I/O Remapping Table (IORT) initial support Tomasz Nowicki
2016-08-12 16:33   ` Lorenzo Pieralisi
2016-08-18  6:25     ` Tomasz Nowicki
2016-08-31  9:30       ` Lorenzo Pieralisi
2016-08-18 10:55   ` Dennis Chen
2016-08-18 11:14     ` Lorenzo Pieralisi
2016-08-19  3:39       ` Dennis Chen
2016-09-02 11:52   ` [Linaro-acpi] " Fu Wei
2016-09-05  6:12     ` Tomasz Nowicki
2016-09-05 15:31       ` Fu Wei [this message]
2016-08-11 10:06 ` [PATCH V8 2/8] ACPI: Add new IORT functions to support MSI domain handling Tomasz Nowicki
2016-08-12 16:42   ` Lorenzo Pieralisi
2016-08-16  2:15     ` Zheng, Lv
2016-08-16 10:41       ` Marc Zyngier
2016-08-11 10:06 ` [PATCH V8 3/8] PCI/MSI: Setup MSI domain on a per-device basis using IORT ACPI table Tomasz Nowicki
2016-08-11 10:06 ` [PATCH V8 4/8] irqchip/gicv3-its: Cleanup for ITS domain initialization Tomasz Nowicki
2016-08-11 10:06 ` [PATCH V8 5/8] irqchip/gicv3-its: Refactor ITS DT init code to prepare for ACPI Tomasz Nowicki
2016-08-17  8:33   ` Hanjun Guo
2016-08-17 15:58     ` Bjorn Helgaas
2016-08-18  6:42       ` Tomasz Nowicki
2016-08-18  6:55         ` Hanjun Guo
2016-08-11 10:06 ` [PATCH V8 6/8] irqchip/gicv3-its: Probe ITS in the ACPI way Tomasz Nowicki
2016-08-11 10:06 ` [PATCH V8 7/8] irqchip/gicv3-its: Factor out PCI-MSI part that might be reused for ACPI Tomasz Nowicki
2016-08-11 10:06 ` [PATCH V8 8/8] irqchip/gicv3-its: Use MADT ITS subtable to do PCI/MSI domain initialization Tomasz Nowicki

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=CADyBb7uT3sOsnQmWTYDsBXBt+D60PgECxsCaziTb9Zw0bigHpg@mail.gmail.com \
    --to=fu.wei@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).