Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp4592176imm; Mon, 25 Jun 2018 19:41:11 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJtrtxZor8Zf4QHC4XYsrM4CYqAvvnlsi7Cxi7OIPRQPVEwmZxzdLlsy6v++qyLEa+xs5Vq X-Received: by 2002:a65:6657:: with SMTP id z23-v6mr12960101pgv.257.1529980871831; Mon, 25 Jun 2018 19:41:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529980871; cv=none; d=google.com; s=arc-20160816; b=rjgSgxXGqQ+Z42IWKwUHKDEeAgSuaGT4LIlDeUVtUWyvb++GvxH9VXUg9e/6D6HQi4 V+VusKoWXZtpclfOB0o4HdrxIxzmOX5pKqXESLwqkaksxkRCo/FfOu5BP7eSg8M8WGye oNC62SybF++7KY7YCOHFZB8Y51PDQW5C86zL3zFTfAaBAFZzKfejhVMmfcZa5+SJ1Nzh 0F7wb8u58tBZOr9D0UUy5Aqk7El0+1rZS7UZsUocqouklIqhTY7HGaLez+eftiTkfvIe 1NCewFIIYUw8SItnYwQf604MXrcLvYSvhWxOmKN3ydSCCquELVLFUoGzrDKBNwL0iBki QbkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=fjV9Fwg1DxN5yysa4E0tn6omnab31MmwCLcxbEUBUcY=; b=CO0vGbTBSEclB8/FBbnHmN0dTiDCh51w6pR+SeWp7obrqpo8ABjt5tDHf/7rvju0nM LPbXaB1X1g/EzI3/6Fg+N3Aov1UXeIDvR855sX7pnSlH+r2hACjsOh++zFn0zlNhQpOr Pv6b30Mr/LMk82CXBUX4v//7yPOdj3Otb4dI2gSNefhPlu95xi3dzZXEFmFDezSRInsp YzO0wwQMi36r0E+q8Aib6BykgFtznf6yIN1AXlCV8PUCT+/EnW65rg/Kipqt3WYKw3Cr RklCJPLBKJ+x3/CsB2mGlxQFQDa+pHHWPla8sXS8FuNIvnca6njvTRH75Lq1I1hNjwBb iP4A== 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 az9-v6si496535plb.454.2018.06.25.19.40.57; Mon, 25 Jun 2018 19:41:11 -0700 (PDT) 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 S965347AbeFZCjq (ORCPT + 99 others); Mon, 25 Jun 2018 22:39:46 -0400 Received: from sauhun.de ([88.99.104.3]:48990 "EHLO pokefinder.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965281AbeFZCjo (ORCPT ); Mon, 25 Jun 2018 22:39:44 -0400 Received: from localhost (unknown [91.73.131.157]) by pokefinder.org (Postfix) with ESMTPSA id D9F8756A487; Tue, 26 Jun 2018 04:39:42 +0200 (CEST) Date: Tue, 26 Jun 2018 11:39:41 +0900 From: Wolfram Sang To: Eddie James Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org, benh@kernel.crashing.org, joel@jms.id.au, mark.rutland@arm.com, gregkh@linuxfoundation.org, rdunlap@infradead.org, andy.shevchenko@gmail.com, peda@axentia.se Subject: Re: [PATCH v10 0/7] i2c: Add FSI-attached I2C master algorithm Message-ID: <20180626023940.zn4zin6idrgcf2zx@ninjato> References: <1528918579-27602-1-git-send-email-eajames@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1528918579-27602-1-git-send-email-eajames@linux.vnet.ibm.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 13, 2018 at 02:36:12PM -0500, Eddie James wrote: > This series adds an algorithm for an I2C master physically located on an FSI > slave device. The I2C master has multiple ports, each of which may be connected > to an I2C slave. Access to the I2C master registers is achieved over FSI bus. > > Due to the multi-port nature of the I2C master, the driver instantiates a new > I2C adapter for each port connected to a slave. The connected ports should be > defined in the device tree under the I2C master device. Thanks for this series and your patience. While I can see why it also helps reviewing to send it as a series of multiple patches, I consider applying the driver itself as just one hunk. I am not decided on this yet. I have a few comments, especially about recovery. I replied to the relevant patches with more detail. Also, are you (or someone from your company) willing to maintain the driver? Then, an addition to MAINTAINERS would be much appreciated. Thanks, Wolfram