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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D71C4C7EE25 for ; Mon, 15 May 2023 10:55:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240997AbjEOKzu (ORCPT ); Mon, 15 May 2023 06:55:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43718 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229582AbjEOKzr (ORCPT ); Mon, 15 May 2023 06:55:47 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 394F61727; Mon, 15 May 2023 03:55:45 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A996662274; Mon, 15 May 2023 10:55:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 75CC6C433D2; Mon, 15 May 2023 10:55:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1684148144; bh=wSC2+LZnwvDDwhiHmsHccGqTZjRzjmoqPgnNaz158w0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fmu3fzbqM6t6EoLnisa+XFQxyWh7rmFpB94zXys0vWlqzNblrm5uCHKvkQ3nUoiQB i+9KlUXPrWlBmdoYyFQ6YVPBG5xOGiLZ31ovEwKbIJZAYHQ7H4cw54DXoWDEQFStJk I6VaC7FEm+BWFh6Cirt1N+VT7PnF6KOdTb0qlPdvVK+cUUpbDvYKLUh8Ak9w2y1h1A Vdg/IjsZgWsxQpj867JjNbInfJ5f4afhWzQ9ov8gFI1hxOZEW3D353vfjjtmRYJAna fd/DcuQ4CUbglCLdshJRtG+w5ZEZW59nReWnnHhBxCKkkdue5KajKp2k58glyQkOwY /XJZt6l3K/GUw== Date: Mon, 15 May 2023 11:55:38 +0100 From: Lee Jones To: Krzysztof Kozlowski Cc: Andre Przywara , 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: <20230515105538.GJ8963@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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230515105229.GI8963@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 15 May 2023, 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. FYI, I just upgraded to 0.12.2. -- Lee Jones [李琼斯]