From: Murali Karicheri <m-karicheri2@ti.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Bjorn Helgaas <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, Paul Burton <paul.burton@imgtec.com>
Subject: Re: [PATCH] PCI: keystone: Use PCI_NUM_INTX
Date: Wed, 16 Aug 2017 14:08:15 -0400 [thread overview]
Message-ID: <59948A0F.4010304@ti.com> (raw)
In-Reply-To: <20170815214430.GO32525@bhelgaas-glaptop.roam.corp.google.com>
On 08/15/2017 05:44 PM, Bjorn Helgaas wrote:
> On Tue, Aug 15, 2017 at 04:37:24PM -0500, Bjorn Helgaas wrote:
>> Switch from using a custom MAX_LEGACY_IRQS macro to the generic
>> PCI_NUM_INTX definition for the number of INTx interrupts.
>>
>> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
>> Cc: Murali Karicheri <m-karicheri2@ti.com>
>> ---
>> drivers/pci/dwc/pci-keystone-dw.c | 4 ++--
>> drivers/pci/dwc/pci-keystone.h | 1 -
>> 2 files changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/pci/dwc/pci-keystone-dw.c b/drivers/pci/dwc/pci-keystone-dw.c
>> index df60f48716d9..3b0f206590f9 100644
>> --- a/drivers/pci/dwc/pci-keystone-dw.c
>> +++ b/drivers/pci/dwc/pci-keystone-dw.c
>> @@ -251,7 +251,7 @@ void ks_dw_pcie_enable_legacy_irqs(struct keystone_pcie *ks_pcie)
>> {
>> int i;
>>
>> - for (i = 0; i < MAX_LEGACY_IRQS; i++)
>> + for (i = 0; i < PCI_NUM_INTX; i++)
>> ks_dw_app_writel(ks_pcie, IRQ_ENABLE_SET + (i << 4), 0x1);
>> }
>>
>> @@ -557,7 +557,7 @@ int __init ks_dw_pcie_host_init(struct keystone_pcie *ks_pcie,
>> /* Create legacy IRQ domain */
>> ks_pcie->legacy_irq_domain =
>> irq_domain_add_linear(ks_pcie->legacy_intc_np,
>> - MAX_LEGACY_IRQS,
>> + PCI_NUM_INTX,
>> &ks_dw_pcie_legacy_irq_domain_ops,
>> NULL);
>> if (!ks_pcie->legacy_irq_domain) {
>> diff --git a/drivers/pci/dwc/pci-keystone.h b/drivers/pci/dwc/pci-keystone.h
>> index 74c5825882df..69fc60129f45 100644
>> --- a/drivers/pci/dwc/pci-keystone.h
>> +++ b/drivers/pci/dwc/pci-keystone.h
>> @@ -12,7 +12,6 @@
>> * published by the Free Software Foundation.
>> */
>>
>> -#define MAX_LEGACY_IRQS 4
>> #define MAX_MSI_HOST_IRQS 8
>> #define MAX_LEGACY_HOST_IRQS 4
>
> BTW, Murali, what is MAX_LEGACY_HOST_IRQS? Is that something we can
> replace by PCI_NUM_INTX also?
>
It is the number of interrupts going to the ARM GIC controller for Legacy
PCI interrupts. Corresponding for MSI is MAX_MSI_HOST_IRQS. MAX_LEGACY_IRQS
is for number of PCI Legacy irq line one PCI bus. In keystone case, it is
1 to 1. So it can be changed.
Murali
> (PCI_NUM_INTX is a new definition in include/linux/pci.h for the
> number of INTx interrupts: INTA, INTB, INTC, INTD).
>
--
Murali Karicheri
Linux Kernel, Keystone
next prev parent reply other threads:[~2017-08-16 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 21:37 [PATCH] PCI: keystone: Use PCI_NUM_INTX Bjorn Helgaas
2017-08-15 21:44 ` Bjorn Helgaas
2017-08-16 18:08 ` Murali Karicheri [this message]
2017-08-16 18:41 ` Bjorn Helgaas
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=59948A0F.4010304@ti.com \
--to=m-karicheri2@ti.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=paul.burton@imgtec.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 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).