On Mon, Oct 29, 2018 at 12:04:22PM +0200, Pekka Pessi wrote: > Hi Thierry, > > There is typically one entity (aux cpu or a VM running on CCPLEX) owning the > "empty" or producer side of mailbox (iow, waking up on empty) and another > entity owning the "full" or consumer side of mailbox (waking up on full). An > entity should not muck with the interrupts used by the opposite side. Okay, that explains some of my observations. I was initially trying to program interrupt enables for both FULL and EMPTY interrupts for all mailboxes, but then I'd usually get timeouts because the consumer wasn't responding (i.e. the SPE wasn't getting FULL interrupts for the CCPLEX's TX mailbox). If I understand correctly, you're saying that the CPU should only be using the EMPTY interrupts for it's TX mailbox (while leaving the FULL interrupts completely untouched) and only the FULL interrupt for it's RX mailbox (while leaving the EMPTY interrupts untouched). This is a bit of a problem because the mailbox driver doesn't really know anything about the direction when it starts up, so how would it make the decision about how to program the registers? > One entity typically owns one shared interrupt only. For the > BPMP/SCE/RCE/SPE HSP blocks the shared interrupt 0 is owned by the auxiliary > processor itself, the shared interrupts 1..4 are connected to LIC and are > available to other entities. The convention is to go through the interrupts > 0..4 and then using the first available shared interrupt for both full and > empty. That partially matches another of my observations. It seems like we can't use the shared interrupt 0 at all on at least the AON HSP. That's fine because that HSP instance contains the TX mailbox for TCU and by the current convention in the HSP driver, shared interrupt 0 would be aggregating the FULL interrupts, which according to the above we don't need for TX mailboxes. What's somewhat surprising is that you're saying that both FULL and EMPTY interrupts should be handled by the same shared interrupt. That's the opposite of what the recommended programming sequence is that the TRM specifies. Why is it better to handle both FULL and EMPTY interrupts with the same shared interrupt? > The interrupt functions should use a mask for mailboxes owned by kernel (in > essence what the IE register should be for the HSP shared interrupt owned by > the kernel) and serve only those mailboxes owned by kernel. Note that there > is no reset for HSP in Xavier, and the IE register contents may be stale. Would it be safe to clear all of the IE registers to 0 on driver probe? I seem to remember trying to do that and getting similar behaviour to what I describe above, namely that interrupts on the SPE weren't working anymore. I concluded that the IE register must be shared between the various processors, even though that's somewhat suprising given that there is no way to synchronize accesses to those registers, so their programming would be somewhat up to chance. Do you know any more about these registers? If they are indeed separate for each processor, it should be fairly easy to keep track of the mailboxes used by the kernel and process only those. Again I don't know how exactly to distinguish between TX and RX mailboxes because they all start out the same and only their use defines which direction they go. Currently this works because we program them as consumers by default. That means we enable the FULL interrupts but keep EMPTY interrupts disabled until a message in transmitted on the mailbox, at which point we enable the EMPTY interrupt. I suppose at that point we should also disable the FULL interrupt, given the above discussion. > And lastly, if we want to support only Xavier and later, perhaps we should > be more clear in the bindings? There are no mailbox-specific interrupt > enable registers available on Parker and your design relies on them. That was certainly not the intention. I thought I had seen the per- mailbox interrupt enable registers also in Tegra186 documentation, but after double-checking they're indeed not there. I don't think the driver currently "relies" on them because it uses them in addition to the HSP_IE registers. I suppose that accessing them might cause aborts on Tegra186 if they don't exist, though. I'm not entirely clear on what the advantages are of using the per- mailbox registers, or how they are supposed to be used. The existing documentation doesn't really explain how these are supposed to be used either, so I was mostly just going by trial and error. Do you know anything more on how to use these registers? I can easily make them Tegra194 specific in the code, but if they're aren't any clear advantages, it might just be easier to stick with HSP_IE programming only. Thierry
Attachment:
signature.asc
Description: PGP signature
