Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753265AbbDASTm (ORCPT ); Wed, 1 Apr 2015 14:19:42 -0400 Received: from quartz.orcorp.ca ([184.70.90.242]:58250 "EHLO quartz.orcorp.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752857AbbDASTl (ORCPT ); Wed, 1 Apr 2015 14:19:41 -0400 Date: Wed, 1 Apr 2015 12:19:25 -0600 From: Jason Gunthorpe To: Jarkko Sakkinen Cc: Peter Huewe , Ashley Lai , Marcel Selhorst , tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, christophe.ricard@gmail.com, jason.gunthorpe@obsidianresearch.com, stefanb@linux.vnet.ibm.com Subject: Re: [PATCH] tpm: unified PPI interface for TPM 1.x/2.0 devices Message-ID: <20150401181925.GA20550@obsidianresearch.com> References: <1427891332-16709-1-git-send-email-jarkko.sakkinen@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1427891332-16709-1-git-send-email-jarkko.sakkinen@linux.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Broken-Reverse-DNS: no host name found for IP address 10.0.0.183 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1733 Lines: 60 On Wed, Apr 01, 2015 at 03:28:52PM +0300, Jarkko Sakkinen wrote: > Added PPI interface to the character device. PPI interface is also kept > in the pdev for backwards compatibility. Could you look at just completely moving the PPI interface to the char dev and then adding a symlink from the pdev? That would be really ideal. symlinks have the advantage that they actually fully fix the lifetime issues. This seems doable, if we replace the ppi_attrs group with a bunch of calls to sysfs_create_link it should work ? > +static struct tpm_chip *ppi_dev_to_chip(struct device *dev) > +{ > + struct tpm_chip *chip = dev_get_drvdata(dev); > + > + if (chip == NULL) > + chip = to_tpm_chip(chip); > + > + return chip; > +} If symlinks don't work out, we should probably just set the drvdata on the tpm_chip itself to avoid this. > + if (!(chip->flags & TPM_CHIP_FLAG_PPI)) > + return -EINVAL; Hum, I don't think the PPI files should be created if there is no PPI support.. > +void __init tpm_ppi_init(struct class *tpm_class) > +{ > + tpm_class->dev_groups = tpm_groups; > } So this shouldn't be unconditional. Also, ultimately PPI can't just claim the dev_groups, other parts of the driver will need to add groups too. I think it makes more sense to do struct attribute_group *tpm_ppi_get_sysfs(struct tpm_chip *chip) { } And take care of building the list in the caller. And tpm_ppi_get_sysfs should be called after the driver is readied but before adding the device. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/