Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3202657pxk; Mon, 21 Sep 2020 07:46:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyyz08+ao/HEiXOLGAO2bMznXA7eZ0BTcRlWADYN6WSiO2QyxDAkQ2w9PLw0oEHAw4Jv7NA X-Received: by 2002:a17:906:f950:: with SMTP id ld16mr49074369ejb.489.1600699610485; Mon, 21 Sep 2020 07:46:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600699610; cv=none; d=google.com; s=arc-20160816; b=ddn8ovfSW9Aj5xSAKJMThB9jcy0gFnoUG1GEWaDGoe9mK88SauFvn0gX2Nsts4K1kr V4ecMs+0oJpc7UNLwdSW3qBOdL/6t35uKR5RINi7AZqnA2ddw5qGbosDcmDue8+VOaOz vm9LffNeNKSIwZRDf4k9AmX2dPeHHl9LhQLZ/XZwTuKDnn7velE7EDPpyBQaTYoxlK8e /oDV5xbTA5bpHWYdC1r/j27MaEXq5oTGbrIZzwXCHaGYh9bn3EMBxLvloQ61NzeZzf/6 A5sAmxVt1VucMPNjjWVq3F9EoL08/TPV+XJezAa+WCTEXdIMLPuUU7LOjUVxFNfuot7j fTUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=VBmGKsH4HXBysaC98/3xCnOtRsPHJTpyWV8wSKmKAjM=; b=1JyY2+T6C711+CRL4aw+pBnZ0hxVrbyHIwO//2VTI3ChAbo3WfOGEEVf5k56LGvpv7 gb3LbJChmQYVbKNdrzay0tN2pzA5Na9tKMRpOoD2exG02s2S6aZOgyNhBqyokJFkkQtb 9qs37ebK3ucih15kBD3PrzfXIKT4j1QthZu6eLHRP9pOzFNNc7Vv4GYJJg3ZCi+GeInk GNORlSiwnkYUaeDtL8mtRQhKuoqycVy6QNeUeA5/AxYI90nohkTxWPi48e8MulpifKuW iwOf3AxEaKCHPZT0hmbZ6zu4D66o/uwcHCAWh6zGvzVEi/+Ys2aoBF5n8t8S1Wzv5lr/ iYng== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=BFVZcoCX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id co28si8481769edb.562.2020.09.21.07.46.27; Mon, 21 Sep 2020 07:46:50 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=BFVZcoCX; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728321AbgIUOop (ORCPT + 99 others); Mon, 21 Sep 2020 10:44:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43800 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727965AbgIUOom (ORCPT ); Mon, 21 Sep 2020 10:44:42 -0400 Received: from mail-lf1-x141.google.com (mail-lf1-x141.google.com [IPv6:2a00:1450:4864:20::141]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E225BC061755; Mon, 21 Sep 2020 07:44:41 -0700 (PDT) Received: by mail-lf1-x141.google.com with SMTP id 77so6996365lfj.0; Mon, 21 Sep 2020 07:44:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=VBmGKsH4HXBysaC98/3xCnOtRsPHJTpyWV8wSKmKAjM=; b=BFVZcoCXkbqbquKK2sSGrqLtZKU9hzgIVQ2eHQpno/78sfx38zmfBEIhAH1oOuaatm lX7GOmadwj/QomMTDwgUyLyExg3FoHj9ReuFspSZ8IyUmt4YBN3NEMi+mScNFnEg8gtK 4i5re2ZtmX2gYb2MANPMa3upP1zoLp3CFzZI6PTnBuhH6DNKdeLs2f6e8/buiPyfMA/P 0Wof0+d7k2Gs33gLKi16XEihTtQa8nhfqQ5p3WBJjmYa9MwZeeqEsQyMhLuLvY8MHbHI V+EK2A+4HlnMfzeu7lygDLb7KCjca8QCFnR//FPG56cetY8StplXI7REZUHw3JQ2VlyD u4Sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=VBmGKsH4HXBysaC98/3xCnOtRsPHJTpyWV8wSKmKAjM=; b=dBd0idAccgsOt+tbUfbgWH3RekJ+ZDJ8/ERJQcFzwmCzmcudISwzjaZFSPS0UImJHO 4YPEeabfmDwezU607MGVXOTbdKetYen+yusw9+C8XT/L38VMHxqKisPJg+Wm9x9qGS0i xEpgaaY3O0FyvUMmUiOAVClHO/EHb9XdBXPZeWdwJ6JHyKbBrfNvu5awxclSczPceHuT PQ112Zmamqoa0lOBJauQTHeaHaYxFMMdZ+WiglFIrjfhGDyISrr5PNFQc+524g3osoZ7 sanqceddodN3nvIbDcNhodhmISp1zrXdf4/M6nA+dDQTf3gHaY5K702ZaGPoBIf7XUsh yK1Q== X-Gm-Message-State: AOAM532rGqWEWilRcEh7cdDx+UPU0Tz2trKrnfIQLOPpj/Q6zC7eYqph tyqMZg/dvQ0n1lqX5jFsfNXCqTa7H4A= X-Received: by 2002:ac2:593b:: with SMTP id v27mr116180lfi.338.1600699480014; Mon, 21 Sep 2020 07:44:40 -0700 (PDT) Received: from [192.168.2.145] (109-252-170-211.dynamic.spd-mgts.ru. [109.252.170.211]) by smtp.googlemail.com with ESMTPSA id x5sm2765162ljh.127.2020.09.21.07.44.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 21 Sep 2020 07:44:39 -0700 (PDT) Subject: Re: [PATCH v7 12/34] i2c: tegra: Use clk-bulk helpers To: Thierry Reding Cc: Jonathan Hunter , Laxman Dewangan , Wolfram Sang , =?UTF-8?B?TWljaGHFgiBNaXJvc8WCYXc=?= , Andy Shevchenko , linux-i2c@vger.kernel.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org References: <20200908224006.25636-1-digetx@gmail.com> <20200908224006.25636-13-digetx@gmail.com> <20200917113846.GX3515672@ulmo> <175e7f54-36f0-32c6-35a3-14c5b5e89e95@gmail.com> <20200921111257.GF3950626@ulmo> From: Dmitry Osipenko Message-ID: <7b3b9e21-f8c8-eebb-85bb-af62fc204f10@gmail.com> Date: Mon, 21 Sep 2020 17:44:38 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200921111257.GF3950626@ulmo> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 21.09.2020 14:12, Thierry Reding пишет: > On Thu, Sep 17, 2020 at 06:01:56PM +0300, Dmitry Osipenko wrote: > [...] >> It's still possible to add the clk-num checking, but it should be >> unpractical. We could always add it later on if there will be a real >> incident. Do you agree? > > There's also clk_bulk_get(), which allows you to specify the number of > clocks and their consumer IDs that you want to request. That seems like > it would allow us to both avoid the repetitive calls to clk APIs and at > the same time allows us to specify exactly which clocks we need. Would > that not work as a compromise? I'll change to use clk_bulk_get(), thanks.