[{"id":1766148,"web_url":"http://patchwork.ozlabs.org/comment/1766148/","msgid":"<20170911090930.p5horsgf4atqtlhs@pengutronix.de>","list_archive_url":null,"date":"2017-09-11T09:09:30","subject":"Re: [PATCH v2] i2c: imx: allow i2c devices share an interrupt","submitter":{"id":1476,"url":"http://patchwork.ozlabs.org/api/people/1476/","name":"Uwe Kleine-König","email":"u.kleine-koenig@pengutronix.de"},"content":"Hello,\n\nOn Mon, Sep 11, 2017 at 04:34:16PM +0800, ying.zhang22455@nxp.com wrote:\n> From: Zhang Ying-22455 \n> \n> Allow the I2C device on the same bus can’t claim irq.\n\nI don't understand the motivation for this change. Is there an\nimx-platform that doesn't have a dedicated irq for i2c? The commit log\nsuggests there is an i2c device with the same irq. What is meant here, a\nbus device or the imx operating in slave mode?\n\nBest regards\nUwe","headers":{"Return-Path":"","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@bilbo.ozlabs.org","Authentication-Results":"ozlabs.org;\n\tspf=none (mailfrom) smtp.mailfrom=vger.kernel.org\n\t(client-ip=209.132.180.67; helo=vger.kernel.org;\n\tenvelope-from=linux-i2c-owner@vger.kernel.org;\n\treceiver=)","Received":["from vger.kernel.org (vger.kernel.org [209.132.180.67])\n\tby ozlabs.org (Postfix) with ESMTP id 3xrMZ62Bj1z9rxm\n\tfor ;\n\tMon, 11 Sep 2017 19:09:34 +1000 (AEST)","(majordomo@vger.kernel.org) by vger.kernel.org via listexpand\n\tid S1751071AbdIKJJc (ORCPT );\n\tMon, 11 Sep 2017 05:09:32 -0400","from metis.ext.4.pengutronix.de ([92.198.50.35]:51007 \"EHLO\n\tmetis.ext.4.pengutronix.de\" rhost-flags-OK-OK-OK-OK)\n\tby vger.kernel.org with ESMTP id S1751013AbdIKJJc (ORCPT\n\t); Mon, 11 Sep 2017 05:09:32 -0400","from [2001:67c:670:100:5054:ff:fe2a:3aa]\n\t(helo=pty.hi.pengutronix.de)\n\tby metis.ext.pengutronix.de with esmtps\n\t(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2)\n\t(envelope-from )\n\tid 1drKig-0003i4-UT; Mon, 11 Sep 2017 11:09:30 +0200","from ukl by pty.hi.pengutronix.de with local (Exim 4.89)\n\t(envelope-from )\n\tid 1drKig-0006iZ-9g; Mon, 11 Sep 2017 11:09:30 +0200"],"Date":"Mon, 11 Sep 2017 11:09:30 +0200","From":"Uwe =?iso-8859-1?q?Kleine-K=F6nig?= ","To":"ying.zhang22455@nxp.com","Cc":"linux-i2c@vger.kernel.org","Subject":"Re: [PATCH v2] i2c: imx: allow i2c devices share an interrupt","Message-ID":"<20170911090930.p5horsgf4atqtlhs@pengutronix.de>","References":"<20170911083416.2895-1-ying.zhang22455@nxp.com>","MIME-Version":"1.0","Content-Type":"text/plain; charset=utf-8","Content-Disposition":"inline","Content-Transfer-Encoding":"8bit","In-Reply-To":"<20170911083416.2895-1-ying.zhang22455@nxp.com>","User-Agent":"NeoMutt/20170113 (1.7.2)","X-SA-Exim-Connect-IP":"2001:67c:670:100:5054:ff:fe2a:3aa","X-SA-Exim-Mail-From":"ukl@pengutronix.de","X-SA-Exim-Scanned":"No (on metis.ext.pengutronix.de);\n\tSAEximRunCond expanded to false","X-PTX-Original-Recipient":"linux-i2c@vger.kernel.org","Sender":"linux-i2c-owner@vger.kernel.org","Precedence":"bulk","List-ID":"","X-Mailing-List":"linux-i2c@vger.kernel.org"}}]