Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp4565051imm; Wed, 30 May 2018 07:56:52 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJWIj6orrVnuWFhb0P0ww5VHo8OyEZe+l9q3capfknrhK+CFN4Xrr88N7O1VH8XA0PHv/ax X-Received: by 2002:a62:d905:: with SMTP id s5-v6mr3145337pfg.20.1527692212365; Wed, 30 May 2018 07:56:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527692212; cv=none; d=google.com; s=arc-20160816; b=tgusidvgHJls38TXG1WCqpDZbdj2wjFFkwN+4Nlu0M2yubqDgUMuzAqEE1g8mejWRM 0HGnIgDvZ/5KKg4x30oCC4XUE1Cle7ervCHvp5Ezt97k/HfBMB9A4dVLhLf5v7TNYa8A gifoOpRRyzSWP9U5AwXvTJCwtXdqplDJq7wzS8PZWulZOVHmhNCotaSTo9v+sEbIEMak eu8ryiWOaRi2KAgzrHxFK63gHX9GsPoVUMBoUQra6cs36dAhSPsR7i/YLi5XxLmu4+P3 0hCGnRORNf6jYmRr9KlXWw/Seq7sre+CPUQlfuCJnGsijWMGZImK5Owfimk2QyLSS+hm 6wOg== 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 :references:in-reply-to:mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=mo0U8UYZTFs8Yfj4kYZIYA3C83yQjpZrmz2WeOnCk8s=; b=b5BFbJ3kG7NfpuUJsewWqqk9urMeHy0ySFMtpFouqedWXJOLytw4DN0/95uaoyUJje 8T9GlCaJh65qgxDKhzQuMz3DphIFuoo/8IOvWK0h0eC5g55bsJVDLtq5vBm82TDALyMP qDNqnHl8zBIZFyb4YMx1Xw5uyryR9YokiBX4qIYuiqhBe8cMNU3ftfjyILoU7CQTiLi/ md6BzlONu6wqQsiAz+SAYdHHw69PYDGisZBTUC+WxcPIYsZORMjOQtYgx9SBFfqnJyIn qFex8qmxYwQnzM4Mo0kgZgOt6DKQX1xBKchkdsrp2gePlfUlHNmFc+2W/NPlTPLTUVTa wB2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@google.com header.s=20161025 header.b=thjqUxov; dkim=fail header.i=@chromium.org header.s=google header.b=Bz5gF19G; 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=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p7-v6si27022506pgd.96.2018.05.30.07.56.37; Wed, 30 May 2018 07:56:52 -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=fail header.i=@google.com header.s=20161025 header.b=thjqUxov; dkim=fail header.i=@chromium.org header.s=google header.b=Bz5gF19G; 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=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753429AbeE3Oyx (ORCPT + 99 others); Wed, 30 May 2018 10:54:53 -0400 Received: from mail-ua0-f195.google.com ([209.85.217.195]:46230 "EHLO mail-ua0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751758AbeE3Oyt (ORCPT ); Wed, 30 May 2018 10:54:49 -0400 Received: by mail-ua0-f195.google.com with SMTP id e8-v6so12660468uam.13 for ; Wed, 30 May 2018 07:54:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=mo0U8UYZTFs8Yfj4kYZIYA3C83yQjpZrmz2WeOnCk8s=; b=thjqUxov1lJas31co0n1jzKJPCKK88YcxrFv7V2pdV6UfxjfUJnSMUUyd71+cs8YT9 YeE7CRqBJbIE1MKXQ/+DN6Z1QK8vHOP5aaqLyWWm/haXfmJfSKE3cCElduHET65S0rOx /oxwoYt9gHlOppavAHPTS7hEL9YuQFheNZnlthc7LExl+5nhwJTg82VRy0JjFQ6Q4J5M vc7Yu8/7QF+2rro4MZUFdzo1TgpE1aOWQP327PBf5cyoRNUFdyAz8scS+fLDREUCWuWP 7USNMm/2j84WzqDkeqRRjQkpwL9UM0xXMe4wKTQXQn74F4i41vR2PySISIsDIwR2gPXm sfmA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=mo0U8UYZTFs8Yfj4kYZIYA3C83yQjpZrmz2WeOnCk8s=; b=Bz5gF19GWz2VKGusW/YxK09Eh2TWbgNegctRAGfffYzvAmqBLbUG1d97cgUSB/nf8Y 6CVKhq5ikee22aZIkMA924aW9kpx32LAypcJiQ7Cz8wJXEWIvy9HC6FarrO/5amfQaM5 ud76EJ+9AE6Smg1LreTDnNOMmrxBg0kdakTM4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=mo0U8UYZTFs8Yfj4kYZIYA3C83yQjpZrmz2WeOnCk8s=; b=LcVNKMEjP96RM9q3W6w0qK7hJU6gFLvsVCc9YuarBp/IH3S+WDuWOjMr/1k37mVjTa DjunshlqGGdezJs8mug/9RmneFi+cxXn38m11dAXhFQwib9FH4J+OisFemXiSTyQ6j59 lcyaeaoSLYEkIAKqDgazVFWomkdBibDapAZeXaMoGqJzOdPdljHGIpAwW50nzqqDGSt6 2mTF/l96jYfkvZfyZC8Azf7vi3XrrlgVgdMTGSj395lKYu+KDN9FTtb2IdQwY9c2qSrB 70Iw7cK5PR+qpKuRvBJBbBCkDhJBSBi+VDMLjeDz2/GIQX6xAsR+OwKT4f1VXOFWtT0+ T0EQ== X-Gm-Message-State: ALKqPwch7o89cG5Lm2dwRhrjeuI5RQTaSlJMRNkPGHlIhRUgiIUbZszH Yl04IEOvkCFcuAZ+3p7AtnYDc/PKMm1RQ4tgKvlDXg== X-Received: by 2002:ab0:6aa:: with SMTP id g39-v6mr1933573uag.82.1527692088445; Wed, 30 May 2018 07:54:48 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1f:3052:0:0:0:0:0 with HTTP; Wed, 30 May 2018 07:54:47 -0700 (PDT) In-Reply-To: <20180530103720.GH6920@sirena.org.uk> References: <6d03576cf90f06afb1194301cb41fc31704def1d.1527040878.git.collinsd@codeaurora.org> <20180530103720.GH6920@sirena.org.uk> From: Doug Anderson Date: Wed, 30 May 2018 07:54:47 -0700 X-Google-Sender-Auth: xO2qLhhKYI8xzZQHnEMUorhh1Zk Message-ID: Subject: Re: [PATCH v4 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings To: Mark Brown Cc: David Collins , Liam Girdwood , Rob Herring , Mark Rutland , linux-arm-msm@vger.kernel.org, Linux ARM , devicetree@vger.kernel.org, LKML , Rajendra Nayak , Stephen Boyd 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 Hi, On Wed, May 30, 2018 at 3:37 AM, Mark Brown wrote: > On Tue, May 29, 2018 at 10:23:20PM -0700, Doug Anderson wrote: > >> > + qcom,drms-mode-max-microamps = <10000 1000000>; > >> Things look pretty good to me now. I'm still hesitant about the whole >> need to list the modes twice (once using the unordered >> "regulator-allowed-modes" and once to match up against the ordered >> "qcom,drms-mode-max-microamps"). I'm also still of the opinion that >> the whole "drms-mode-max-microamps" ought to be a standard property >> (not a qcom specific one) and handled in the regulator core. > > I'm confused as to why we are specifying the maximum current the device > can deliver in a given mode in the DT - surely that's a fixed property > of the hardware? Said another way: you're saying that you'd expect the "max-microamps" table to have one fewer element than the listed modes? So in the above example you'd have: drms-modes: LPM, HPM max-microamps: 10000 ...or in a more complicated case, you could have: drms-modes: RET, LPM, AUTO, HPM max-microamps: 1, 100, 10000 Did I understand you correctly? I'm personally OK with that color for the shed. I kinda like the symmetry of having the same number of elements in both lists (and being able to print an error message if someone ends up asking for too much current), but it's not a big deal for me either way. -Doug