Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp503157imj; Sat, 16 Feb 2019 05:15:43 -0800 (PST) X-Google-Smtp-Source: AHgI3IYPqhSV9J3u7tDYvNAbhWNOyn4g9mNfilefeGfmTgbLZ39GIMOxCPLwoSizmdKz6V545yjt X-Received: by 2002:a62:b248:: with SMTP id x69mr14698595pfe.256.1550322943616; Sat, 16 Feb 2019 05:15:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550322943; cv=none; d=google.com; s=arc-20160816; b=Cv2kq3G468OHZdkwPAVonWojGffG+mPtBEk/1IXd6Pr93aJq1VBob+R89Nud/nFYMz UxkUeRTqpTY4IUCI2bZ3H7PlNBkhGkLUqKzSDQw+UqmVKfLblwaNSWFnNWqH5ReLFaSu 6ZIMBM0ec01EEiVVKZNccWv9tK3TExLd3e1OuDq2RE7Ss70aCuQ4vZlyWkaKp8pGnDj5 mwcekQ1XEJ7fJHcFOdVojWBTiNeA2zSm2IG4HaA6syuHM1OkzEcA0K6w24votWM2kcvC klloPbUZZsSEUgzMJvHhSEK0o37rcg6Uz1UH+5Z1jdJylw884kcKQ8a2I3h1XgEJRNh2 QB9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id; bh=GP2JGsMTYRdh7SZVB1HiSRIIyopekGB2kMiZIoBT3fI=; b=MoZif+CgH3xRixY42vbSDbrjN9+JL6Mv4aobpHm1HX7W0ggdkhfwBEwOKtPr15Xk/b wxR9avmv7pN8DkjX6qQ9a6LdQ4wn9S19AOwo6Rtj8vwIqwrKxDun5Rk5TSDRSY86WQai z6hDNuF3LA6lf6RCjRBsTeAbsaSf+HScETo6PC0c0yDhbz3Ysm/fX9AHbypKCjCVp/DF yp1hYpnEJnkMvz3C8ZDvqR2GOMQYOGUYb2V1oq0cKzGTWzpXKeja12NFo8lQRRWvCpjf M0ZOQkw5WLAjkJrFRtF5vqBil7QnVfjnFH65l4jbRGd2zB5jcW8M0ptnRkCmaWy/LD4F hV4Q== 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 m21si8572478pls.324.2019.02.16.05.15.27; Sat, 16 Feb 2019 05:15:43 -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 S1726993AbfBPLcT (ORCPT + 99 others); Sat, 16 Feb 2019 06:32:19 -0500 Received: from Mailgw01.mediatek.com ([1.203.163.78]:27245 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726150AbfBPLcT (ORCPT ); Sat, 16 Feb 2019 06:32:19 -0500 X-UUID: 28b42441216a494489c2a4836339c4e9-20190216 X-UUID: 28b42441216a494489c2a4836339c4e9-20190216 Received: from mtkcas34.mediatek.inc [(172.27.4.250)] by mailgw01.mediatek.com (envelope-from ) (mailgw01.mediatek.com ESMTP with TLS) with ESMTP id 1313132266; Sat, 16 Feb 2019 19:32:05 +0800 Received: from MTKCAS32.mediatek.inc (172.27.4.184) by MTKMBS31DR.mediatek.inc (172.27.6.102) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sat, 16 Feb 2019 19:32:04 +0800 Received: from [10.17.3.153] (10.17.3.153) by MTKCAS32.mediatek.inc (172.27.4.170) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Sat, 16 Feb 2019 19:32:03 +0800 Message-ID: <1550316723.30065.44.camel@mhfsdcap03> Subject: Re: [PATCH v3 5/6] dt-bindings: i2c: Add Mediatek MT8183 i2c binding From: Qii Wang To: Wolfram Sang CC: , , , , , , , , , , Rob Herring Date: Sat, 16 Feb 2019 19:32:03 +0800 In-Reply-To: <20190215090257.geumssb2cucs7rzt@ninjato> References: <1548057574-8061-1-git-send-email-qii.wang@mediatek.com> <1548057574-8061-6-git-send-email-qii.wang@mediatek.com> <20190205131641.GF12401@kunai> <1550109268.30065.13.camel@mhfsdcap03> <20190215090257.geumssb2cucs7rzt@ninjato> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2019-02-15 at 10:02 +0100, Wolfram Sang wrote: > On Thu, Feb 14, 2019 at 09:54:28AM +0800, Qii Wang wrote: > > On Tue, 2019-02-05 at 14:16 +0100, Wolfram Sang wrote: > > > > + - mediatek,share-i3c: i3c controller can share i2c function. > > > > > > I am not happy with this binding. There must be a better way of using > > > the I3C controller in I2C mode. I think it would be easier to tell if we > > > had an I3C driver to see how it implements I2C fallback there. Is the > > > I3C driver on the way? > > > > > > > I am very sorry for the late reply due to the Chinese New Year holiday. > > No worries. I hope you enjoyed the holidays! > > > After confirmation, for I2C mode in I3C controller, we will push an I3C > > driver to implement I2C fallback there later, and we will remove > > "mediatek,share-i3c" for i2c controller driver in the next patch. > > The problem with DT bindings is that you need to support them forever > once you introduced them. Because there might be old device trees on > boards out there which need the property. So, I don't like the idea of > having a temporary binding which is meant to be removed anyway. My take > is that you should just send out the I3C driver which will handle the > I2C support then. > > Adding Rob to CC in case he has a different opinion. > Maybe you think that MT8183 SoC only has the I3C controllers. Actually, there are I2C and I3C controllers on MT8183 SoC. We will remove "mediatek,share-i3c" for I2C controller driver, so these patches are just to support the I2C controllers on MT8183 SoC. For the I3C controller we will send some new patches which are based on i3c framework directories(kernel/drivers/i3c), not based on i2c-mt65xx.c.