Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754574AbbK3T1e (ORCPT ); Mon, 30 Nov 2015 14:27:34 -0500 Received: from quartz.orcorp.ca ([184.70.90.242]:46802 "EHLO quartz.orcorp.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751691AbbK3T1a (ORCPT ); Mon, 30 Nov 2015 14:27:30 -0500 From: Jason Gunthorpe To: Jarkko Sakkinen , tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Cc: Martin Wilck , Peter Huewe , =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= Subject: tpm_tis: Clean up force module parameter Date: Mon, 30 Nov 2015 12:27:10 -0700 Message-Id: <1448911632-20070-1-git-send-email-jgunthorpe@obsidianresearch.com> X-Mailer: git-send-email 2.1.4 X-Broken-Reverse-DNS: no host name found for IP address 10.0.0.160 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 939 Lines: 23 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 force_device needs to be re-used for them. 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. Jason Gunthorpe (2): tpm_tis: Disable interrupt auto probing on a per-device basis tpm_tis: Clean up the force=1 module parameter drivers/char/tpm/tpm_tis.c | 177 +++++++++++++++++++++++++++------------------ 1 file changed, 108 insertions(+), 69 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/