On Fri, 2 Oct 2015 23:56:37 +0200 Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Friday 02 October 2015 15:53:44 Ley Foon Tan wrote: > > > Strictly speaking, if you have undocumented bindings downstream that > > > is your problem and we don't have to accept them as-is upstream. I'm > > > not going to worry about that here. > > > > > >>> txs contains the config space? > > >> It is not the config space, but a memory slave port. > > > > > > Then where is the config space? It should not be part of "ranges" is > > > all I care about. > > The config space is not part of "ranges". Our IP uses TLP packet to > > access config space. > > > > It took me a bit to figure out what you mean here. To save others > from reading the source, here is what I found: > > * The config space is accessed indirectly through registers from the > "cra" register range, which is the right approach according to the > point that Rob made. > * hardware-wise this basically looks like bit-banged PCIe, which is > both awesome and scary ;-) drivers/pcie/host/pcie-host-gpio.c anyone? ;-) M. -- Jazz is not dead. It just smells funny. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
