From: Shengyu Qu <wiagn233@outlook.com>
To: Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: wiagn233@outlook.com, Andre Przywara <andre.przywara@arm.com>,
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 <martin.botka@somainline.org>
Subject: Re: [PATCH v3 2/3] mfd: axp20x: Add support for AXP15060 PMIC
Date: Mon, 15 May 2023 22:19:25 +0800 [thread overview]
Message-ID: <TY3P286MB2611F5969DC0F3F11FB8689B98789@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230515105229.GI8963@google.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 3966 bytes --]
Hi Lee,
Why there's no news about patch 3 for my series and axp313a series?
It can't work without patch 3. And could we see the fix for patch1/2 in
next RC?
Best regards,
Shengyu
> 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 <lee@kernel.org> 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 <wiagn233@outlook.com>
>>>>> ---
>>>> 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.
>
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 6977 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-15 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230421150816.10513-1-wiagn233@outlook.com>
2023-04-21 15:08 ` [PATCH v3 1/3] dt-bindings: mfd: x-powers,axp152: Document the AXP15060 variant Shengyu Qu
2023-04-27 17:19 ` Lee Jones
2023-04-21 15:08 ` [PATCH v3 2/3] mfd: axp20x: Add support for AXP15060 PMIC Shengyu Qu
2023-04-26 14:27 ` Lee Jones
2023-05-03 11:07 ` Andre Przywara
2023-05-04 6:59 ` Krzysztof Kozlowski
2023-05-15 10:52 ` Lee Jones
2023-05-15 10:55 ` Lee Jones
2023-05-15 14:19 ` Shengyu Qu [this message]
2023-05-15 15:10 ` Krzysztof Kozlowski
2023-05-15 15:19 ` Andre Przywara
2023-05-15 15:28 ` Lee Jones
2023-05-15 15:44 ` Shengyu Qu
2023-05-24 0:06 ` Andre Przywara
2023-04-21 15:08 ` [PATCH v3 3/3] regulator: axp20x: Add AXP15060 support Shengyu Qu
2023-04-21 16:28 ` Mark Brown
2023-05-04 7:02 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TY3P286MB2611F5969DC0F3F11FB8689B98789@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM \
--to=wiagn233@outlook.com \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.botka@somainline.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®