From: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>
To: balbi@kernel.org, gregkh@linuxfoundation.org, kishon@ti.com,
vkoul@kernel.org, robh+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, dongsheng.qiu@ingenic.com,
aric.pzqi@ingenic.com, rick.tyliu@ingenic.com,
yanfei.li@ingenic.com, sernia.zhou@foxmail.com,
zhenwenjin@gmail.com, paul@crapouillou.net
Subject: [PATCH v8 0/3] Use the generic PHY framework for Ingenic USB PHY.
Date: Sat, 7 Nov 2020 17:47:55 +0800 [thread overview]
Message-ID: <20201107094758.83291-1-zhouyanjie@wanyeetech.com> (raw)
v3->v4:
Only add new generic-PHY driver, without removing the old one. Because the
jz4740-musb driver is not ready to use the generic PHY framework. When the
jz4740-musb driver is modified to use the generic PHY framework, the old
jz4770-phy driver can be "retired".
v4->v5:
1.Add an extra blank line between "devm_of_phy_provider_register" and "return".
2.Remove unnecessary "phy_set_drvdata".
3.Add Paul Cercueil's Reviewed-by.
v5->v6:
1.Revert the removal of "phy_set_drvdata" in v5, removing "phy_set_drvdata" will
cause a kernel panic on CI20.
Reported-by: H. Nikolaus Schaller <hns@goldelico.com>
2.Rewrite the macro definitions, replace the original code with "FIELD_PREP()"
and "u32p_replace_bits()" according to Vinod Koul's suggestion.
v6->v7:
1.Remove the stray tab character.
2.Remove unnecessary "platform_set_drvdata".
3.Remove the "dev" field in priv structure, and use &phy->dev instead.
v7->v8:
Add support for Ingenic JZ4775 SoC and X2000 SoC.
周琰杰 (Zhou Yanjie) (3):
USB: PHY: JZ4770: Remove unnecessary function calls.
dt-bindings: USB: Add bindings for Ingenic JZ4775 and X2000.
PHY: Ingenic: Add USB PHY driver using generic PHY framework.
.../ingenic,phy-usb.yaml} | 4 +-
drivers/phy/Kconfig | 1 +
drivers/phy/Makefile | 1 +
drivers/phy/ingenic/Kconfig | 12 +
drivers/phy/ingenic/Makefile | 2 +
drivers/phy/ingenic/phy-ingenic-usb.c | 412 +++++++++++++++++++++
drivers/usb/phy/phy-jz4770.c | 2 +-
7 files changed, 432 insertions(+), 2 deletions(-)
rename Documentation/devicetree/bindings/{usb/ingenic,jz4770-phy.yaml => phy/ingenic,phy-usb.yaml} (89%)
create mode 100644 drivers/phy/ingenic/Kconfig
create mode 100644 drivers/phy/ingenic/Makefile
create mode 100644 drivers/phy/ingenic/phy-ingenic-usb.c
--
2.11.0
next reply other threads:[~2020-11-07 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 9:47 周琰杰 (Zhou Yanjie) [this message]
2020-11-07 9:47 ` [PATCH v8 1/3] USB: PHY: JZ4770: Remove unnecessary function calls 周琰杰 (Zhou Yanjie)
2020-11-07 9:47 ` [PATCH v8 2/3] dt-bindings: USB: Add bindings for Ingenic JZ4775 and X2000 周琰杰 (Zhou Yanjie)
2020-11-09 15:42 ` Rob Herring
2020-11-07 9:47 ` [PATCH v8 3/3] PHY: Ingenic: Add USB PHY driver using generic PHY framework 周琰杰 (Zhou Yanjie)
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=20201107094758.83291-1-zhouyanjie@wanyeetech.com \
--to=zhouyanjie@wanyeetech.com \
--cc=aric.pzqi@ingenic.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.qiu@ingenic.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=rick.tyliu@ingenic.com \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=vkoul@kernel.org \
--cc=yanfei.li@ingenic.com \
--cc=zhenwenjin@gmail.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).