From: Changhuang Liang <changhuang.liang@starfivetech.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor@kernel.org>
Cc: Walker Chen <walker.chen@starfivetech.com>,
Hal Feng <hal.feng@starfivetech.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/4] Add JH7110 AON PMU support
Date: Thu, 20 Jul 2023 11:46:27 +0800 [thread overview]
Message-ID: <7fe9bc9a-2bb1-6c5c-2ed5-1eee85b8f299@starfivetech.com> (raw)
In-Reply-To: <20230519060202.15296-1-changhuang.liang@starfivetech.com>
On 2023/5/19 14:01, Changhuang Liang wrote:
> This patchset adds aon power domain driver for the StarFive JH7110 SoC.
> It is used to turn on/off dphy rx/tx power switch. It also can use syscon
> operation. The series has been tested on the VisionFive 2 board.
>
> This patchset should be applied after the patchset [1]:
> [1] https://lore.kernel.org/all/20230512022036.97987-1-xingyu.wu@starfivetech.com/
>
Hi, Conor
Pll series is accepted, should I need to send a new version about this series?
Best regards,
Changhuang
next prev parent reply other threads:[~2023-07-20 3:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:01 [PATCH v4 0/4] Add JH7110 AON PMU support Changhuang Liang
2023-05-19 6:01 ` [PATCH v4 1/4] dt-bindings: power: Add power-domain header for JH7110 Changhuang Liang
2023-05-19 18:42 ` Conor Dooley
2023-05-20 11:10 ` Changhuang Liang
2023-05-19 6:02 ` [PATCH v4 2/4] soc: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE Changhuang Liang
2023-05-19 6:02 ` [PATCH v4 3/4] soc: starfive: Extract JH7110 pmu private operations Changhuang Liang
2023-05-19 6:02 ` [PATCH v4 4/4] soc: starfive: Add JH7110 AON PMU support Changhuang Liang
2023-07-20 3:46 ` Changhuang Liang [this message]
2023-07-20 6:48 ` [PATCH v4 0/4] " Conor Dooley
2023-07-20 17:12 ` Conor Dooley
2023-07-21 3:01 ` Changhuang Liang
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=7fe9bc9a-2bb1-6c5c-2ed5-1eee85b8f299@starfivetech.com \
--to=changhuang.liang@starfivetech.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hal.feng@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=walker.chen@starfivetech.com \
/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;
as well as URLs for NNTP newsgroup(s).