Serialization of configuration accesses for mvebu/designware

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I've noticed that the mvebu and designware both use spinlocks to
serialize access to the configuration space (pci_ops.[read|write]).
However the read/write ops are only ever used from the pci core
(access.c, pci.c) where they are already protected with the pci_lock.

As far as I can tell these extra spinlocks are superfluous, therefore...

Can they be removed?
Can future host bridge drivers assume that calls to the pci_ops are serialized?

I'm happy to provide a patch for the existing drivers if so.

Thanks,

Andrew Murray
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux