Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2769211ybc; Wed, 20 Nov 2019 20:50:07 -0800 (PST) X-Google-Smtp-Source: APXvYqwaWR6lK4XOEz39cVZ+WSGWM1Owt4Adl/GQayEG+QoMqqvYZiAcoMnfv1TSn9XRjHKByoJ+ X-Received: by 2002:a17:906:2e52:: with SMTP id r18mr11038749eji.178.1574311807166; Wed, 20 Nov 2019 20:50:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574311807; cv=none; d=google.com; s=arc-20160816; b=S/Mzl29Ol9fG8/Y7V3BfS47F948qxbevfSyk2hbA+LNXqXMOnkrQ2K7xrmNp1eB9NA LnySKVn9R8n1PUBhecOMjdmLLzAJAj1l8RBKDMUMC6S8WY+3xMBJjPErR1yh9qE7lDi4 NBrqz/iSeggakP6Hdcakrv1381VSgTpw5LpHmdZ6OpGhMsBRHquz6NXgQci39yeSE3ar 9c9T50+FZy9SgOlL1Bb7eRyOnrSOHbF/zBAxT6VkFHDL/JlQHIEXmJ1SiP1hOSg0aV9w S1cDrN508XU1PUjPsGewCpqh2gvwEGFqrbJ3CRl6KIgx2amQ5F9T5VPtqc6N/2qRxYLE UWVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=fh2kN/lU7mRPHokRtJd6e3fCEFIJiroZZ0yxElbfzqs=; b=p1T0Nn7N2NsIMmGu03VgMh0e5WdLpBpXqCU83Davu7aqjKnxyyxN387I1jsT2VZewd K+gL7ULZGch2DSyDUWafBto16nPeguX7zSoZ1nxOa740MvmIp1j/uAuFs02j3LAP/NKw 2He+qKaqMlbO0fVaQ8msmPRL1vxxUWVnRtv1iB1qAC7xFzz7NVF0pgZQT+NOhyk7xX+p T+0vDnM1eMLE0mffCi9RwnMMJWk7u0Xm/+HhSEiQpXc/m3LuqPr0S/t4YsvzofX3e/Pz LivjL3MZprz9rwSkXOOF4HYdM/33vfgP8XFUIhoM700JBcs9DEtbMhk2ylIbzDPfN+6w p0CA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=jA3ylDn3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u19si933952ejx.150.2019.11.20.20.49.39; Wed, 20 Nov 2019 20:50:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=jA3ylDn3; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726132AbfKUEsi (ORCPT + 99 others); Wed, 20 Nov 2019 23:48:38 -0500 Received: from mail-il1-f194.google.com ([209.85.166.194]:36683 "EHLO mail-il1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725819AbfKUEsh (ORCPT ); Wed, 20 Nov 2019 23:48:37 -0500 Received: by mail-il1-f194.google.com with SMTP id s75so2009130ilc.3; Wed, 20 Nov 2019 20:48:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fh2kN/lU7mRPHokRtJd6e3fCEFIJiroZZ0yxElbfzqs=; b=jA3ylDn3R3rlm4ISMWmWOZLv3cbhukQnCFPvuaVeBxawOL684lGXZxJ8blgLbTLQ0l jTXN4y2umAWY1w66x+eKSqVInaRvSB+myglrsWUpwQpUSybDLFbfvVfVss90Jz3eEvPJ xzB67KjCRlz1vJHybZ8IpjQg+LygNev64Wa1JplRnPh7xhAPu9XbN/aYcj5o8RGt2lVg +X2dYp0dR8caWXL7llZ4PzTx8KENv6c6YmR5AEv6oa3/ruy2592VPdRm2Mh4II/KR1vY CblbTmbAzZ9/9ieQKHgeZ2NrRwu4v3FET5Ig+yJYnAWZ55iyIlcKG4lSlwh8QiMdp6G7 wDnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fh2kN/lU7mRPHokRtJd6e3fCEFIJiroZZ0yxElbfzqs=; b=D5gOkvkZKteAoCfuINcTyVm+Vsg49ZAAoZJg4SK8tTZcgEvAraFp+LB4GRIclccbB3 O35F+38pgTXgrNavhZxTQqB/T8cNNRTfLNupHl5C51kEC6W/01/MBD3CV6pz5eUgBVYT MV26JCSln677ntxeY8R8RSobA41NY2FsRG6WERmEXbMnCufpoxIrDXtPDBA7MYX0f3xQ f5syT05p8/2qvsRdGjEWKTY7eUp+IjPdakmqp5efG/+92PCT5JLzakZIKDslUKYBdoVs J9qsNlrk+M0MBPo2BJVlTSZ9gI8lw1HrGHWBJHiE7EKFnC5a2/8OqyvewlZr5MXnNOwm uM7w== X-Gm-Message-State: APjAAAWOODc68dqWonPFvK6G4E3Y4f38jzc4lkv2nLa6sQ6FvLpAltcQ 0PuopkrkuJBxMKTkTbi+2focBYMuEYj3DTBNVK8= X-Received: by 2002:a92:ba04:: with SMTP id o4mr8252986ili.19.1574311716391; Wed, 20 Nov 2019 20:48:36 -0800 (PST) MIME-Version: 1.0 References: <20190902143121.pjnykevzlajlcrh6@linux.intel.com> In-Reply-To: <20190902143121.pjnykevzlajlcrh6@linux.intel.com> From: Dan Williams Date: Wed, 20 Nov 2019 20:48:25 -0800 Message-ID: Subject: Re: [GIT PULL] tpmdd updates for Linux v5.4 To: Jarkko Sakkinen Cc: Linus Torvalds , Linux Kernel Mailing List , linux-integrity@vger.kernel.org, James Morris , Stefan Berger , stable , Dan Williams Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 2, 2019 at 7:34 AM Jarkko Sakkinen wrote: > > Hi > > A new driver for fTPM living inside ARM TEE was added this round. In > addition to that, there is three bug fixes and one clean up. > > /Jarkko > > The following changes since commit 8fb8e9e46261e0117cb3cffb6dd8bb7e08f8649b: > > Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2019-08-30 09:23:45 -0700) > > are available in the Git repository at: > > git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20190902 > > for you to fetch changes up to e8bd417aab0c72bfb54465596b16085702ba0405: > > tpm/tpm_ftpm_tee: Document fTPM TEE driver (2019-09-02 17:08:35 +0300) > > ---------------------------------------------------------------- > tpmdd updates for Linux v5.4 > > ---------------------------------------------------------------- > Jarkko Sakkinen (1): > tpm: Remove a deprecated comments about implicit sysfs locking > > Lukas Bulwahn (1): > MAINTAINERS: fix style in KEYS-TRUSTED entry > > Sasha Levin (2): > tpm/tpm_ftpm_tee: A driver for firmware TPM running inside TEE > tpm/tpm_ftpm_tee: Document fTPM TEE driver > > Stefan Berger (2): > tpm_tis_core: Turn on the TPM before probing IRQ's > tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts Hi Jarrko, I'm replying here because I can't find the patches to reply to directly from LKML. Commit 7f064c378e2c "tpm_tis_core: Turn on the TPM before probing IRQ's" in the v5.3-stable tree caused a regression on a pre-release platform with a TPM2 device. The interrupt starts screaming when the driver is loaded and does not stop until the device is force unbond from the driver by: echo IFX0740:00 > /sys/bus/platform/drivers/tpm_tis/unbind I checked v5.4-rc8 and it has the same problem. I tried reverting: 1ea32c83c699 tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts 5b359c7c4372 tpm_tis_core: Turn on the TPM before probing IRQ's Which silenced the screaming interrupt problem, but now the TPM is reporting: [ 3.725131] tpm_tis IFX0740:00: 2.0 TPM (device-id 0x1B, rev-id 16) [ 3.725358] tpm tpm0: tpm_try_transmit: send(): error -5 [ 3.725359] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead ...at load, where it was not reporting this previously. Can you take a look?