From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED, MAILING_LIST_MULTI,SPF_PASS,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BE2F5C433F4 for ; Tue, 28 Aug 2018 21:09:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 77DC1205F4 for ; Tue, 28 Aug 2018 21:09:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sirena.org.uk header.i=@sirena.org.uk header.b="b/+Cpbk/" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 77DC1205F4 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727650AbeH2BCD (ORCPT ); Tue, 28 Aug 2018 21:02:03 -0400 Received: from heliosphere.sirena.org.uk ([172.104.155.198]:47810 "EHLO heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727523AbeH2BCC (ORCPT ); Tue, 28 Aug 2018 21:02:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sirena.org.uk; s=20170815-heliosphere; h=Date:Message-Id:In-Reply-To: Subject:Cc:To:From:Sender:Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:References: List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner: List-Archive; bh=cuRoM54QCsvDpMjzmHouIBKG9bSCf1G/eF5XoG+jTfE=; b=b/+Cpbk/1hpg qLLdZb8p8ZWcq84zYEF4ERaCmtInmuOoLtTxCmmiAmGhgoZPYTd31wYoeqlkmC2dtIEHI1j18oj9p 6mDM16khOssGsUeT7tXP7eRJgv45lOQ0uLCUVu2SES0AMXb9Q6sznLhCw0VrVtwG5diV76NRTuxDC TECxM=; Received: from 94.197.121.204.threembb.co.uk ([94.197.121.204] helo=finisterre.ee.mobilebroadband) by heliosphere.sirena.org.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1fulE1-0007lu-Ew; Tue, 28 Aug 2018 21:08:33 +0000 Received: by finisterre.ee.mobilebroadband (Postfix, from userid 1000) id 55B4544007A; Tue, 28 Aug 2018 21:54:57 +0100 (BST) From: Mark Brown To: Douglas Anderson Cc: Mark Brown , linux-kernel@vger.kernel.org Subject: Applied "regulator: core: Add consumer-requested load in regulator_summary" to the regulator tree In-Reply-To: Message-Id: <20180828205457.55B4544007A@finisterre.ee.mobilebroadband> Date: Tue, 28 Aug 2018 21:54:57 +0100 (BST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The patch regulator: core: Add consumer-requested load in regulator_summary has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark >From 7d3827b5954840ff7765aef282257b7368b5ea67 Mon Sep 17 00:00:00 2001 From: Douglas Anderson Date: Thu, 16 Aug 2018 13:28:02 -0700 Subject: [PATCH] regulator: core: Add consumer-requested load in regulator_summary It's handy to see the load requested by a regulator consumer in the regulator_summary. Add it. Signed-off-by: Douglas Anderson Signed-off-by: Mark Brown --- drivers/regulator/core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c index 69b64e5ffc76..df55cf8f09f0 100644 --- a/drivers/regulator/core.c +++ b/drivers/regulator/core.c @@ -4715,7 +4715,8 @@ static void regulator_summary_show_subtree(struct seq_file *s, switch (rdev->desc->type) { case REGULATOR_VOLTAGE: - seq_printf(s, "%45dmV %5dmV", + seq_printf(s, "%37dmA %5dmV %5dmV", + consumer->uA_load / 1000, consumer->voltage[PM_SUSPEND_ON].min_uV / 1000, consumer->voltage[PM_SUSPEND_ON].max_uV / 1000); break; -- 2.18.0