Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp632513imu; Thu, 13 Dec 2018 01:33:54 -0800 (PST) X-Google-Smtp-Source: AFSGD/Unf4MraQtIZtqjBHOjjEZVPJVL8dXQqUSjOGv99yDKtf7YLlGA9vWtvFaUQWXf/ZH3mqfB X-Received: by 2002:a17:902:47aa:: with SMTP id r39mr22815664pld.219.1544693634670; Thu, 13 Dec 2018 01:33:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544693634; cv=none; d=google.com; s=arc-20160816; b=DW2ZPYVsdQnoYUUePIdIXUrlvScW+ZvPbHFcKo12gNUXIwF8Q9It88lA1PnPq9gXMQ DKfnv1ZehfelC3vrXfBCxEdnmB4eqsSzZdnNULEBvwKWdvtePoWbhc+xVfkHMwLUqBJH nOftTtnrNbC09BkvO7yg+rx1ArTXea1Qz6bQoG1ouQsOs2NSmh4/xTnGmvGQjka4jTLJ gynPi1S/Ff7upJj/h+aTPxU2tSIp6oLt5YWGmeQRs0hEBy3G34LzTncyUtZhN/ziEz+o bbAy31Q7EwVjh0BRv3IJlQGFmbu2gKsTrW1UG4ZaeIry/SSQX6W6Xpn1DxabTjeIZzgz Iguw== 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=9pZIVRgtGp3cMlZrkwjORBBMvCOKyqPiLZWR8S6Pd7Y=; b=CpHLleXjWnuu4kmSmT0yXVGVd0GK7rz61g6XLvBzWYZUhXJjueAfsi72IamH53Rfmg z5tuAByfUtD6TbrrRSgJasf+tJP0chU66eToYtY63Jqur6SNTEbQWTkWnw4i4bt3R1ZB XDJHDnd1pfA++JgU4Nu2LVauo9h3YuLsXOlqjNn/IyqB3Ous8OQAaOEr6H1/hKTF9m2k SjTdrhvEMsPpswTiTVn9nrSs0Ga0JgvIeB1W6DDErGD2kZ5vjH+DfkgMDrgWp3efk5Ro JWKZjvPFg4SO3iaqMmeYz6+fBMaN653BIg626PrS9zrW3n9cRtM5HdhhQAhk0nmP02O1 HdNA== 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 186si1000807pgi.424.2018.12.13.01.33.40; Thu, 13 Dec 2018 01:33:54 -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 S1727548AbeLMJcw (ORCPT + 99 others); Thu, 13 Dec 2018 04:32:52 -0500 Received: from Mailgw01.mediatek.com ([1.203.163.78]:48470 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726578AbeLMJcv (ORCPT ); Thu, 13 Dec 2018 04:32:51 -0500 X-UUID: 926697806b884b48a978688681d5b666-20181213 X-UUID: 926697806b884b48a978688681d5b666-20181213 Received: from mtkcas34.mediatek.inc [(172.27.4.250)] by mailgw01.mediatek.com (envelope-from ) (mailgw01.mediatek.com ESMTP with TLS) with ESMTP id 1351068479; Thu, 13 Dec 2018 17:32:29 +0800 Received: from MTKCAS36.mediatek.inc (172.27.4.186) by MTKMBS31DR.mediatek.inc (172.27.6.102) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 13 Dec 2018 17:32:27 +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, 13 Dec 2018 17:32:27 +0800 Message-ID: <1544693547.11699.40.camel@mhfsdcap03> Subject: Re: [PATCH 4/5] dt-bindings: i2c: Add Mediatek MT8183 i2c binding From: Qii Wang To: Wolfram Sang CC: , , , , , , , Date: Thu, 13 Dec 2018 17:32:27 +0800 In-Reply-To: <20181211202931.xav4gzi7rzh2scgx@ninjato> References: <1543843974-4054-1-git-send-email-qii.wang@mediatek.com> <1543843974-4054-5-git-send-email-qii.wang@mediatek.com> <20181211202931.xav4gzi7rzh2scgx@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 Tue, 2018-12-11 at 21:29 +0100, Wolfram Sang wrote: > > + - ch-offset: base reg offset for multi-user. > > What is "multi-user"? Why can't you add this offset to the reg-property > directly? > Thanks for your comment. There are 3 channel in one MT8183 I3C controller, and every channel can be used as an I2C controller. Take the following diagram as example: If use I3C channels as I2C bus, 1. CH-A/B/C offset are different; 2. If use CH-B or CH-A as I2C, they must config registers which's address are in CH-A. ____________________________________ | ________ | | | |<--- offset:0x00 | | | CH-A | | | |________| | | | |<--- offset:0x100 | | | CH-B | | | |________| | | | |<--- offset:0x200 | | | CH-C | | | |________| | |____________________________________| one I3C controller Because of CH-B/CH-C depend on CH-A's register, it can't add offset to reg-property directly. MT8183 doesn't need to support muti-user according to the latest project information, and I'll remove this feature from patches. > > + - mediatek,share-i3c: i3c controller can share i2c function. > > Please explain in more detail? Is this an I3C controller? > Yes, it is a i3c controller, and it is compatible with i2c. I only use the feature of i2c, so I need a flag to do some extra settings.