From: Ray Jui <rjui@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>,
Mark Rutland <mark.rutland@arm.com>,
Hauke Mehrtens <hauke@hauke-m.de>, <linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pci@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] PCI: iproc: enable arm64 support for iProc PCIe
Date: Tue, 21 Jul 2015 17:01:02 -0700 [thread overview]
Message-ID: <55AEDD3E.6060808@broadcom.com> (raw)
In-Reply-To: <20150721220259.GK21967@google.com>
On 7/21/2015 3:02 PM, Bjorn Helgaas wrote:
> On Tue, Jul 21, 2015 at 01:50:28PM -0700, Ray Jui wrote:
>>
>>
>> On 7/21/2015 1:30 PM, Bjorn Helgaas wrote:
>>> On Wed, Jul 15, 2015 at 09:39:20PM -0700, Ray Jui wrote:
>>>> This patch enables arm64 support to the iProc PCIe driver
>>>
>>> This needs a little more explanation: ARM has a common struct pci_sys_data
>>> but ARM64 does not,
>>
>> Correct, and according to Arnd, there's already work in process of
>> removing the need for pci_sys_data on arm32. Before that is done, we
>> need this in the driver for it to work on both arm32 and arm64.
>>
>> and ARM needs pci_fixup_irqs() but ARM64 does not (why
>>> not?),
>>
>> under arch/arm64/kernel/pci.c:
>>
>> 41 /*
>> 42 * Try to assign the IRQ number from DT when adding a new device
>> 43 */
>> 44 int pcibios_add_device(struct pci_dev *dev)
>> 45 {
>> 46 dev->irq = of_irq_parse_and_map_pci(dev, 0, 0);
>> 47
>> 48 return 0;
>> 49 }
>>
>> interrupt is automatically parsed and mapped when adding a new device
>> for arm64.
>>
>> ARM uses the common pci_sys_data for the PCI sysdata while ARM64
>>> uses a driver-specific sysdata, etc.
>>
>> Correct. pci_sys_data for arm32 will eventually be removed, so all arm32
>> based PCie host should only need to carry driver specific sysdata.
>
> That all makes sense. I'm just looking for a condensed version of it in
> the changelog because it takes some digging to figure it out, and in a
> couple months even the implicit context of "somebody's working to combine
> arm32 and arm64" will be gone. So we need a changelog that motivates this
> patch as it is.
>
Okay I will re-submit a new patch with a commit message that explains
the change in more details.
Thanks,
Ray
WARNING: multiple messages have this Message-ID (diff)
From: rjui@broadcom.com (Ray Jui)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] PCI: iproc: enable arm64 support for iProc PCIe
Date: Tue, 21 Jul 2015 17:01:02 -0700 [thread overview]
Message-ID: <55AEDD3E.6060808@broadcom.com> (raw)
In-Reply-To: <20150721220259.GK21967@google.com>
On 7/21/2015 3:02 PM, Bjorn Helgaas wrote:
> On Tue, Jul 21, 2015 at 01:50:28PM -0700, Ray Jui wrote:
>>
>>
>> On 7/21/2015 1:30 PM, Bjorn Helgaas wrote:
>>> On Wed, Jul 15, 2015 at 09:39:20PM -0700, Ray Jui wrote:
>>>> This patch enables arm64 support to the iProc PCIe driver
>>>
>>> This needs a little more explanation: ARM has a common struct pci_sys_data
>>> but ARM64 does not,
>>
>> Correct, and according to Arnd, there's already work in process of
>> removing the need for pci_sys_data on arm32. Before that is done, we
>> need this in the driver for it to work on both arm32 and arm64.
>>
>> and ARM needs pci_fixup_irqs() but ARM64 does not (why
>>> not?),
>>
>> under arch/arm64/kernel/pci.c:
>>
>> 41 /*
>> 42 * Try to assign the IRQ number from DT when adding a new device
>> 43 */
>> 44 int pcibios_add_device(struct pci_dev *dev)
>> 45 {
>> 46 dev->irq = of_irq_parse_and_map_pci(dev, 0, 0);
>> 47
>> 48 return 0;
>> 49 }
>>
>> interrupt is automatically parsed and mapped when adding a new device
>> for arm64.
>>
>> ARM uses the common pci_sys_data for the PCI sysdata while ARM64
>>> uses a driver-specific sysdata, etc.
>>
>> Correct. pci_sys_data for arm32 will eventually be removed, so all arm32
>> based PCie host should only need to carry driver specific sysdata.
>
> That all makes sense. I'm just looking for a condensed version of it in
> the changelog because it takes some digging to figure it out, and in a
> couple months even the implicit context of "somebody's working to combine
> arm32 and arm64" will be gone. So we need a changelog that motivates this
> patch as it is.
>
Okay I will re-submit a new patch with a commit message that explains
the change in more details.
Thanks,
Ray
next prev parent reply other threads:[~2015-07-22 0:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 4:39 [PATCH v3 0/4] Add Broadcom North Star 2 support Ray Jui
2015-07-16 4:39 ` Ray Jui
2015-07-16 4:39 ` [PATCH v3 1/4] PCI: iproc: enable arm64 support for iProc PCIe Ray Jui
2015-07-16 4:39 ` Ray Jui
2015-07-21 20:30 ` Bjorn Helgaas
2015-07-21 20:30 ` Bjorn Helgaas
2015-07-21 20:50 ` Ray Jui
2015-07-21 20:50 ` Ray Jui
2015-07-21 21:04 ` Ray Jui
2015-07-21 21:04 ` Ray Jui
2015-07-21 22:02 ` Bjorn Helgaas
2015-07-21 22:02 ` Bjorn Helgaas
2015-07-22 0:01 ` Ray Jui [this message]
2015-07-22 0:01 ` Ray Jui
2015-07-16 4:39 ` [PATCH v3 2/4] PCI: iproc: Fix ARM64 dependency in Kconfig Ray Jui
2015-07-16 4:39 ` Ray Jui
2015-07-16 4:39 ` [PATCH v3 3/4] arm64: Add Broadcom iProc family support Ray Jui
2015-07-16 4:39 ` Ray Jui
2015-07-16 4:39 ` [PATCH v3 4/4] arm64: dts: Add Broadcom North Star 2 support Ray Jui
2015-07-16 4:39 ` Ray Jui
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=55AEDD3E.6060808@broadcom.com \
--to=rjui@broadcom.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.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.