Excerpts from Frederic Barrat's message of 2016-07-06 20:11:48 +0200: > > Le 04/07/2016 15:22, Ian Munsie a écrit : > > From: Ian Munsie <imun...@au1.ibm.com> > > > > These APIs will be used by the Mellanox CX4 support. While they function > > standalone to configure existing behaviour, their primary purpose is to > > allow the Mellanox driver to inform the cxl driver of a hardware > > limitation, which will be used in a future patch. > > > > Signed-off-by: Ian Munsie <imun...@au1.ibm.com> > > Any way to add a check that the "set max" API is called before the > interrupts are allocated?
I don't think there is any real need - if the set max API has not been called then we use the maximum number of interrupts possible on the PHB, which is the correct thing to do if we don't need the workaround. We could try adding a WARN in the set max API if interrupts have previously been allocated, but realistically - if a driver developer needs to use this they already know it and will be testing for it. Cheers, -Ian _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
