[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQX4XujVNBXTL_TaEyPPiGgANwa9eavBL23eyZOJbG2f5w@mail.gmail.com>
Date: Wed, 21 Oct 2015 18:15:27 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
David Miller <davem@...emloft.net>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Wei Yang <weiyang@...ux.vnet.ibm.com>, TJ <linux@....tj>,
Yijing Wang <wangyijing@...wei.com>,
Khalid Aziz <khalid.aziz@...cle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7 03/60] sparc/PCI: Unify pci_register_region()
On Wed, Oct 21, 2015 at 3:59 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Wed, Oct 21, 2015 at 3:32 PM, Yinghai Lu <yinghai@...nel.org> wrote:
>> On Wed, Oct 21, 2015 at 11:50 AM, Bjorn Helgaas <helgaas@...nel.org> wrote:
>>> Lots of other architectures have both mem32 and mem64 apertures. You
>>> haven't explained what's unique about sparc yet. Does
>>> pci_find_parent_resource() not work on sparc? If not, is that because the
>>> resource tree looks different on sparc than on other architectures? If so,
>>> is that difference something intentional that we want to keep, or should we
>>> converge on a single resource tree format across all architectures?
>>
>> In the new pci_register_legacy_regions(), we only have root bus.
>> but current pci_find_parent_resource is taking pci dev.
>>
>> So will need to change it to take bus instead, please check if you are ok
>> with following, then I would update other two.
>
> Never mind, I could just one dummy pci device to work around it.
> so don't need to change that.
Khalid,
Please use attached two to replace patch2, patch3 and patch4.
Thanks
Yinghai
View attachment "sparc_fix_range_offset.patch" of type "text/x-patch" (7981 bytes)
View attachment "sparc_simplify_region_reserve.patch" of type "text/x-patch" (6354 bytes)
Powered by blists - more mailing lists