Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2208573rwd; Mon, 15 May 2023 08:37:03 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5qyMpBUqYt6bAbU2fgTBm6/Dt9xhDMqY9giKg/YrM/w0/8W3chj9pn2F/6PCFPwkgo0H+r X-Received: by 2002:a05:6a00:1396:b0:646:6cc3:4a52 with SMTP id t22-20020a056a00139600b006466cc34a52mr34163776pfg.3.1684165023648; Mon, 15 May 2023 08:37:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684165023; cv=none; d=google.com; s=arc-20160816; b=s6Uh0OUs7ek7+3KpIhye81dFqR22T26hWKp15LKLFHuNel9NvtW70boLn0swEl+/jr CPuon9wdTp38A8dY4aglN+GLMnqUx/dZlJ7/tUOf8r9g/8SC7KIMormkTOwmyDl+HzI/ s9+sV2bWHm50nkSZqxGztyli44E2phRvDlkXb0DIVz0p0ZrQiJxEM1Xx640EK58M+U6N a9JH86jj4KT2cAUg2lHDFdE0V0TLc0Ay0+UqqZu2BMgvCAW6hX3HM7wI0TBrpw+3MdwN rqxlFHHByHDKKyW7osw0LlX4GWF4m48Oc54XNqc/4Piu6Cc1WJDtWNVbav6VUMtNZ783 QU/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=OVV7IBfo8yVYUQE5OD7Rk4qUCOaqDKuA2q3rnnANJfk=; b=ODhXME+PdbC09e93YgXg8smChsJ+PcrP6tdU42x8a3gnIiQMmjl4UG1+jHMBitbtxU wWBewFc0Bpi/sfTZ+9rMhcCxMUqIpUTkRtUrHGf9RhTDAxl08uqru6gcSjYfypvLCivb 60fduex/kbXI2KQz7sX6F1iD1Pu1xW5UjGYoDd+OrTN4O8vaagz55uwMRC+8XpGrI8vh Jijz2AVeo9SszXtNOAOxeV/e6kHtBvgVmkul2dakFIjmZ7KuBdvfslZWD8+a/H9nCjgp AFKLAnCNcJxGZ1SSfaCY7+W9tB/WSlMge+XuDkvWpOgjvC6M6FDEsKNEoTN/KFQpsBOO MTxg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q24-20020aa78438000000b0063afb349e8fsi17355415pfn.141.2023.05.15.08.36.49; Mon, 15 May 2023 08:37:03 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242319AbjEOPT7 (ORCPT + 99 others); Mon, 15 May 2023 11:19:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242365AbjEOPTv (ORCPT ); Mon, 15 May 2023 11:19:51 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 1BC5E172A; Mon, 15 May 2023 08:19:44 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 522F92F4; Mon, 15 May 2023 08:20:29 -0700 (PDT) Received: from donnerap.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 186883F663; Mon, 15 May 2023 08:19:42 -0700 (PDT) Date: Mon, 15 May 2023 16:19:40 +0100 From: Andre Przywara To: Lee Jones Cc: Krzysztof Kozlowski , Shengyu Qu , robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, wens@csie.org, lgirdwood@gmail.com, broonie@kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, conor.dooley@microchip.com, Martin Botka Subject: Re: [PATCH v3 2/3] mfd: axp20x: Add support for AXP15060 PMIC Message-ID: <20230515161940.3bcbe932@donnerap.cambridge.arm.com> In-Reply-To: <20230515105229.GI8963@google.com> References: <20230421150816.10513-1-wiagn233@outlook.com> <20230426142740.GN50521@google.com> <20230503120759.6fd6a7a9@donnerap.cambridge.arm.com> <19bccb62-b7e0-855d-fb5f-4fd3dde4f6f0@linaro.org> <20230515105229.GI8963@google.com> Organization: ARM X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.32; aarch64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 15 May 2023 11:52:29 +0100 Lee Jones wrote: > On Thu, 04 May 2023, Krzysztof Kozlowski wrote: > > > On 03/05/2023 13:07, Andre Przywara wrote: > > > On Wed, 26 Apr 2023 15:27:40 +0100 > > > Lee Jones wrote: > > > > > > Hi Lee, > > > > > > I see this patch in Linus' tree, but something must have gone wrong here, > > > can you please check? See below ... > > > > > >> On Fri, 21 Apr 2023, Shengyu Qu wrote: > > >> > > >>> The AXP15060 is a PMIC chip produced by X-Powers, and could be connected > > >>> via an I2C bus. > > >>> > > >>> Describe the regmap and the MFD bits, along with the registers exposed > > >>> via I2C. Eventually advertise the device using a new compatible string > > >>> and add support for power off the system. > > >>> > > >>> The driver would disable PEK function if IRQ is not configured in device > > >>> tree, since some boards (For example, Starfive Visionfive 2) didn't > > >>> connect IRQ line of PMIC to SOC. > > >>> > > >>> GPIO function isn't enabled in this commit, since its configuration > > >>> operation is different from any existing AXP PMICs and needs > > >>> logic modification on existing driver. GPIO support might come in later > > >>> patches. > > >>> > > >>> --- > > >> > > >> You must not use these above the tags or Git will drop them. > > >> > > >>> Changes since v2: > > >>> - Rebase to AXP313a series v10 [1] + newest (20230420) -next branch > > > > > > So this patch was based on the AXP313a series, but I don't see that in > > > Linus' tree (or in any of your trees, if I have checked correctly). > > > There must have been a conflict, as this [PATCH v3 2/3] diff actually lists > > > the axp313a entry in the context lines. > > > > > >>> - Add axp_regulator_only_cells rather than directly using axp806_cells > > >>> for cases that IRQ line isn't connected. > > >>> > > >>> Changes since v1: > > >>> - Nothing > > >>> > > >>> [1] https://lore.kernel.org/linux-sunxi/20230401001850.4988-1-andre.przywara@arm.com/ > > >>> > > >>> Signed-off-by: Shengyu Qu > > >>> --- > > >> > > >> Put change-logs here instead. > > >> > > >>> drivers/mfd/axp20x-i2c.c | 2 + > > >>> drivers/mfd/axp20x.c | 107 +++++++++++++++++++++++++++++++++++++ > > >>> include/linux/mfd/axp20x.h | 85 +++++++++++++++++++++++++++++ > > >>> 3 files changed, 194 insertions(+) > > >> > > >> I manually added the missing tags for this and the DT patch and applied. > > > > > > So this patch doesn't list any tags aside from Shengyu's > > > Signed-off-by. The patch in Linus' tree list a Reviewed-by: from > > > Krzysztof, which I don't see anywhere in the thread, he just reviewed the > > > binding patch, AFAICT. > > > > Yep, I never reviewed this. > > > > > I see your tentative R-b: on v2, but with the > > > request to rebase and resend, which he did with v3. The applied patch > > > looks like v3, but not on the base commit this was send against. > > > > > > So I am slightly confused, and am also wondering what happened to the > > > AXP313a patches? I see the binding patch merged, but not the MFD part, > > > even though you replied saying so. > > > > Because the patch #1 was broken, see: > > https://lore.kernel.org/all/TY3P286MB261177CF7AA2959BD9517DA998609@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM/ > > > > The SoB and Reviewed-by were after --- and apparently b4 understood it > > as cover letter and applied everywhere. > > > > Lee, > > Do you have the latest b4? If yes, this should be reported as b4 bug, > > assuming you used it. > > I am using b4, although the version I'm using is quite old (0.9.0). > > Also, this was quite some time ago - I have slept since applying this > and do not distinctly remember doing so. Thus, the application of your > R-b may well have been a mistake on my part. I'll keep an eye for such > things in the future and if I see (and remember) an issue, I'll report > it. So what are we going to do about the two series now? I guess it's not worthwhile to revert Shengyu's patch, just for the wrong R-b: tag? So does this mean both series should be rebased on top of that and re-sent? Cheers, Andre