Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1281227 > unrolled thread

Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4 Khalid Aziz <khalid.aziz@oracle.com> - 2015-12-01 22:30 +0100
    Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4 Yinghai Lu <yinghai@kernel.org> - 2015-12-02 05:30 +0100

#1281227 — Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4

On 11/23/2015 07:39 PM, Yinghai Lu wrote:
> On Mon, Nov 23, 2015 at 1:31 PM, Khalid Aziz <khalid.aziz@oracle.com> wrote:
>>> Looks like only the device BAR6 is not assigned form OF?
>>
>> Any progress on this? Do you need any more information from me?
>
> Should be one warning about this device in that system.
>
> We don't need to do anything about it if the device is working with
> this patch set.

Hi Yinghai,

Picking this up again after thanksgiving.......

The device does work with this patch. Doesn't this warning mean BAR6 
resources could not be reserved which means the device driver may not be 
able to get the BAR6 resource at some point if another device grabs the 
unreserved resource?

David M had pointed out an issue with how OF driver uses the same 
address range for all ROMs enabling them only one at a time. That seems 
to be in play here in the issue I am seeing. Does this patch series need 
to address this?

Thanks,
Khalid
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1281437

On Tue, Dec 1, 2015 at 1:23 PM, Khalid Aziz <khalid.aziz@oracle.com> wrote:
> The device does work with this patch.

Good.

> Doesn't this warning mean BAR6
> resources could not be reserved which means the device driver may not be
> able to get the BAR6 resource at some point if another device grabs the
> unreserved resource?

Current sparc pci only have checking, does not have assign unassigned
bar from firmware.

because firmware does not assign resource to that BAR6, the driver may
not need that bar at all.

>
> David M had pointed out an issue with how OF driver uses the same address
> range for all ROMs enabling them only one at a time. That seems to be in
> play here in the issue I am seeing. Does this patch series need to address
> this?

That trick may have problem when we have devices under bridge. as bridge
window need to be setup at first.

If the driver really need to use that trick, it should borrow from BAR0 (MEM)
instead.

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web