All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Tomasz Nowicki <tn@semihalf.com>
Cc: helgaas@kernel.org, will.deacon@arm.com, catalin.marinas@arm.com,
	rafael@kernel.org, hanjun.guo@linaro.org,
	Lorenzo.Pieralisi@arm.com, okaya@codeaurora.org,
	jchandra@broadcom.com, robert.richter@caviumnetworks.com,
	mw@semihalf.com, Liviu.Dudau@arm.com, ddaney@caviumnetworks.com,
	wangyijing@huawei.com, Suravee.Suthikulpanit@amd.com,
	msalter@redhat.com, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linaro-acpi@lists.linaro.org,
	jcm@redhat.com, andrea.gallo@linaro.org, dhdang@apm.com,
	jeremy.linton@arm.com, liudongdong3@huawei.com,
	cov@codeaurora.org
Subject: Re: [RFC PATCH 1/3] pci, acpi: Match PCI config space accessors against platfrom specific ECAM quirks.
Date: Thu, 02 Jun 2016 13:42:43 +0200	[thread overview]
Message-ID: <4347711.qDrKz2s8lr@wuerfel> (raw)
In-Reply-To: <1464856864-18049-2-git-send-email-tn@semihalf.com>

On Thursday, June 2, 2016 10:41:01 AM CEST Tomasz Nowicki wrote:
> +struct pci_ecam_ops *pci_mcfg_get_ops(struct acpi_pci_root *root)
> +{
> +       int bus_num = root->secondary.start;
> +       int domain = root->segment;
> +       struct pci_cfg_fixup *f;
> +
> +       if (!mcfg_table)
> +               return &pci_generic_ecam_ops;
> +
> +       /*
> +        * Match against platform specific quirks and return corresponding
> +        * CAM ops.
> +        *
> +        * First match against PCI topology <domain:bus> then use OEM ID and
> +        * OEM revision from MCFG table standard header.
> +        */
> +       for (f = __start_acpi_mcfg_fixups; f < __end_acpi_mcfg_fixups; f++) {
> +               if ((f->domain == domain || f->domain == PCI_MCFG_DOMAIN_ANY) &&
> +                   (f->bus_num == bus_num || f->bus_num == PCI_MCFG_BUS_ANY) &&
> +                   (!strncmp(f->oem_id, mcfg_table->header.oem_id,
> +                             ACPI_OEM_ID_SIZE)) &&
> +                   (f->oem_revision == mcfg_table->header.oem_revision))
> +                       return f->ops;
> +       }
> +       /* No quirks, use ECAM */
> +       return &pci_generic_ecam_ops;
> +}
> +
>  int pci_mcfg_lookup(struct acpi_pci_root *root)

Can you explain the use of pci_ecam_ops instead of pci_ops here?

I was hoping we'd be able to fold all of pci-ecam code into the
generic PCI layer at some point and get rid of pci_ecam_ops in the
process.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/3] pci, acpi: Match PCI config space accessors against platfrom specific ECAM quirks.
Date: Thu, 02 Jun 2016 13:42:43 +0200	[thread overview]
Message-ID: <4347711.qDrKz2s8lr@wuerfel> (raw)
In-Reply-To: <1464856864-18049-2-git-send-email-tn@semihalf.com>

On Thursday, June 2, 2016 10:41:01 AM CEST Tomasz Nowicki wrote:
> +struct pci_ecam_ops *pci_mcfg_get_ops(struct acpi_pci_root *root)
> +{
> +       int bus_num = root->secondary.start;
> +       int domain = root->segment;
> +       struct pci_cfg_fixup *f;
> +
> +       if (!mcfg_table)
> +               return &pci_generic_ecam_ops;
> +
> +       /*
> +        * Match against platform specific quirks and return corresponding
> +        * CAM ops.
> +        *
> +        * First match against PCI topology <domain:bus> then use OEM ID and
> +        * OEM revision from MCFG table standard header.
> +        */
> +       for (f = __start_acpi_mcfg_fixups; f < __end_acpi_mcfg_fixups; f++) {
> +               if ((f->domain == domain || f->domain == PCI_MCFG_DOMAIN_ANY) &&
> +                   (f->bus_num == bus_num || f->bus_num == PCI_MCFG_BUS_ANY) &&
> +                   (!strncmp(f->oem_id, mcfg_table->header.oem_id,
> +                             ACPI_OEM_ID_SIZE)) &&
> +                   (f->oem_revision == mcfg_table->header.oem_revision))
> +                       return f->ops;
> +       }
> +       /* No quirks, use ECAM */
> +       return &pci_generic_ecam_ops;
> +}
> +
>  int pci_mcfg_lookup(struct acpi_pci_root *root)

