From patchwork Fri Oct 5 15:36:32 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dmitry Osipenko X-Patchwork-Id: 979537 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="NVu2GOkO"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 42RYnw4nPrz9s3T for ; Sat, 6 Oct 2018 01:39:00 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729104AbeJEWhP (ORCPT ); Fri, 5 Oct 2018 18:37:15 -0400 Received: from mail-lj1-f196.google.com ([209.85.208.196]:33440 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729069AbeJEWhP (ORCPT ); Fri, 5 Oct 2018 18:37:15 -0400 Received: by mail-lj1-f196.google.com with SMTP id z21-v6so12009559ljz.0; Fri, 05 Oct 2018 08:38:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=wO8rLezgv03Kc1/H2qOEeUj33zOmxhncF8Ftb8pScZc=; b=NVu2GOkOfb7iY0EvP908xRb2fPjxVvHVVrFXH2aGx8QW2B9pa/wpRJkbwppKvI/znd OWxovxOmmnH7ueeeqMlAB+qWYlulB1h3j8RnSN6ZUcBRbfLGhlk1ZkTGIwRvRaxlPmqp iXbbPCm7uiwqypcMbcz3x396fisS9bsMTrkAtE2B9v7PKvAPZGcYYNlsleiLcKmadKeT rN7aPtpDY06PIpQqmyQTiokHNuQYF1+BDxYLIRsQFKnMXHRgp8K2kWx3KfY2e8V4WT0I T7VQFDtdxmlb5s9j9is/KlSDphjb+x+zgzPinHMJOSjB12iH7k6XcR6B3YCQo5zkRKdV ythQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=wO8rLezgv03Kc1/H2qOEeUj33zOmxhncF8Ftb8pScZc=; b=qXkTbhJ3R/BOaZT2Iw8lyEyQ2tJuk3LXmhc2apLiaafmZHyLNZEbMoxDTJb7uEESnp i9gQjB0v/sxqPSmC4pv7clSffSPYTFGr4fg6mSJuaLJ+qTOiyvMZc9tFbPYLQOBy93eK vwYTZWBSDSvg2z8EpT6D/kk53ROk2/KhkyZOfq3bMlhC1rT+jbEex7pBX/PwK0lONNQC JICvdJQCfD1O5xJ15eAY5bsVAA0ZoUjyloXqAqWqy6ab2jJfnP5OoUSO4ZFatDuhgkRZ SCfcdnICLztpbKgnynaVJ0hlAm5OOL4ZEAqximqrwdVeAQGwDYNZRd5Pcf1JdT3RN04v ojRA== X-Gm-Message-State: ABuFfojnJ0dvSwxanYfnCy/K4+fz6RNRwRsnYpNqJJTXNIbEzqZXKi5S XnA7WwUDgjtwqM51VXeHqyk= X-Google-Smtp-Source: ACcGV61tzkAcoe5zkUcESDoYnBzR66PilWuiQizktu3bVLN9FaRF7z0P7b5HSc3thKSnAZE5d0omWg== X-Received: by 2002:a2e:2205:: with SMTP id i5-v6mr6737163lji.15.1538753879137; Fri, 05 Oct 2018 08:37:59 -0700 (PDT) Received: from localhost.localdomain (109-252-91-213.nat.spd-mgts.ru. [109.252.91.213]) by smtp.gmail.com with ESMTPSA id w22-v6sm1879373lfd.72.2018.10.05.08.37.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Oct 2018 08:37:58 -0700 (PDT) From: Dmitry Osipenko To: Mark Brown , Rob Herring , Maciej Purski Cc: Thierry Reding , Jonathan Hunter , Peter De Schrijver , Lucas Stach , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, linux-omap@vger.kernel.org Subject: [PATCH v1 05/11] dt-bindings: regulator: Change regulator-coupled-max-spread property Date: Fri, 5 Oct 2018 18:36:32 +0300 Message-Id: <20181005153638.1886-6-digetx@gmail.com> X-Mailer: git-send-email 2.19.0 In-Reply-To: <20181005153638.1886-1-digetx@gmail.com> References: <20181005153638.1886-1-digetx@gmail.com> MIME-Version: 1.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Redefine binding for regulator-coupled-max-spread property in a way that max-spread values are defined per regulator couple instead of defining single max-spread for the whole group of coupled regulators. With that change the following regulators coupling configuration will be possible: regA: regulatorA { regulator-coupled-with = <®B ®C>; regulator-coupled-max-spread = <100000 300000>; }; regB: regulatorB { regulator-coupled-with = <®A ®C>; regulator-coupled-max-spread = <100000 200000>; }; regC: regulatorC { regulator-coupled-with = <®A ®B>; regulator-coupled-max-spread = <300000 200000>; }; Signed-off-by: Dmitry Osipenko Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/regulator/regulator.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt index a7cd36877bfe..9b525b657fca 100644 --- a/Documentation/devicetree/bindings/regulator/regulator.txt +++ b/Documentation/devicetree/bindings/regulator/regulator.txt @@ -76,8 +76,9 @@ Optional properties: - regulator-coupled-with: Regulators with which the regulator is coupled. The linkage is 2-way - all coupled regulators should be linked with each other. A regulator should not be coupled with its supplier. -- regulator-coupled-max-spread: Max spread between voltages of coupled regulators - in microvolts. +- regulator-coupled-max-spread: Array of maximum spread between voltages of + coupled regulators in microvolts, each value in the array relates to the + corresponding couple specified by the regulator-coupled-with property. Deprecated properties: - regulator-compatible: If a regulator chip contains multiple From patchwork Fri Oct 5 15:36:34 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dmitry Osipenko X-Patchwork-Id: 979533 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="GSrZroaU"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 42RYnc00mzz9s8J for ; Sat, 6 Oct 2018 01:38:43 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728003AbeJEWhu (ORCPT ); Fri, 5 Oct 2018 18:37:50 -0400 Received: from mail-lf1-f68.google.com ([209.85.167.68]:46730 "EHLO mail-lf1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728562AbeJEWhR (ORCPT ); Fri, 5 Oct 2018 18:37:17 -0400 Received: by mail-lf1-f68.google.com with SMTP id z144-v6so1149790lff.13; Fri, 05 Oct 2018 08:38:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=QEkMidX6FxpiZSTFa8KISKNbf0++dhdesLBYR/Rbies=; b=GSrZroaUf5AOHNuqOF41WdXLoyG59HDiX2qeyBcCVtJ71aNkPPezwfR8PcsYKG1AE5 urobSipTdm3rq6y9HjnpqGzV0zNl491rhaO4AD0pol97TJHm1f+QV+hyjyElaLedE1BH gkUaOAXpoAx1QKnMX2/bKDwlsiZe6vWFj9LjMg9cvVI80KICQw3DdejkYuWRHImYLHrc sPjsZ2lZJEaqFCVVt0bsZUqB54obIUgbKi8Dmn9bdcuXDu60Z1iDgqGihjiOHRXLLgFK 9EvPF+IMJ6UN2yxbVpMqQIDlYn8UT8dHLf1YAj4B3/v73C0p2g3VoS6vo5TI9UL35IFP 8P6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=QEkMidX6FxpiZSTFa8KISKNbf0++dhdesLBYR/Rbies=; b=oabazvVLKN4edEMmmH3MLFWuZy4Ews3cuyWMn4cRDtm/G+lFO3ay+p3c48RO31/tUH mAJV5vQB+h0hBHEkQiksGyj3/kuxtepYe/9Q7lM90jNISuwOQq9F5SxOrjUL4F3r6x9F asTHB/U3EKgkFiRDyJLL+8Y9cOMfzm41OPweGsy7Y618mdGQeXlpZZm55KuOR/u/FHme XL9m8oW12zeqwslguB5ROgpA3UkT+zVkXdhNOfu1oou5yHSlh8O33BWquNOzyReiapZ1 Lx+cAvHLbWm2XJUxyX8AJ5POC9Vv8Tdeh8Z2NFYOLYMK4qKulEuS4qUo/CMqJg58KEtq TkAA== X-Gm-Message-State: ABuFfoiF6G9AQaT6Ic8hbKFnyg+N5WU5MfzfpYnCZNlDaZoPjuICnXlt s7u00mk6SKa57cPnSNM1fl8= X-Google-Smtp-Source: ACcGV60sUESNjMBioepOaWBIT4jaCs+E/WyNbSCiW4Lg1PT8d7swZtjtBtQiH67UlcQRa3tArGEZLQ== X-Received: by 2002:a19:c650:: with SMTP id w77-v6mr7448587lff.108.1538753881679; Fri, 05 Oct 2018 08:38:01 -0700 (PDT) Received: from localhost.localdomain (109-252-91-213.nat.spd-mgts.ru. [109.252.91.213]) by smtp.gmail.com with ESMTPSA id w22-v6sm1879373lfd.72.2018.10.05.08.38.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 Oct 2018 08:38:01 -0700 (PDT) From: Dmitry Osipenko To: Mark Brown , Rob Herring , Maciej Purski Cc: Thierry Reding , Jonathan Hunter , Peter De Schrijver , Lucas Stach , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, linux-omap@vger.kernel.org Subject: [PATCH v1 07/11] dt-bindings: regulator: Document new regulator-max-step-microvolt property Date: Fri, 5 Oct 2018 18:36:34 +0300 Message-Id: <20181005153638.1886-8-digetx@gmail.com> X-Mailer: git-send-email 2.19.0 In-Reply-To: <20181005153638.1886-1-digetx@gmail.com> References: <20181005153638.1886-1-digetx@gmail.com> MIME-Version: 1.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Certain hardware may require supply voltage to be changed in steps. Define new property that allow to describe such hardware. Signed-off-by: Dmitry Osipenko Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/regulator/regulator.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/regulator/regulator.txt b/Documentation/devicetree/bindings/regulator/regulator.txt index 9b525b657fca..0c3a243c95df 100644 --- a/Documentation/devicetree/bindings/regulator/regulator.txt +++ b/Documentation/devicetree/bindings/regulator/regulator.txt @@ -79,6 +79,8 @@ Optional properties: - regulator-coupled-max-spread: Array of maximum spread between voltages of coupled regulators in microvolts, each value in the array relates to the corresponding couple specified by the regulator-coupled-with property. +- regulator-max-step-microvolt: Maximum difference between current and target + voltages that can be changed safely in a single step. Deprecated properties: - regulator-compatible: If a regulator chip contains multiple