From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [PATCH] tpm: Add sysfs interface to show TPM hardware version Date: Tue, 14 Mar 2017 14:42:51 -0700 Message-ID: <1489527771.19081.49.camel@HansenPartnership.com> References: <1489382517-9078-1-git-send-email-Meng.Li@windriver.com> <29B2C361-A0C0-410E-ACCA-07AFA382A251@gmx.de> <9f67321b-50bd-9e6f-61f8-c29ae14f261f@linux.vnet.ibm.com> <074515F2-51E7-485B-B1AB-11B913CC4B46@gmx.de> <20170314212425.GA29359@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170314212425.GA29359-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tpmdd-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Jason Gunthorpe , Peter Huewe Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: tpmdd-devel@lists.sourceforge.net On Tue, 2017-03-14 at 15:24 -0600, Jason Gunthorpe wrote: > On Tue, Mar 14, 2017 at 07:58:37PM +0100, Peter Huewe wrote: > > > > In practice, I suspect that a single user space application won't > > > support both TPMs. > > Think of init scripts. > > Which daemon should it start? > > Right, ideally we'd have a udev rule that triggers systemd to start > the userspace daemons when a TPM is detected, as other hardware does. > > So whatever format we use has to be compatible with udev's matcher.. Technically, we have that already: my TPM2.0 detection stuff for udev triggers off the presence of the SUBSYSTEM=="tpmrm" that matches any TPM2 device but not a 1.x one. James ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752084AbdCNVm5 (ORCPT ); Tue, 14 Mar 2017 17:42:57 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:40124 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750940AbdCNVm4 (ORCPT ); Tue, 14 Mar 2017 17:42:56 -0400 Message-ID: <1489527771.19081.49.camel@HansenPartnership.com> Subject: Re: [tpmdd-devel] [PATCH] tpm: Add sysfs interface to show TPM hardware version From: James Bottomley To: Jason Gunthorpe , Peter Huewe Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Date: Tue, 14 Mar 2017 14:42:51 -0700 In-Reply-To: <20170314212425.GA29359@obsidianresearch.com> References: <1489382517-9078-1-git-send-email-Meng.Li@windriver.com> <29B2C361-A0C0-410E-ACCA-07AFA382A251@gmx.de> <9f67321b-50bd-9e6f-61f8-c29ae14f261f@linux.vnet.ibm.com> <074515F2-51E7-485B-B1AB-11B913CC4B46@gmx.de> <20170314212425.GA29359@obsidianresearch.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2017-03-14 at 15:24 -0600, Jason Gunthorpe wrote: > On Tue, Mar 14, 2017 at 07:58:37PM +0100, Peter Huewe wrote: > > > > In practice, I suspect that a single user space application won't > > > support both TPMs. > > Think of init scripts. > > Which daemon should it start? > > Right, ideally we'd have a udev rule that triggers systemd to start > the userspace daemons when a TPM is detected, as other hardware does. > > So whatever format we use has to be compatible with udev's matcher.. Technically, we have that already: my TPM2.0 detection stuff for udev triggers off the presence of the SUBSYSTEM=="tpmrm" that matches any TPM2 device but not a 1.x one. James