From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9F150C433FE for ; Fri, 11 Feb 2022 19:47:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1352967AbiBKTrG (ORCPT ); Fri, 11 Feb 2022 14:47:06 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:57800 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348914AbiBKTrF (ORCPT ); Fri, 11 Feb 2022 14:47:05 -0500 Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3D6DF13A for ; Fri, 11 Feb 2022 11:47:04 -0800 (PST) Received: by mail-lf1-x135.google.com with SMTP id k13so18529713lfg.9 for ; Fri, 11 Feb 2022 11:47:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=wlk9TNYVCMph61ewMNIOja5bBaQXf36U4fYvmtONX+s=; b=erzjDC8HdhKkcESrt6GaJK5DCgdNcuVGJ/RhXe53huFkT7eDuRGXpjtPbgkTEsAYZS 6byctj6XeVjjK17pOOeahYbFMgpjTz74V8ONndInduGW0izI931LiQTDKE/7hy60g/Lj 6Ch02JY8yPmSQT4K1nX4bgiqr1zvKYg5kZgOqrxjVqu2CSw0dpJV3XtRFSR6KuzEs63E T+V0pkYOov744TzjcZKWxA+84i9ofDVd99kKlBsyQBT7qfR1itkx26IWXvNT9d2hL3+n WB/J2xQawKrPt4Jz4qD+VlBqdEALvS9d2LJxMZTJ/d51fgSVfB2SXMRfFG9wuG/AfvrJ PW9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=wlk9TNYVCMph61ewMNIOja5bBaQXf36U4fYvmtONX+s=; b=b+0EhWZmZ9fJSCMkbglKvnRtuhvDuiPZE1g+DgfFpVCWv2SYFu/4E1dovDVVDiC/bq eHGgP288J9Sto1K0XVDFJXY7ClmbrDqAh2YDakdapcFw+5MJmBsdRXdUxf61cMgGfcGh YEJPUDlW2rHIE2P3SR8NdzqMFo46wRsKw3cOGJHZCcI3Mb8gVyY3jChNISvjLc0xdaXB HbAuiGjdMftjtD5PpnZyp49KYrBEuuexSK8j/oXmMCtXNtFMCIIQICYpajgkwyhpwjyE eABX4QWzGCLxen7C0SFeX8Z2DvoPt9KnYgbLElWvdSHCPo2gwaydFCDz9CZt7Z4HX3ZJ Q7Dw== X-Gm-Message-State: AOAM5308NspuQ83n0SSGBSQXk0HJdCLJjoevMCLep7okcfOdJKuQWA3D KgD5TTaYBDwV3YqvhBqnMBL/4bBI+rh7mGl1 X-Google-Smtp-Source: ABdhPJzqoBMA+QIOiEPvnR09WPKnrncnY5ngE4lRCI6j++aI6QzP6sjWQIhKmmoS9UKcAgSnvTeuKA== X-Received: by 2002:a05:6512:3e1c:: with SMTP id i28mr2170671lfv.83.1644608822600; Fri, 11 Feb 2022 11:47:02 -0800 (PST) Received: from [192.168.1.102] (88-113-46-102.elisa-laajakaista.fi. [88.113.46.102]) by smtp.gmail.com with ESMTPSA id k1sm367352lfo.295.2022.02.11.11.47.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Feb 2022 11:47:02 -0800 (PST) Subject: Re: [PATCH 0/9] i2c: qcom-cci: fixes and updates To: Wolfram Sang References: <20220203164629.1711958-1-vladimir.zapolskiy@linaro.org> Cc: Loic Poulain , Rob Herring , Robert Foss , linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org, devicetree@vger.kernel.org From: Vladimir Zapolskiy Message-ID: Date: Fri, 11 Feb 2022 21:46:36 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hi Wolfram, On 2/11/22 7:49 PM, Wolfram Sang wrote: > Hi, > >> The new bus adapter specific bus_regulator from commit 5a7b95fb993e >> ("i2c: core: support bus regulator controlling in adapter") is reused, > > Reusing is nice, of course, but I hope you noticed that I needed to > revert this feature: > > a19f75de73c2 ("Revert "i2c: core: support bus regulator controlling in adapter"") yes, I've seen it, and as far as I understand it's expected to get it back after the regression fixes. > The thread to get it re-applied is currently here: > > https://lore.kernel.org/all/20220106122452.18719-1-wsa@kernel.org/ > A presented change in the series is I2C controller specific, so it works well on top of the reverted feature, however it has a potential to be simplified after the re-application. Wolfram, can you please share your opinion on device tree binding name and placement for an SDA/SDC pull-up controlled by a regulator? See https://lore.kernel.org/all/682b7ffe-e162-bcf7-3c07-36b3a39c25ab@linaro.org Thank you in advance. -- Best wishes, Vladimir