From: Jeremy Linton <jeremy.linton@arm.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: liguozhu@hisilicon.com,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
linaro-acpi@lists.linaro.org, catalin.marinas@arm.com,
Liviu.Dudau@arm.com, linux-kernel@vger.kernel.org,
will.deacon@arm.com, linux-acpi@vger.kernel.org,
wangzhou1@hisilicon.com, hanjun.guo@linaro.org,
liudongdong3@huawei.com, linux-pci@vger.kernel.org,
wangyijing@huawei.com, tn@semihalf.com, tglx@linutronix.de,
xuwei5@hisilicon.com, bhelgaas@google.com,
jiang.liu@linux.intel.com
Subject: Re: [RFC PATCH 1/2] PCI/ACPI: Add ACPI support for non ECAM Host Bridge Controllers
Date: Fri, 4 Dec 2015 14:46:19 -0600 [thread overview]
Message-ID: <5661FB9B.20201@arm.com> (raw)
In-Reply-To: <5018756.5lEEeJVMod@wuerfel>
On 12/03/2015 02:58 PM, Arnd Bergmann wrote:
> On Thursday 03 December 2015 17:58:26 Lorenzo Pieralisi wrote:
>> I will put together a proposal to define the way we specify HID and
>> related DSD properties for PCI host controllers and send it to
>> the ACPI working group for review.
>
> That also requires a change to SBSA, right? Today, SBSA assumes that
> we have a standard PCI host that will work with any hardware independent
> PCI implementation in an OS. We either have to give up on SBSA saying
> much about how PCI hosts are implemented, or stop assuming that hardware
> is SBSA compliant.
Which would be standardizing nonstandard hardware. It would surprise me
if that got much traction.
WARNING: multiple messages have this Message-ID (diff)
From: jeremy.linton@arm.com (Jeremy Linton)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/2] PCI/ACPI: Add ACPI support for non ECAM Host Bridge Controllers
Date: Fri, 4 Dec 2015 14:46:19 -0600 [thread overview]
Message-ID: <5661FB9B.20201@arm.com> (raw)
In-Reply-To: <5018756.5lEEeJVMod@wuerfel>
On 12/03/2015 02:58 PM, Arnd Bergmann wrote:
> On Thursday 03 December 2015 17:58:26 Lorenzo Pieralisi wrote:
>> I will put together a proposal to define the way we specify HID and
>> related DSD properties for PCI host controllers and send it to
>> the ACPI working group for review.
>
> That also requires a change to SBSA, right? Today, SBSA assumes that
> we have a standard PCI host that will work with any hardware independent
> PCI implementation in an OS. We either have to give up on SBSA saying
> much about how PCI hosts are implemented, or stop assuming that hardware
> is SBSA compliant.
Which would be standardizing nonstandard hardware. It would surprise me
if that got much traction.
next prev parent reply other threads:[~2015-12-04 20:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 15:19 [RFC PATCH 0/2] PCI/ACPI: HiSi: Add ACPI support for Hip05 PCIe Host Bridge Controller Gabriele Paoloni
2015-12-03 15:19 ` Gabriele Paoloni
2015-12-03 15:19 ` Gabriele Paoloni
2015-12-03 15:19 ` [RFC PATCH 1/2] PCI/ACPI: Add ACPI support for non ECAM Host Bridge Controllers Gabriele Paoloni
2015-12-03 15:19 ` Gabriele Paoloni
2015-12-03 15:19 ` Gabriele Paoloni
2015-12-03 17:58 ` Lorenzo Pieralisi
2015-12-03 17:58 ` Lorenzo Pieralisi
2015-12-03 20:58 ` Arnd Bergmann
2015-12-03 20:58 ` Arnd Bergmann
2015-12-04 12:04 ` Lorenzo Pieralisi
2015-12-04 12:04 ` Lorenzo Pieralisi
2015-12-04 13:57 ` Arnd Bergmann
2015-12-04 13:57 ` Arnd Bergmann
2015-12-04 16:22 ` Gabriele Paoloni
2015-12-04 16:22 ` Gabriele Paoloni
2015-12-11 14:17 ` Tomasz Nowicki
2015-12-11 14:17 ` Tomasz Nowicki
2015-12-04 20:46 ` Jeremy Linton [this message]
2015-12-04 20:46 ` Jeremy Linton
2015-12-04 21:34 ` Arnd Bergmann
2015-12-04 21:34 ` Arnd Bergmann
2015-12-04 22:48 ` Jeremy Linton
2015-12-04 22:48 ` Jeremy Linton
2015-12-04 12:47 ` Gabriele Paoloni
2015-12-04 12:47 ` Gabriele Paoloni
2015-12-04 12:47 ` Gabriele Paoloni
2015-12-04 20:38 ` Jeremy Linton
2015-12-04 20:38 ` Jeremy Linton
2015-12-03 15:19 ` [RFC PATCH 2/2] PCI/ACPI: HiSi: Add ACPI support for HiSi PCIe Host Bridge Gabriele Paoloni
2015-12-03 15:19 ` Gabriele Paoloni
2015-12-03 15:19 ` 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=5661FB9B.20201@arm.com \
--to=jeremy.linton@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=gabriele.paoloni@huawei.com \
--cc=hanjun.guo@linaro.org \
--cc=jiang.liu@linux.intel.com \
--cc=liguozhu@hisilicon.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=tglx@linutronix.de \
--cc=tn@semihalf.com \
--cc=wangyijing@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.