Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp1419877imm; Wed, 6 Jun 2018 16:01:42 -0700 (PDT) X-Google-Smtp-Source: ADUXVKL/ePRwLMVmS/qLu8Mah6wCUYWktCo15X4/R2cayTHzvYTMl9gwlHZgUbCtAOPeZLQn8zuF X-Received: by 2002:a17:902:6bc1:: with SMTP id m1-v6mr5069829plt.91.1528326101982; Wed, 06 Jun 2018 16:01:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528326101; cv=none; d=google.com; s=arc-20160816; b=Rk+cUml/KRFwm/Qw5bGnP2Bh4/goSW7FSEODcD1s47YPIjPmLptBxebnVAEjGOwedD 6BA0HZoPw5VC34BayTrBdvUP0m6XejtRaHAnzDqQazO4dhoCdBB8uuEZyLAvIggIJhgr vhPryUDnBaDp8kShCghvUaPjNDyqFyT3ZbMvWPefIo9Pb//2Na4himUZelK/c9T3R5VU T0IRFibDFHafJcuiZhlOHLBdKLliU8udFB4KzU7lTl8BGr0Y/0jfQb/yheRSltmBQF4H RcvkCvzFVpA5wMcfkJFCLlpVkOMG7rmDVhfGzRVlYqQYEF3/9w+wZ3tEcsKUCADoKheu rXxg== 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=Kx6h6ws3N7QXDTR2Nk8etFBlorZDMxBP7LfhDUvdFgw=; b=bty1KXwYtOoKvi6b8qFOtnZnhWM26ayXXTfrTK6Ncej/HlbahQ8mSqbxHEDluLfb97 TWPrLTPwyk1mnZ21jkJHj3pj5VV/vhgXaDwLzWJGOMHxQ+wAw5OpQcvl8i/JN9eYC67t znN7dCwU5Iswu+SBuiRTG2QPCvEUlwAOXEae1np4MV+s3u86CNrt0YwXjkUL401CnpgE xhzJI7M6b+OfABe3eOOGJiy46GeJ+ehKDxwpMeOjhMpVmWtsf4vZqEHVuf48Nv6w7yv5 69tbbRpArwsQv/Nr/xDeRZBEnL2Es9uSF+NcpEG3ARE2TRwYT84W4k6u4m/f6z5ttIQq 5UGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@google.com header.s=20161025 header.b=Y2XcBnY2; dkim=fail header.i=@chromium.org header.s=google header.b=cWXK0bMg; 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 q24-v6si11654779pgv.658.2018.06.06.16.01.27; Wed, 06 Jun 2018 16:01:41 -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=Y2XcBnY2; dkim=fail header.i=@chromium.org header.s=google header.b=cWXK0bMg; 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 S1752224AbeFFW6b (ORCPT + 99 others); Wed, 6 Jun 2018 18:58:31 -0400 Received: from mail-vk0-f68.google.com ([209.85.213.68]:46216 "EHLO mail-vk0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752124AbeFFW63 (ORCPT ); Wed, 6 Jun 2018 18:58:29 -0400 Received: by mail-vk0-f68.google.com with SMTP id b134-v6so4829316vke.13 for ; Wed, 06 Jun 2018 15:58:29 -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=Kx6h6ws3N7QXDTR2Nk8etFBlorZDMxBP7LfhDUvdFgw=; b=Y2XcBnY2Izk6UfH68Q0XdONAFZ5fGbJiIF7qE+21XvNo5CsoaCWCRDT5tzN2QJXmc9 2Pt5z8iof+fE9qFxS4Qncz0GS2Xo0KBY4e5O8ErTRRuLMi/4g3gsUQPI+hUV2Nq/jHoP fZNSvFKF9pYfCMKoiqcGS34h3rSPA/H0N0a04vhLaK3Xp6A+Zfa1/b3EDW5DinGkbyrj EeDIkGqGP91M0GplCImT5uAz1aEUhhhSv9KgoTUfVbBJBIFuiuME3EwkR21n6bXBIRZN sxcsFpNtxoUlTr3TUZi7djeeoI0zq5qox1by06WXEghzEazfCViHJTR/kpWlEDYPQhyN RevA== 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=Kx6h6ws3N7QXDTR2Nk8etFBlorZDMxBP7LfhDUvdFgw=; b=cWXK0bMgQ6I5ugASIH28JK3aIbHLne3j9fwYnL2ClHr23nFpM0Val88hKrwX4XXpbe +pmJ8tPvgjHlIqmNT/Hv2hxV+G1omxYx65MxIFYkYdXDuKHffo6BdA8WFzZVuQ/m8ImW VvBUaMJEpnpHdr3Z7WOxMg83RaPSkmLnjQc50= 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=Kx6h6ws3N7QXDTR2Nk8etFBlorZDMxBP7LfhDUvdFgw=; b=f/cFhXFyaDQQhpf5UoJjoJGStaLi/BZ6hze2rZmp7Ne9nKiXowbbR0j2hl46xKluZ+ Az/1kROnKDvbOQHoNQEj8Ip8rKRopymKiUd6ZYc6XSB5Z1JO+qjeEIz6B82KC6IXK2Ob GezmQ2EUK65lHoFKno10cOZaszLsTWviHoaENFIS99RKr6lYWDPnUtwHDASBFo2zOtHS 4EQbedmGCWYXkNPFVDL+0rY5A+3hEsH3ugpIPGpRY4hAmLcqNsnRbSXPTGuAssF0bSuz Y/1qy6b4uwAR0uBnM5TvQgTGPaTd0WBzqfkbcM/zhlVwR5ESREbMtkXus1e6X2p+8Le+ LEEQ== X-Gm-Message-State: APt69E0c7jEuNkKTFJ13/sEssbXTucRpzLq5WOj8CMd7S2ms3usT4e3D BmbuCLDYx43oTjMHpwpa+pwcrXhJ3fHr9uJ9lmctjw== X-Received: by 2002:a1f:3a15:: with SMTP id h21-v6mr3234993vka.93.1528325908212; Wed, 06 Jun 2018 15:58:28 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1f:9495:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 15:58:27 -0700 (PDT) In-Reply-To: <6d7abf248493cf81d62eb17ecb5030783aa85f72.1528138319.git.collinsd@codeaurora.org> References: <6d7abf248493cf81d62eb17ecb5030783aa85f72.1528138319.git.collinsd@codeaurora.org> From: Doug Anderson Date: Wed, 6 Jun 2018 15:58:27 -0700 X-Google-Sender-Auth: 0ReGBmJnIRAH_Gom7XSDn9PlzmI Message-ID: Subject: Re: [PATCH v6 2/2] regulator: add QCOM RPMh regulator driver To: David Collins Cc: Mark Brown , Liam Girdwood , Rob Herring , Mark Rutland , linux-arm-msm@vger.kernel.org, Linux ARM , devicetree@vger.kernel.org, LKML , Rajendra Nayak , Stephen Boyd , Andy Gross , Bjorn Andersson 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 Mon, Jun 4, 2018 at 12:15 PM, David Collins wrote: > Add the QCOM RPMh regulator driver to manage PMIC regulators > which are controlled via RPMh on some Qualcomm Technologies, Inc. > SoCs. RPMh is a hardware block which contains several > accelerators which are used to manage various hardware resources > that are shared between the processors of the SoC. The final > hardware state of a regulator is determined within RPMh by > performing max aggregation of the requests made by all of the > processors. > > Add support for PMIC regulator control via the voltage regulator > manager (VRM) and oscillator buffer (XOB) RPMh accelerators. > VRM supports manipulation of enable state, voltage, and mode. > XOB supports manipulation of enable state. > > Signed-off-by: David Collins > --- > drivers/regulator/Kconfig | 9 + > drivers/regulator/Makefile | 1 + > drivers/regulator/qcom-rpmh-regulator.c | 767 ++++++++++++++++++++++++++++++++ > 3 files changed, 777 insertions(+) Assuming Mark is OK with this, it looks good to me now. My previous feedback is resolved and I'm OK with the hardcoded current loads in the driver for now until we come up with something better. Reviewed-by: Douglas Anderson NOTE: Presumably this can't actually land anywhere :( until the RPMh patchset lands somewhere and that's still sitting in limbo waiting for Qualcomm to spin the patches. Presumably once RPMh lands someone will need to put it somewhere that can be pulled into the relevant trees so we don't need to wait for a whole merge window... -Doug