Hello Jason, On 12/12/2017 07:57 PM, Jason Gunthorpe wrote: > On Tue, Dec 12, 2017 at 12:38:00PM +0100, Javier Martinez Canillas wrote: > >> I'm not familiar with LPC so please let me know if my assumptions are wrong, >> but I find suspicious that a driver for a single device attached to the bus >> can control the CLKRUN# signal which AFAIU may be needed for other devices. > > My understanding was that the fix was to force CLKRUN on before > starting a LPC transaction for TPM. > Yes, I got that part from the commit message and the thread when was posted. > I guess the issues is blindly assuming that CLKRUN started out as off. > It needs to remember the old setting and put it back, and hope against > all hope there isn't another thread mucking with it. > This is the part that worries me, and it seems that assumption was wrong due the reported issues with other PS/2 devices attached to the LPC bus. > Guessing that on a system with a LPC connected superio controller for > PS/2 that CLKRUN will be always high??? > I'm not really familiar with the LPC bus trasmision protocol to comment on this. But if different devices rely on the CLKRUN state, then as you said it needs to remember the old setting and also some synchronization mechanism should be used to serialize access to it and prevent a race? > Jason > Best regards, -- Javier Martinez Canillas Software Engineer - Desktop Hardware Enablement Red Hat
