From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/4] Add ACPI support for HiSilicon PCIe Host Controllers
Date: Mon, 8 Feb 2016 09:11:32 -0500 [thread overview]
Message-ID: <56B8A214.8040203@codeaurora.org> (raw)
In-Reply-To: <7297343.ktGck3KQJN@wuerfel>
On 2/8/2016 8:55 AM, Arnd Bergmann wrote:
> I haven't really followed what is going on with ACPI. Do you expect
> to see future machines come out that are not just implementing SBSA
> but that still need to run ACPI? I thought this was just a hack
> for some early machines that only run with ACPI but are not actually
> compliant.
>
> Arnd
I agree. We shouldn't be playing with half-baked ACPI solutions. We have seen
two variants already that claim to be ACPI compliant yet they do not tie into
anything inside ACPICA.
The correct route is to use Tomasz's ACPI PCI root bridge driver and use the ACPI
framework.
If a platform has quirks, Tomasz's patches allow vendors add quirks too.
The combination of PCI host bridge driver + ACPI hack is not right.
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-02-08 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 11:37 [RFC PATCH 0/4] Add ACPI support for HiSilicon PCIe Host Controllers Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 1/4] PCI: Designware: Add support for ACPI based controllers Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 2/4] PCI: hisi: re-architect Hip05/Hip06 controllers driver to preapare for ACPI Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 3/4] PCI: hisi: Make the HiSilicon PCIe host controller ECAM compliant Gabriele Paoloni
2016-02-04 11:37 ` [RFC PATCH 4/4] PCI/ACPI: hisi: Add ACPI support for HiSilicon SoCs Host Controllers Gabriele Paoloni
2016-02-04 13:11 ` [RFC PATCH 0/4] Add ACPI support for HiSilicon PCIe " Arnd Bergmann
2016-02-04 15:11 ` Gabriele Paoloni
2016-02-04 16:07 ` Arnd Bergmann
2016-02-04 16:44 ` Gabriele Paoloni
2016-02-04 17:01 ` Arnd Bergmann
2016-02-04 17:06 ` Gabriele Paoloni
2016-02-08 13:17 ` Gabriele Paoloni
2016-02-08 13:55 ` Arnd Bergmann
2016-02-08 14:11 ` Sinan Kaya [this message]
2016-02-08 16:20 ` Gabriele Paoloni
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=56B8A214.8040203@codeaurora.org \
--to=okaya@codeaurora.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).