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=-12.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_PASS 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 72D91C43218 for ; Thu, 25 Apr 2019 19:27:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9B1722077C for ; Thu, 25 Apr 2019 19:27:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556220433; bh=7rTmrTrxhop8MUj70t6sLTQCqwUpQACvHEsmSi+y6sk=; h=From:To:Cc:Subject:In-Reply-To:Date:List-ID:From; b=SjKtAgiRMJ6w4dByV6mR09QsoubeG3z1hLjsgB88uR8SANces8N/Jk7dvj43SVUUy 8bfpXgjXWnp4xtfEvJwydAIHJuykhxUc7efGn3k4TyJhKKHWIVHrqFfCzQwXnXtWgP uTWhjyJrk9Cx1r1sdqUyrtug1H2LWxpXmJK0Z+2g= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730557AbfDYT0q (ORCPT ); Thu, 25 Apr 2019 15:26:46 -0400 Received: from heliosphere.sirena.org.uk ([172.104.155.198]:52678 "EHLO heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729417AbfDYT0l (ORCPT ); Thu, 25 Apr 2019 15:26:41 -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=VqilEpU0zcs5UID60f+ZH1pJ3ZhXj2B3wEwvevnvqGU=; b=HysAUfxATRFm 1BAWCJVbQlgiL+rB1RzR869KWBJunD1c9mqTEcpJ26dXd5rM0DUKKgetoVdKYVmrMwnN2aTwgJZ13 QbdV8UuUFFJcDmmt2JVcydWRR0NDyyNvU5dsO5hefth7WsjTk9z5GOYIgJkwjVnB1UhRnrMXzEktk R185Q=; Received: from 188.29.164.24.threembb.co.uk ([188.29.164.24] 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 1hJk0z-0004eV-JO; Thu, 25 Apr 2019 19:26:37 +0000 Received: by finisterre.ee.mobilebroadband (Postfix, from userid 1000) id AC64A441D3D; Thu, 25 Apr 2019 20:26:36 +0100 (BST) From: Mark Brown To: Axel Lin Cc: Dmitry Osipenko , Laxman Dewangan , Liam Girdwood , linux-kernel@vger.kernel.org, Mark Brown , Mark Zhang , Venkat Reddy Talla Subject: Applied "regulator: max77620: Fix regulator info setting for max20024" to the regulator tree In-Reply-To: <20190422053531.23123-1-axel.lin@ingics.com> X-Patchwork-Hint: ignore Message-Id: <20190425192636.AC64A441D3D@finisterre.ee.mobilebroadband> Date: Thu, 25 Apr 2019 20:26:36 +0100 (BST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The patch regulator: max77620: Fix regulator info setting for max20024 has been applied to the regulator tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.1 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 734008e714d8c757613c43ff57c1bf7ef1bb5b5d Mon Sep 17 00:00:00 2001 From: Axel Lin Date: Mon, 22 Apr 2019 13:35:31 +0800 Subject: [PATCH] regulator: max77620: Fix regulator info setting for max20024 Current code always set pmic->rinfo[id] = &max77620_regs_info[id]; It should set to either max77620_regs_info or max20024_regs_info depends on the chip_id. Signed-off-by: Axel Lin Reviewed-by: Dmitry Osipenko Tested-by: Dmitry Osipenko Signed-off-by: Mark Brown --- drivers/regulator/max77620-regulator.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/regulator/max77620-regulator.c b/drivers/regulator/max77620-regulator.c index 1607ac673e44..0ad91a7f9cb9 100644 --- a/drivers/regulator/max77620-regulator.c +++ b/drivers/regulator/max77620-regulator.c @@ -803,7 +803,7 @@ static int max77620_regulator_probe(struct platform_device *pdev) continue; rdesc = &rinfo[id].desc; - pmic->rinfo[id] = &max77620_regs_info[id]; + pmic->rinfo[id] = &rinfo[id]; pmic->enable_power_mode[id] = MAX77620_POWER_MODE_NORMAL; pmic->reg_pdata[id].active_fps_src = -1; pmic->reg_pdata[id].active_fps_pd_slot = -1; -- 2.20.1