Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp6191421imm; Mon, 23 Jul 2018 13:10:12 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfotAOYT6NCd0d5u4OaIQ0gJyJG1JOnmz5x3+aMw8nl/TeY/SffIzGnHXLpRZCIqlQ/3Cif X-Received: by 2002:a63:d80f:: with SMTP id b15-v6mr13691676pgh.347.1532376612575; Mon, 23 Jul 2018 13:10:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532376612; cv=none; d=google.com; s=arc-20160816; b=tHk8V9HlzgkfjaWSvRt353Gqt8IpdBiJogCELkAKGSuDZGgyPSC3vffUlfWIS8WKo8 JyZMqIu84sv8MpmreEtaXf500tyYCYpl1sDmtArb0l4fhX+6wy+ZBy7y46t+HZrW/XTv YXcoTf5igWaFOSB4PGDgCOytqAsYA99nOUSDWAW+6B+JfhLWtQA6Czlk/bIbrTiu/enJ 1Jcy6q96xFizEGrSRGvGpRCXTl4hX9DnwDoqLtlYaUKvUEcGqrECv+BiNy9u3XoDpoBY xycDHyJrhPu5RITAnyq5aP+zFXZ9p/YFD3nxpHrzo/gVmvCWkBSQpuaMNG02IjsqRX+j tI2Q== 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=r4sUffr0Ek90qYcA1OGQ81QwDvnIZGgAGSIDCrrMg44=; b=NDTKcJWXB3w7TY9iZyuTkzqIHZTCZgFVFr2AFLxJbStQPHdlw7L5B2gbpsFNpFLD/c TC7xSgaMuPn1+R8PSwT2pEZsy/FopUcCbxGO34xeislmRHHqKYQRHzpsjeFaLZLKd+Jk zfdN38zLR0JcFmM1Hd9LV6uI0K8xryy/3drnY8oLBV4Dg7cuwFV89EQ9RKScu3ItDnaJ wsSru9fEzSb57lOqf7kO2J1MR2erK9Em7nQGYou4acGne3qcpS104kkJ54fs6808i7Ic +DHQM+q/ZiPuv9adZz8np6vEeojX4mz0aioQbfCTVMt3XlSVRi0DpqhxVeUDWFqTQXIo 6/oQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@google.com header.s=20161025 header.b=aoBQxFZh; dkim=fail header.i=@chromium.org header.s=google header.b=G6YTuVMb; 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 w185-v6si9263817pgb.599.2018.07.23.13.09.57; Mon, 23 Jul 2018 13:10:12 -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=aoBQxFZh; dkim=fail header.i=@chromium.org header.s=google header.b=G6YTuVMb; 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 S2388068AbeGWVL5 (ORCPT + 99 others); Mon, 23 Jul 2018 17:11:57 -0400 Received: from mail-ua0-f193.google.com ([209.85.217.193]:44418 "EHLO mail-ua0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728298AbeGWVL4 (ORCPT ); Mon, 23 Jul 2018 17:11:56 -0400 Received: by mail-ua0-f193.google.com with SMTP id k25-v6so1248135uao.11 for ; Mon, 23 Jul 2018 13:09:07 -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=r4sUffr0Ek90qYcA1OGQ81QwDvnIZGgAGSIDCrrMg44=; b=aoBQxFZhH26EoAbX0C6uCualGudX2NFFD6r+d4inwNaiJDh15BiVQUV4HY5K1ZED9k 4YtXsuDuB962R+5y4qK85dJKdbSuqoaQTPogKbF1aZkAxxtdtJDmyjbOxPTyOXJchZG1 X07NqN51OHAQjKJmcaQAbUI8Yr05lFLs7AW6PNudNIMDuCuuigRQ+M90AXNWlcPss3g4 mecIfxNTHPyYgEot0ummFDaDTJr/v6YhHxsWfw0mKmyU3ADCQLPVoS02W+tHVwCVr3xT V6eMz3t2ndh8COL7cX0tP2NKaSO5zxH4DVD/xqLHGxIvZ8QhDMW5ZKuOM9U8+RIyAAH8 AW0w== 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=r4sUffr0Ek90qYcA1OGQ81QwDvnIZGgAGSIDCrrMg44=; b=G6YTuVMbB6/uMCwgGryMlMJD1FvJ8TAxi0+Iv3OKZhUd1o4uAhjEbmRkeq2SMjrGCS EX8m6toLS/fZt19/wpW+Aqzf3JVIezEgkHyaiw3WSNNqKHYaLYsdXnKvhYehHwXRBB3/ 8gzFbLezuUe2CvZHIWUXydvoduedadt5oIUak= 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=r4sUffr0Ek90qYcA1OGQ81QwDvnIZGgAGSIDCrrMg44=; b=LS8n9Clg4oaJg5bvJ7M3Lgbn75Mgeq6uU4okuWdsmf9kNF+RYmUwEp4VvD08QesYQX xp1EoEBjU+POBI3v1oTrP+KogbBNR1G2fom7RWXwxvIg8lYjNukfcJvQpJkv+0cjkfVV d5vfjX4FT31qXvTiH/WdFKky0/chm/PViPlVVhyawfl4xXw2C10fYvdS6rNLbrRR9gj1 347WoejpX7xRU59R02HHMgRk1xxnfq5l7XvVxkXIhccraMsXgS46mkdQPvnZyjyqvb0P dsskoIN3+lUNsrY3IZCEu910UtQsGecw78O+fGqnFLnI3jy2ktZVFd2CyaTWZEOwXR+P YYGw== X-Gm-Message-State: AOUpUlFatuBoiDX8HRD7cjZYmreZbgQh8EKHOWwTSGivzFl2r/55NaIy 5OP1G7+FI0AsL/AfGuNiSCwnXKkImFmw2DT5clBA1Q== X-Received: by 2002:ab0:4364:: with SMTP id k91-v6mr9828541uak.46.1532376546840; Mon, 23 Jul 2018 13:09:06 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1f:cd5:0:0:0:0:0 with HTTP; Mon, 23 Jul 2018 13:09:05 -0700 (PDT) In-Reply-To: <56b9d5c38cfe46da1228c54f001a49773c3e31dc.1531531808.git.collinsd@codeaurora.org> References: <56b9d5c38cfe46da1228c54f001a49773c3e31dc.1531531808.git.collinsd@codeaurora.org> From: Doug Anderson Date: Mon, 23 Jul 2018 13:09:05 -0700 X-Google-Sender-Auth: 43ZwUjHa8EzenPmp93OMzt-LtKY Message-ID: Subject: Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings To: Mark Brown , David Collins Cc: Liam Girdwood , Rob Herring , Mark Rutland , linux-arm-msm , Linux ARM , devicetree@vger.kernel.org, LKML , Rajendra Nayak , Stephen Boyd , Matthias Kaehlcke 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 Mark, On Fri, Jul 13, 2018 at 6:50 PM, David Collins wrote: > Introduce bindings for RPMh regulator devices found on some > Qualcomm Technlogies, Inc. SoCs. These devices allow a given > processor within the SoC to make PMIC regulator requests which > are aggregated within the RPMh hardware block along with requests > from other processors in the SoC to determine the final PMIC > regulator hardware state. > > Signed-off-by: David Collins > Reviewed-by: Rob Herring > Reviewed-by: Douglas Anderson > --- > .../bindings/regulator/qcom,rpmh-regulator.txt | 160 +++++++++++++++++++++ > .../dt-bindings/regulator/qcom,rpmh-regulator.h | 36 +++++ > 2 files changed, 196 insertions(+) I know you are still looking for time to review the RPMh-regulator driver and that's fine. One idea I had though: if the bindings look OK to you and are less controversial, is there any chance they could land in the meantime? Specifically it would be very handy to be able to post up device tree files that refer to regulators and even get those landed, but they can't land without the bindings. If that's not possible then no worries, but I figured I'd check. -Doug