On 04/11/15 12:30, Bharat Kumar Gogada wrote: >> >>>> Also, you still lack support for MSI-X (which would come for free...). >>> >>> We don't support MSI-X in root port mode. >> >> I don't believe you. If you support single MSI, you support MSI-X (because >> that's mostly a property of the endpoint). > > In our architecture specification MSI-X is unsupported for Root Port. I still can't believe it, but in the end, that's your own problem. >>>>> + .chip = &nwl_msi_irq_chip, >>>>> +}; >>>>> +#endif >>>>> + >>>>> + >>>>> + /* setup AFI/FPCI range */ >>>>> + msi->pages = __get_free_pages(GFP_KERNEL, 0); >>>>> + base = virt_to_phys((void *)msi->pages); >>>>> + nwl_bridge_writel(pcie, lower_32_bits(base), I_MSII_BASE_LO); >>>>> + nwl_bridge_writel(pcie, upper_32_bits(base), I_MSII_BASE_HI); >>>> >>>> I just read this, and I'm puzzled. Actually, puzzled is an >>>> understatement. Why on Earth do you need to give RAM to your MSI >> HW? >>>> This should be a device, not RAM. By the look of it, this could be >>>> absolutely anything. Are you sure you have to supply RAM here? >>>> >>> This is required in our hardware, so that bridge identifies incoming MWr as >> MSI. >> >> I'm asking why this has to be RAM. What is the actual requirement? > > We are allocating RAM for MSI (which is expected) and assigning this address to msi->pages > this is what EP MSI capability will be programmed with. > For the bridge to detect an incoming MWr from EP as MSI, hardware needs to know MSI address > so the same address is programmed in the hardware register for comparison purpose. > It is the actual requirement from hardware. I understand that you need to provide an address for the bridge to match. I'm asking why this has to be RAM as opposed to any other device address. This seems to be a unique requirement (nobody else does that), and I'd like to understand why there is this requirement. Thanks, 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