Can you explain the use of pci_ecam_ops instead of pci_ops here?

I was hoping we'd be able to fold all of pci-ecam code into the
generic PCI layer at some point and get rid of pci_ecam_ops in the
process.

	Arnd

  reply	other threads:[~2016-06-02 11:42 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02  8:41 [RFC PATCH 0/3] ECAM quirks handling for ARM64 platforms Tomasz Nowicki
2016-06-02  8:41 ` Tomasz Nowicki
2016-06-02  8:41 ` [RFC PATCH 1/3] pci, acpi: Match PCI config space accessors against platfrom specific ECAM quirks Tomasz Nowicki
2016-06-02  8:41   ` Tomasz Nowicki
2016-06-02  8:41   ` Tomasz Nowicki
2016-06-02 11:42   ` Arnd Bergmann [this message]
2016-06-02 11:42     ` Arnd Bergmann
2016-06-02 12:07     ` Tomasz Nowicki
2016-06-02 12:07       ` Tomasz Nowicki
2016-06-02 12:32       ` Arnd Bergmann
2016-06-02 12:32         ` Arnd Bergmann
2016-06-02 13:35         ` Tomasz Nowicki
2016-06-02 13:35           ` Tomasz Nowicki
2016-06-02 15:19           ` Arnd Bergmann
2016-06-02 15:19             ` Arnd Bergmann
2016-06-14  9:06             ` Tomasz Nowicki
2016-06-14  9:06               ` Tomasz Nowicki
2016-06-03 15:15   ` Christopher Covington
2016-06-03 15:15     ` Christopher Covington
2016-06-03 15:32     ` Gabriele Paoloni
2016-06-03 15:32       ` Gabriele Paoloni
2016-06-03 15:32       ` Gabriele Paoloni
2016-06-03 15:32       ` Gabriele Paoloni
2016-06-03 16:57       ` David Daney
2016-06-03 16:57         ` David Daney
2016-06-03 16:57         ` David Daney
2016-06-03 16:57         ` David Daney
2016-06-03 16:59       ` Jeffrey Hugo
2016-06-03 16:59         ` Jeffrey Hugo
2016-06-03 16:59         ` Jeffrey Hugo
2016-06-03 16:59         ` Jeffrey Hugo
2016-06-06  7:27         ` Gabriele Paoloni
2016-06-06  7:27           ` Gabriele Paoloni
2016-06-06  7:27           ` Gabriele Paoloni
2016-06-06  7:27           ` Gabriele Paoloni
2016-06-06  7:54           ` Hanjun Guo
2016-06-06  7:54             ` Hanjun Guo
2016-06-06  7:54             ` Hanjun Guo
2016-06-06  7:54             ` Hanjun Guo
2016-06-02  8:41 ` [RFC PATCH 2/3] arm64, pci: Start using quirks handling for ACPI based PCI host controller Tomasz Nowicki
2016-06-02  8:41   ` Tomasz Nowicki
2016-06-02  8:41 ` [RFC PATCH 3/3] pci, pci-thunder-pem: Add ACPI support for ThunderX PEM Tomasz Nowicki
2016-06-02  8:41   ` Tomasz Nowicki
2016-07-19 21:17 ` [RFC PATCH 0/3] ECAM quirks handling for ARM64 platforms Bjorn Helgaas
2016-07-19 21:17   ` Bjorn Helgaas
2016-07-19 21:17   ` Bjorn Helgaas
2016-07-20  5:05   ` Tomasz Nowicki
2016-07-20  5:05     ` 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=4347711.qDrKz2s8lr@wuerfel \
    --to=arnd@arndb.de \
    --cc=Liviu.Dudau@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=andrea.gallo@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=cov@codeaurora.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=dhdang@apm.com \
    --cc=hanjun.guo@linaro.org \
    --cc=helgaas@kernel.org \
    --cc=jchandra@broadcom.com \
    --cc=jcm@redhat.com \
    --cc=jeremy.linton@arm.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=msalter@redhat.com \
    --cc=mw@semihalf.com \
    --cc=okaya@codeaurora.org \
    --cc=rafael@kernel.org \
    --cc=robert.richter@caviumnetworks.com \
    --cc=tn@semihalf.com \
    --cc=wangyijing@huawei.com \
    --cc=will.deacon@arm.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.