Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752904AbdLSNKa (ORCPT ); Tue, 19 Dec 2017 08:10:30 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34711 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751981AbdLSNK2 (ORCPT ); Tue, 19 Dec 2017 08:10:28 -0500 X-Google-Smtp-Source: ACJfBovfHH3z/1Wah3xpD/CvT1sShNRaFcaHmHWEMWuxvRAnCTC2ojhpqmkaCoWLZmyf7GJbE/SrjA== Subject: Re: [BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system To: Jarkko Sakkinen Cc: Jason Gunthorpe , James Ettle , linux-integrity@vger.kernel.org, azhar.shaikh@intel.com, linux-kernel@vger.kernel.org, james.l.morris@oracle.com References: <57d96314-cc9c-0656-186e-4eb77a132b70@ettle.org.uk> <34b361bf-cce7-a1ac-f8a3-76ef22f5b6b0@redhat.com> <5fb5de24-5a4c-4c01-1f72-49fc5844516c@ettle.org.uk> <011b4d29-9d93-4b7a-90dd-0c25cf184c3e@redhat.com> <20171214191052.GA20833@ziepe.ca> <20171215145630.ftsnj4azqqhzqwsh@linux.intel.com> <20171215173826.GD12434@ziepe.ca> <1513443676.29063.0.camel@linux.intel.com> <20171219125923.b46fwqfmeaimsonx@linux.intel.com> From: Javier Martinez Canillas Message-ID: <4e7f8b67-9818-b0be-ac69-2fac7a6539b2@redhat.com> Date: Tue, 19 Dec 2017 14:10:25 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171219125923.b46fwqfmeaimsonx@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1510 Lines: 51 Hello Jarkko, On 12/19/2017 01:59 PM, Jarkko Sakkinen wrote: > James, Javier, thank you for sorting this out. I'll just have couple of > minor comments on the patch. > > On Mon, Dec 18, 2017 at 01:22:28PM +0100, Javier Martinez Canillas wrote: >> + u32 vendor, intfcaps, intmask, clkrun_val; > > Could these split into four lines (one declaration per line)? > Yes, I didn't like that either but did this way for consistency with the driver. >> u8 rid; >> int rc, probe; >> struct tpm_chip *chip; >> @@ -772,6 +772,15 @@ int tpm_tis_core_init(struct device *dev, struct tpm_tis_data *priv, int irq, >> ILB_REMAP_SIZE); >> if (!priv->ilb_base_addr) >> return -ENOMEM; >> + >> + clkrun_val = ioread32(priv->ilb_base_addr + LPC_CNTRL_OFFSET); >> + /* Check if CLKRUN# is already not enabled in the LPC bus */ > > /* > >> + if (!(clkrun_val & LPC_CLKRUN_EN)) { >> + priv->flags |= TPM_TIS_CLK_ENABLE; > > Is the flag added just so surpress those WARN()'s? > I believe so. I just included here again for consistency, but I think the flag and the warns can just go away. > I've forgot why the WARN()'s even exist assuming that driver is > functioning correctly. > > /Jarkko > If you agree with the patch, I can post it as a formal patch on a series that do these cleanups as preparatory work. I've also noticed a NULL pointer deref bug in an error path so I'll also fix that too. Best regards, -- Javier Martinez Canillas Software Engineer - Desktop Hardware Enablement Red Hat