Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3440092yba; Tue, 23 Apr 2019 04:00:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqzV29JtGe531WwKXjePOvJv17oaDDGKH80u4lupaZPIYeMZr2ayz8PLUVT93i1Rdo81Zlwh X-Received: by 2002:a63:2ad3:: with SMTP id q202mr5775181pgq.423.1556017235623; Tue, 23 Apr 2019 04:00:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556017235; cv=none; d=google.com; s=arc-20160816; b=NTlMbuJ29SuMErEUOxsGFD9j5hUGHl1Hq8uo1XBVlt7diu0fp16A6vMhBUIyppsHR5 PWM5/kjtGv6ZHAwOSdYPN76RtEJFCjIG7FckxBAOehyxiT2MjrbfX+/Kzhjr6nnr0kQU 8eNVCx0amv2RF9K0m0UT/IzE4kMjQn7blI4vwKg0NSXS6JIcY2bHhqymcJUqwzdor40j jOBk1BYOWKI5+ZyYkkM18HZZG3P8UAjF0rqnAMCLOcrkIjUH2k2Cv+zbmkPuHJJddXOY NXXyMycyNT3ld7gPdxsVdxpTlx9bPfnjS2lqdU8gUaZn68W4w9KCsE+hV0s5s/J2lLHB 7Ukg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=pyg0HKgyKo4XumEcjZgMODxIIKRnavkBcxxGWvq5fdA=; b=w2E+hUqgPEs/ffATf2AFduU5R4XABSKoo4uW17B8HdoMNFKPLljOYH9aThvDuOG9ue O2WbSQ3uSkgwdUK1j9rBuVUYAGkUA0yibBV+tu1wBEeytaNiO4EBaeMZRXT+lAPqawzm zyldGrbYa2paMWKuSD8TCVsdPcx3QRi/bwxFfH3wTac01eBfvuVCBG6bitz1eZW54BBn IH7dW1trDaLI0IbQXPYGszoC/waRumXTXUYWwWuOrouvHZTx0pZJBVczINJkdFCDinaz UuTuHF4BYHLbynxj/kJ9/cPYD7hZC96YISNBZCGCaolWT4SLrGUnyHZIYrK92fj282ke ONDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=JxySI2ff; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t16si262275pgl.97.2019.04.23.04.00.18; Tue, 23 Apr 2019 04:00:35 -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; dkim=pass header.i=@linaro.org header.s=google header.b=JxySI2ff; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727314AbfDWK70 (ORCPT + 99 others); Tue, 23 Apr 2019 06:59:26 -0400 Received: from mail-lj1-f195.google.com ([209.85.208.195]:39902 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726150AbfDWK70 (ORCPT ); Tue, 23 Apr 2019 06:59:26 -0400 Received: by mail-lj1-f195.google.com with SMTP id l7so13092530ljg.6 for ; Tue, 23 Apr 2019 03:59:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pyg0HKgyKo4XumEcjZgMODxIIKRnavkBcxxGWvq5fdA=; b=JxySI2ffapiw6sTeEqlBimIoD0M/JGNUoiMyA2e03Hs1PMRejveZJbwLoWZun7K1FK gPnfFJOusjAT9nUe4kjgupR8k4FokiwNufbA0OItZJwZmwSvwsxrtOXJ4Zsa0OIx407T kVikTCBj8e2FjeHIbhutQFA0UOFamvO2E1MLhm0kRYwd7FwGFibWwlNNQFuY9JnQCVaZ ggIo9Z2mum0vCptoLqCtNfsVo0tvFa4os4A5eMspniPNVWC8uZlXRXb0qQcOGbtpM7+6 Zc+2u9vjxke52USN/PuVq4N4vR9B/7f18t4LHKXKMLyOo/JM6VvM+T5kr9SBL+CQHqT7 yaBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pyg0HKgyKo4XumEcjZgMODxIIKRnavkBcxxGWvq5fdA=; b=sMS2ruhHpemnH0kvgBYfF1UmGgOPukMJ2B0XYV4uvbiMUiGcIOKesIVtTdpzKtq5Nv mQI/7x18ZIMIi8Qb85UNKbKUJyH7AkoSWRwztDIv5jtwMarG9cwH4Ol2FESkT8WZqTYW +65sfzMuembrt9MW8MtKGJQKW293isxvJGhGp58LagWqe0sJq2hdjH+i069SzWgXkxBm //IGauuD9ehxedQpCWo5cGklfX0i6jzodHc9llH6DOC/MA+2iAYJXi2cN2l2HmQtEo8K 7AtfkTffhLHfRg7thcYTMdrU6KhrMi34MsIHe8Tns0ZrlkJ/qmGFsZUSGJJm1KPfGXAp XdcA== X-Gm-Message-State: APjAAAXuutRFrloi+BHfr0yLfk2utl3+ZWNiJYrFonimuEaibbXO18/C KGXrJJj1c88L/WO9urnpZPQnf4JMX0CJH1q9pZKVXA== X-Received: by 2002:a2e:834d:: with SMTP id l13mr13688335ljh.97.1556017164724; Tue, 23 Apr 2019 03:59:24 -0700 (PDT) MIME-Version: 1.0 References: <20190325124137.6117-1-zhiyong.tao@mediatek.com> <20190325124137.6117-5-zhiyong.tao@mediatek.com> <206361ee-b238-4017-83fe-702ea59ae9c5@gmail.com> In-Reply-To: <206361ee-b238-4017-83fe-702ea59ae9c5@gmail.com> From: Linus Walleij Date: Tue, 23 Apr 2019 12:59:13 +0200 Message-ID: Subject: Re: [PATCH RESEND v3 4/4] pinctrl: add drive for I2C related pins on MT8183 To: Matthias Brugger Cc: Zhiyong Tao , Rob Herring , Mark Rutland , Sean Wang , srv_heupstream@mediatek.com, hui.liu@mediatek.com, huang eddie , chuanjia.liu@mediatek.com, Biao Huang , Hongzhou Yang , Erin Lo , Sean Wang , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , Linux ARM , "moderated list:ARM/Mediatek SoC support" , "open list:GPIO SUBSYSTEM" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 16, 2019 at 10:08 AM Matthias Brugger wrote: > On 25/03/2019 13:41, Zhiyong Tao wrote: > > This patch provides the advanced drive for I2C used pins on MT8183. > > The detail strength specification description of the I2C pin: > > When E1=0/E0=0, the strength is 0.125mA. > > When E1=0/E0=1, the strength is 0.25mA. > > When E1=1/E0=0, the strength is 0.5mA. > > When E1=1/E0=1, the strength is 1mA. > > For I2C pins, there are existing generic driving setup and the above > > specific driving setup. I2C pins can only support 2/4/6/8/10/12/14/16mA > > driving adjustment in generic driving setup. But in specific driving > > setup, they can support 0.125/0.25/0.5/1mA adjustment. > > If we enable specific driving setup for I2C pins, > > the existing generic driving setup will be disabled. > > For some special features, we need the I2C pins specific driving setup. > > The specific driving setup is controlled by E1E0EN. > > So we need add extra vendor driving preperty instead of the generic > > driving property. We can add "mediatek,drive-strength-adv = ;" > > to describe the specific driving setup property. > > "XXX" means the value of E1E0EN. So the valid arguments of > > "mediatek,drive-strength-adv" are from 0 to 7. > > > > Signed-off-by: Zhiyong Tao > > --- > > drivers/pinctrl/mediatek/pinctrl-mt8183.c | 50 ++++++++++++++++++++++++ > > drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 47 ++++++++++++++++++++++ > > drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.h | 11 ++++++ > > drivers/pinctrl/mediatek/pinctrl-paris.c | 12 ++++++ > > 4 files changed, 120 insertions(+) > > > > Linus, did that fall through the cracks? Do you have any comments on this driver? It's applied AFAICT. Maybe I forgot to push the branch, but its there. Please confirm so I didn't miss anything! Linus Walleij