Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756284AbbLAVOz (ORCPT ); Tue, 1 Dec 2015 16:14:55 -0500 Received: from mga03.intel.com ([134.134.136.65]:63897 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753070AbbLAVOy (ORCPT ); Tue, 1 Dec 2015 16:14:54 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,370,1444719600"; d="scan'208";a="610868337" Date: Tue, 1 Dec 2015 23:14:49 +0200 From: Jarkko Sakkinen To: Jason Gunthorpe Cc: tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org, Martin Wilck , Peter Huewe , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Subject: Re: [PATCH v2 0/3] tpm_tis: Clean up force module parameter Message-ID: <20151201211449.GB5071@intel.com> References: <1448996309-15220-1-git-send-email-jgunthorpe@obsidianresearch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1448996309-15220-1-git-send-email-jgunthorpe@obsidianresearch.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2023 Lines: 49 On Tue, Dec 01, 2015 at 11:58:26AM -0700, Jason Gunthorpe wrote: > Drive the force=1 flow through the driver core. There are two main reasons to do this: > 1) To enable tpm_tis for OF environments requires a platform_device anyhow, so > the probe/release code needs to be re-used for that. > 2) Recent changes in the core code break the assumption that a driver will be > 'attached' to things created through platform_device_register_simple, > which causes the tpm core to blow up. > > v2: > - Make sure we request the mem resource in tpm_tis to avoid double-loading > the driver > - Re-order the init sequence so that a forced platform device gets first crack at > loading, and excludes the other mechanisms via the above > - Checkpatch clean > - Gotos renamed > > Martin, this should fix the double loading you noticed, please confirm. There > is a possibility the force path needs a bit more code to be compatible with > devm_ioremap_resource, I'm not sure, hoping not. Just wanted to quickly say that I'm good with your interrupt rework patches. I did only one squash as you can see: https://github.com/jsakkine/linux-tpmdd/commits/master For the other changes your arguments how patches should be separated in this rework made perfect sense after a few re-reads. I can accept them once I've tested them but in order to test them we have to get these patches reviewed first as soon as possible. /Jarkko > Jason Gunthorpe (3): > tpm_tis: Disable interrupt auto probing on a per-device basis > tpm_tis: Use devm_ioremap_resource > tpm_tis: Clean up the force=1 module parameter > > drivers/char/tpm/tpm_tis.c | 203 +++++++++++++++++++++++++++------------------ > 1 file changed, 122 insertions(+), 81 deletions(-) > > -- > 2.1.4 > -- 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/