From: Jian Yang <jian.yang@mediatek.com>
To: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Jianjun Wang" <jianjun.wang@mediatek.com>
Cc: <linux-pci@vger.kernel.org>, <linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<Chuanjia.Liu@mediatek.com>, <Jieyy.Yang@mediatek.com>,
<Qizhong.Cheng@mediatek.com>, <Jianguo.Zhang@mediatek.com>,
Jian Yang <jian.yang@mediatek.com>
Subject: [PATCH v4 0/2] PCI: mediatek-gen3: Support controlling power supplies
Date: Mon, 6 Nov 2023 14:12:18 +0800 [thread overview]
Message-ID: <20231106061220.21485-1-jian.yang@mediatek.com> (raw)
Add support for controlling power supplies and reset GPIO of a downstream
component in Mediatek's PCIe GEN3 controller driver.
Changes in v4:
1. Rename power supplies properties in DT binding and driver.
2. Reorder variables alphabetically.
3. Use 'dev_err_probe' to do some error handling stuff.
Changes in v3:
1. Modify description of power supply properties in DT binding.
2. Remove unused header files.
3. Use 'device_wakeup_path' to determine whether the downstream component
needs to skip the reset process in system suspend scenarios.
Changes in v2:
1. Remove an unnecessary property in dt-bindings file.
2. Use the flag 'GPIOD_OUT_LOW' to set initial state of a downstream
component's reset GPIO.
3. Keep downstream component powered on in suspend state if it is capable
of waking up the system.
jian.yang (2):
dt-bindings: PCI: mediatek-gen3: Add support for controlling power and
reset
PCI: mediatek-gen3: Add power and reset control feature for downstream
component
.../bindings/pci/mediatek-pcie-gen3.yaml | 30 +++++++
drivers/pci/controller/pcie-mediatek-gen3.c | 89 ++++++++++++++++++-
2 files changed, 118 insertions(+), 1 deletion(-)
--
2.18.0
next reply other threads:[~2023-11-06 6:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 6:12 Jian Yang [this message]
2023-11-06 6:12 ` [PATCH v4 1/2] dt-bindings: PCI: mediatek-gen3: Add support for controlling power and reset Jian Yang
2023-11-06 7:50 ` Krzysztof Kozlowski
2023-11-06 8:25 ` AngeloGioacchino Del Regno
2023-11-06 8:48 ` Krzysztof Kozlowski
2023-11-06 6:12 ` [PATCH v4 2/2] PCI: mediatek-gen3: Add power and reset control feature for downstream component Jian Yang
2023-11-06 7:53 ` Krzysztof Kozlowski
2023-11-06 8:36 ` AngeloGioacchino Del Regno
2023-11-06 8:46 ` Krzysztof Kozlowski
2023-11-06 8:56 ` AngeloGioacchino Del Regno
2023-11-06 8:23 ` AngeloGioacchino Del Regno
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=20231106061220.21485-1-jian.yang@mediatek.com \
--to=jian.yang@mediatek.com \
--cc=Chuanjia.Liu@mediatek.com \
--cc=Jianguo.Zhang@mediatek.com \
--cc=Jieyy.Yang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Qizhong.Cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jianjun.wang@mediatek.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=matthias.bgg@gmail.com \
--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