From: Peter Chen <peter.chen@cixtech.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, mani@kernel.org
Cc: Gary Yang <gary.yang@cixtech.com>,
lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
robh@kernel.org, bhelgaas@google.com, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
cix-kernel-upstream@cixtech.com
Subject: Re: [PATCH v4 1/2] dt-bindings: PCI: cix,sky1-pcie-host: Add power-domains
Date: Mon, 16 Mar 2026 16:50:03 +0800 [thread overview]
Message-ID: <abfEO6iW3NcnMyNx@nchen-desktop> (raw)
In-Reply-To: <20260314-maize-warthog-of-modernism-f74475@quoll>
On 26-03-14 10:26:11, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL
>
> On Fri, Mar 13, 2026 at 07:49:13PM +0800, Gary Yang wrote:
> > The Sky1 PCIe controller resides in a dedicated power domain managed
> > via SCMI. Add the power-domains property to the binding to allow
> > describing this dependency.
> >
> > Signed-off-by: Gary Yang <gary.yang@cixtech.com>
> > ---
> > Documentation/devicetree/bindings/pci/cix,sky1-pcie-host.yaml | 3 +++
> > 1 file changed, 3 insertions(+)
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
Thank Krzysztof for kindly review it.
Mani, I assume this patch will go to PCIe tree, right?
--
Best regards,
Peter
next prev parent reply other threads:[~2026-03-16 8:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 11:49 [PATCH v4 0/2] Add scmi powerdomain for sky1 Gary Yang
2026-03-13 11:49 ` [PATCH v4 1/2] dt-bindings: PCI: cix,sky1-pcie-host: Add power-domains Gary Yang
2026-03-14 9:26 ` Krzysztof Kozlowski
2026-03-16 8:50 ` Peter Chen [this message]
2026-03-24 6:44 ` Peter Chen
2026-03-24 7:13 ` Manivannan Sadhasivam
2026-03-13 11:49 ` [PATCH v4 2/2] arm64: dts: cix: Add scmi powerdomain nodes for sky1 Gary Yang
2026-03-24 11:45 ` Peter Chen
2026-03-24 7:17 ` (subset) [PATCH v4 0/2] Add scmi powerdomain " Manivannan Sadhasivam
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=abfEO6iW3NcnMyNx@nchen-desktop \
--to=peter.chen@cixtech.com \
--cc=bhelgaas@google.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gary.yang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.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