From: Jianjun Wang <jianjun.wang@mediatek.com>
To: Chunfeng Yun <chunfeng.yun@mediatek.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
"Chen-Yu Tsai" <wenst@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Wei-Shun Chang <weishunc@google.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rex-bc.chen@mediatek.com>,
<randy.wu@mediatek.com>, <jieyy.yang@mediatek.com>,
<chuanjia.liu@mediatek.com>, <qizhong.cheng@mediatek.com>,
<jian.yang@mediatek.com>
Subject: Re: [PATCH v5 0/2] phy: mediatek: Add PCIe PHY driver
Date: Wed, 6 Apr 2022 13:47:34 +0800 [thread overview]
Message-ID: <06c9f2f8236f8dab6b27da9db0332b4ca45a1039.camel@mediatek.com> (raw)
In-Reply-To: <20220326022728.2969-1-jianjun.wang@mediatek.com>
Hello Maintainers,
Is there anything I can do to get these patches merged?
Thanks.
On Sat, 2022-03-26 at 10:27 +0800, Jianjun Wang wrote:
> These series patches add support for PCIe PHY driver on MediaTek
> chipsets.
>
> Changes in v5:
> 1. Fix typo in kerneldoc: "eFues" => "eFuse".
>
> Changes in v4:
> 1. Fix no return when calling dev_err_probe.
>
> Changes in v3:
> 1. Add introductions for structure members;
> 2. Add SoC dependent data;
> 3. Dynamically allocate efuse data;
> 4. Check return value if it's an -EPROBE_DEFER.
>
> Changes in v2:
> 1. Add specific compatible name;
> 2. Read NVMEM data at probe time;
> 3. Fix typos.
>
> Jianjun Wang (2):
> dt-bindings: phy: mediatek: Add YAML schema for PCIe PHY
> phy: mediatek: Add PCIe PHY driver
>
> .../bindings/phy/mediatek,pcie-phy.yaml | 75 +++++
> drivers/phy/mediatek/Kconfig | 11 +
> drivers/phy/mediatek/Makefile | 1 +
> drivers/phy/mediatek/phy-mtk-pcie.c | 272
> ++++++++++++++++++
> 4 files changed, 359 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/phy/mediatek,pcie-phy.yaml
> create mode 100644 drivers/phy/mediatek/phy-mtk-pcie.c
>
next prev parent reply other threads:[~2022-04-06 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 2:27 [PATCH v5 0/2] phy: mediatek: Add PCIe PHY driver Jianjun Wang
2022-03-26 2:27 ` [PATCH v5 1/2] dt-bindings: phy: mediatek: Add YAML schema for PCIe PHY Jianjun Wang
2022-03-26 2:27 ` [PATCH v5 2/2] phy: mediatek: Add PCIe PHY driver Jianjun Wang
2022-04-11 17:24 ` Vinod Koul
2022-04-14 8:50 ` Jianjun Wang
2022-04-06 5:47 ` Jianjun Wang [this message]
2022-04-06 15:38 ` [PATCH v5 0/2] " Krzysztof Kozlowski
2022-04-07 2:27 ` Jianjun Wang
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=06c9f2f8236f8dab6b27da9db0332b4ca45a1039.camel@mediatek.com \
--to=jianjun.wang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chuanjia.liu@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=jian.yang@mediatek.com \
--cc=jieyy.yang@mediatek.com \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=qizhong.cheng@mediatek.com \
--cc=randy.wu@mediatek.com \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=weishunc@google.com \
--cc=wenst@chromium.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;
as well as URLs for NNTP newsgroup(s).