Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp1174072imj; Thu, 14 Feb 2019 02:24:59 -0800 (PST) X-Google-Smtp-Source: AHgI3IbT6LJOw8qzPMstEHHiZZ0jnasWosq5kpzZJ5RTW+gufancn7vCSqKlhAGCWQ93Pj440rpg X-Received: by 2002:a63:4b5e:: with SMTP id k30mr3022812pgl.212.1550139899497; Thu, 14 Feb 2019 02:24:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550139899; cv=none; d=google.com; s=arc-20160816; b=acgLxVVOj9brSG8+mH+KhMq0PatiXRWtlBl0VnC16nL4lus0HbFk5nhMrQFA8mFcB3 3yNEGivRoi7JO2T8vVR7UsIV4qKzrU1Dd4USO61WpT57Uq5vl7ky3Ua434/VUd3KGtLl DlT9HNgSGHhsDf+rdeTAT5K0/8zQDlEkN6a8zD79stS9uxJwB/yASzZU9qlLb63gDKQc JYXeWd9xiZo0tw1zlH/1zXJ8MJfJDb3+pdaxjGjw1e9V3fCt1ZnPhBDENL4c6whtEER2 rIrNtxbPyvHlKLHVINa/9LQ1f+MxmJfPGQMp2K9spcIo4PWOXBeikhvOTIJwv91kclB9 kSJw== 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=Ta0HkTvD5ejiomG/NTPjOFlXl2G6wcF9miAourKcRLg=; b=EXlFwUl5Vqs6uOX3VWIxSJ8TASc6G2x76N2+WvPtEITOk6fSRD/O3oQfEJpqWdfRTU D7F2OtaTP2HIORyhR+uxIZk8UOQOgjm3gdHc0gexQxRM6CMekdL55K7tMAUnZPe6gG9c mGXFPC0YXfeby9Lq4pM4qtB3fMIncgIXZrnKEvMidwFsEesyIY3GseBorvWNJjNLbXt3 qgF6sFpGwa78aNpx0fW+kzhteL6iziJWvWz5sb5Nqd64x9BZGa0jPeMuDZpaOIa9Q07d oipszJ+4YZx81F9pUCULIleNQWYd+Yvb/NDRCLe3Zwf5zsvlGonq5HW2tQ09hhFEBMyB usNg== 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 d64si1952486pgc.413.2019.02.14.02.24.42; Thu, 14 Feb 2019 02:24:59 -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 S2392261AbfBNByg (ORCPT + 99 others); Wed, 13 Feb 2019 20:54:36 -0500 Received: from mailgw02.mediatek.com ([1.203.163.81]:59308 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1728032AbfBNByg (ORCPT ); Wed, 13 Feb 2019 20:54:36 -0500 X-UUID: a376d6289f334b4193666d8d5b816656-20190214 X-UUID: a376d6289f334b4193666d8d5b816656-20190214 Received: from mtkcas32.mediatek.inc [(172.27.4.250)] by mailgw02.mediatek.com (envelope-from ) (mailgw01.mediatek.com ESMTP with TLS) with ESMTP id 559263774; Thu, 14 Feb 2019 09:54:30 +0800 Received: from MTKCAS36.mediatek.inc (172.27.4.186) by MTKMBS31N2.mediatek.inc (172.27.4.87) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 14 Feb 2019 09:54:29 +0800 Received: from [10.17.3.153] (10.17.3.153) by MTKCAS36.mediatek.inc (172.27.4.170) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Thu, 14 Feb 2019 09:54:28 +0800 Message-ID: <1550109268.30065.13.camel@mhfsdcap03> Subject: Re: [PATCH v3 5/6] dt-bindings: i2c: Add Mediatek MT8183 i2c binding From: Qii Wang To: Wolfram Sang CC: , , , , , , , , , Date: Thu, 14 Feb 2019 09:54:28 +0800 In-Reply-To: <20190205131641.GF12401@kunai> References: <1548057574-8061-1-git-send-email-qii.wang@mediatek.com> <1548057574-8061-6-git-send-email-qii.wang@mediatek.com> <20190205131641.GF12401@kunai> 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 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. 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.