Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp3956997ybv; Mon, 10 Feb 2020 09:30:48 -0800 (PST) X-Google-Smtp-Source: APXvYqxjvhghV9ntlm3NnqiMWAIZ6nvNH9V1FbtX7lcDmX3uqQ71iNaKkwlfjWO1saCSqFt8eRvr X-Received: by 2002:a9d:7086:: with SMTP id l6mr1822098otj.294.1581355847939; Mon, 10 Feb 2020 09:30:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581355847; cv=none; d=google.com; s=arc-20160816; b=p4fU90kcwrpQ1r9i23J5stxy/RhcDs9/AAwduOy7SrYRYzHEeQ7/9BmBKDHXiFy9mF /cQBzQTS8WM2q/6IojH6MmS0OGbnCyBZbxbHSKEdXWzE3Y/hrXAqatx0Ef3MDE3So5fc KGYGiv4StueX7wto6/2Jnmg1FmIOutBYQXJw6vKLXU0ShVKHMjW1TzkqL74lUX1mJx0x AzvFpuHo7v93v6qqTISZ3qzTEGGmeh10ex90fS7L8DJzNmQysQHqGcu9Ns+2vRQmUB36 t49FJvL4hET+gVyS4mMSjl0eLlqRymsuSkk89hp80dXhIlR9EcV3d2F6LnvAGAPmCsSc BdaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=LUTb7muI1ZbfSXrTXvnou/2ts7D86nxGHobXYQ21mko=; b=mBBLe5tsQD/4RL2pITvu+QxCvJlbZKbZP79gdeQfHql4LPdQMY9yF3isO0piXogrUY IwZ8JMKEQzXlRFt+w54yiDlrjcT/39ZaXv/MgVxPApxapV/z2oQiaClEfpdiZkqSLvqa MZuWCjAi3whpAEjB9pvp+E16f1zhAY22BwtGLECixMrfbkpaMmMTPWTWIxWpxNM1FtbV ZwFoaYzLzNRdsCYQJAnwnZC/3DFYSLdhBeFF8NPwkwmRJqtLmhxSRBZ5Ts88OPtTGFO8 zOiyXq4tNqZK3tzu+D5kusjlpdxBDv6LYvNhuyBppILmyQ/gxouTfO9MUfWfAbPvLR15 SazA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d199si438654oib.135.2020.02.10.09.30.35; Mon, 10 Feb 2020 09:30:47 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728135AbgBJR3k (ORCPT + 99 others); Mon, 10 Feb 2020 12:29:40 -0500 Received: from sauhun.de ([88.99.104.3]:44010 "EHLO pokefinder.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727967AbgBJR3d (ORCPT ); Mon, 10 Feb 2020 12:29:33 -0500 Received: from localhost (p54B33161.dip0.t-ipconnect.de [84.179.49.97]) by pokefinder.org (Postfix) with ESMTPSA id EEDB72C07F9; Mon, 10 Feb 2020 18:29:31 +0100 (CET) From: Wolfram Sang To: linux-i2c@vger.kernel.org Cc: Benjamin Tissoires , Phil Reid , Wolfram Sang , Wolfram Sang , linux-kernel@vger.kernel.org Subject: [PATCH 3/3] i2c: smbus: remove outdated references to irq level triggers Date: Mon, 10 Feb 2020 18:29:27 +0100 Message-Id: <20200210172929.6001-4-wsa+renesas@sang-engineering.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200210172929.6001-1-wsa+renesas@sang-engineering.com> References: <20200210172929.6001-1-wsa+renesas@sang-engineering.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org IRQ levels are now handled within the IRQ core. Remove the forgotten references from the documentation. Fixes: 9b9f2b8bc2ac ("i2c: i2c-smbus: Use threaded irq for smbalert") Signed-off-by: Wolfram Sang --- drivers/i2c/i2c-core-smbus.c | 5 ----- include/linux/i2c-smbus.h | 5 ----- 2 files changed, 10 deletions(-) diff --git a/drivers/i2c/i2c-core-smbus.c b/drivers/i2c/i2c-core-smbus.c index 5ab30d627b4d..d11a8ce2aa61 100644 --- a/drivers/i2c/i2c-core-smbus.c +++ b/drivers/i2c/i2c-core-smbus.c @@ -676,11 +676,6 @@ EXPORT_SYMBOL(i2c_smbus_read_i2c_block_data_or_emulated); * Handling can be done either through our IRQ handler, or by the * adapter (from its handler, periodic polling, or whatever). * - * NOTE that if we manage the IRQ, we *MUST* know if it's level or - * edge triggered in order to hand it to the workqueue correctly. - * If triggering the alert seems to wedge the system, you probably - * should have said it's level triggered. - * * This returns the ara client, which should be saved for later use with * i2c_handle_smbus_alert() and ultimately i2c_unregister_device(); or an * ERRPTR to indicate an error. diff --git a/include/linux/i2c-smbus.h b/include/linux/i2c-smbus.h index aa24a11d1a83..b89b91eb1c72 100644 --- a/include/linux/i2c-smbus.h +++ b/include/linux/i2c-smbus.h @@ -15,17 +15,12 @@ /** * i2c_smbus_alert_setup - platform data for the smbus_alert i2c client - * @alert_edge_triggered: whether the alert interrupt is edge (1) or level (0) - * triggered * @irq: IRQ number, if the smbus_alert driver should take care of interrupt * handling * * If irq is not specified, the smbus_alert driver doesn't take care of * interrupt handling. In that case it is up to the I2C bus driver to either * handle the interrupts or to poll for alerts. - * - * If irq is specified then it it crucial that alert_edge_triggered is - * properly set. */ struct i2c_smbus_alert_setup { int irq; -- 2.20.1