On Tue, 2014-04-08 at 17:18 -0400, Mark Lord wrote:
> > I assume you're talking about the one added by cf3e1feba7f9 ("PCI:
> > Workaround missing pci_set_master in pci drivers"), but as far as I
> > can tell, it only calls pci_set_master() for *bridge* devices. What
> > am I missing? Is pci_set_master() being called for your endpoint?
> > What path is that?
>
> Yes, it is being called during execution of the _probe() function in my
> driver,
> as evidenced by the annoying (and wrong) message it produces.
>
> Next time I've got the hardware at hand, I'll put a "dump_stack()" into there
> to see the exact calling path.
Note that one of the reason we want to do it early on bridges is that without
it,
we may also not get the PCIe error messages.
Cheers,
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
