From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Alex Dewar <alex.dewar90@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Yu Chen <chenyu56@huawei.com>,
devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/5] Promote Hikey 970 USB phy out of staging
Date: Tue, 19 Jan 2021 11:44:38 +0100 [thread overview]
Message-ID: <cover.1611052729.git.mchehab+huawei@kernel.org> (raw)
Hi Vinod/Rob,
This series moves the Hikey 970 USB PHY driver out of staging.
Patches 1 to 4 contain the fixes from staging. Patch 5 moves the
driver from staging:
$ git show 82ce73ac9a38 --summary
...
rename drivers/staging/hikey9xx/phy-hi3670-usb3.yaml => Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml (100%)
rename drivers/{staging/hikey9xx => phy/hisilicon}/phy-hi3670-usb3.c (100%)
I opted to use --no-renames on this series in order to make easier to
review via e-mail, as the entire driver and DT bindings will be seen
at the last patch on this series.
v4:
- do additional changes at the hi3670_is_abbclk_seleted() function,
fixing the typo on its name and reversing the bool return code;
- the yaml fix is now on a separate patch.
v3:
- no changes on patches 1-2 nor at phy-hi3670-usb3.c;
- yaml renamed to: hisilicon,hi3670-usb3.yaml
- Added a blank line after maintainers at hisilicon,hi3670-usb3.yaml
Mauro Carvalho Chehab (5):
staging: hikey9xx: phy-hi3670-usb3: use bitfield macros
staging: hikey9xx: phy-hi3670-usb3: adjust retry logic
staging: hikey9xx: phy-hi3670-usb3: hi3670_is_abbclk_seleted() returns
bool
staging: hikey9xx: phy-hi3670-usb3.yaml: add a blank line
phy: phy-hi3670-usb3: move driver from staging into phy
.../bindings/phy/hisilicon,hi3670-usb3.yaml | 73 ++
MAINTAINERS | 9 +-
drivers/phy/hisilicon/Kconfig | 10 +
drivers/phy/hisilicon/Makefile | 1 +
drivers/phy/hisilicon/phy-hi3670-usb3.c | 668 +++++++++++++++++
drivers/staging/hikey9xx/Kconfig | 11 -
drivers/staging/hikey9xx/Makefile | 2 -
drivers/staging/hikey9xx/phy-hi3670-usb3.c | 671 ------------------
drivers/staging/hikey9xx/phy-hi3670-usb3.yaml | 72 --
9 files changed, 760 insertions(+), 757 deletions(-)
create mode 100644 Documentation/devicetree/bindings/phy/hisilicon,hi3670-usb3.yaml
create mode 100644 drivers/phy/hisilicon/phy-hi3670-usb3.c
delete mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.c
delete mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.yaml
--
2.29.2
next reply other threads:[~2021-01-19 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 10:44 Mauro Carvalho Chehab [this message]
2021-01-19 10:44 ` [PATCH v4 5/5] phy: phy-hi3670-usb3: move driver from staging into phy Mauro Carvalho Chehab
2021-02-04 7:48 ` Vinod Koul
2021-02-05 22:13 ` Rob Herring
2021-01-26 17:49 ` [PATCH v4 0/5] Promote Hikey 970 USB phy out of staging Greg Kroah-Hartman
2021-02-04 7:49 ` Vinod Koul
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=cover.1611052729.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=alex.dewar90@gmail.com \
--cc=chenyu56@huawei.com \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).