From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Vinod Koul <vkoul@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>,
Rob Herring <robh+dt@kernel.org>, Yu Chen <chenyu56@huawei.com>,
devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] Promote Hikey 970 USB phy out of staging
Date: Thu, 14 Jan 2021 18:35:40 +0100 [thread overview]
Message-ID: <cover.1610645385.git.mchehab+huawei@kernel.org> (raw)
Hi Vinod,
This series contain just the PHY patch I sent in Nov, 30 from this series:
Move Hikey 970 USB support out of staging and add DT
The 3 initial patches address the issues you pointed during your
review:
patch 1 change the logic to use GENMASK and FIELD_GET/FIELD_PREP macros.
It also places all hexadecimal values in lowercase;
patch 2 add a delay inside the retry logic;
patch 3 changes a function to return a boolean.
The 4th patch is actually identical to the patch I sent previously:
it just moves the driver to drivers/phy:
rename {drivers/staging/hikey9xx => Documentation/devicetree/bindings/phy}/phy-hi3670-usb3.yaml (100%)
rename drivers/{staging/hikey9xx => phy/hisilicon}/phy-hi3670-usb3.c (100%)
Yet, in order to make this series easier to review, I'm submitting it with
--no-merges. This way, you can check the driver as a hole while reviewing
the last patch.
Mauro Carvalho Chehab (4):
staging: hikey9xx: phy-hi3670-usb3.c: use bitfield macros
staging: hikey9xx: phy-hi3670-usb3.c: adjust retry logic
staging: hikey9xx: phy-hi3670-usb3.c: hi3670_is_abbclk_seleted()
returns bool
phy: phy-hi3670-usb3: move driver from staging into phy
.../bindings/phy/phy-hi3670-usb3.yaml | 72 ++
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, 759 insertions(+), 757 deletions(-)
create mode 100644 Documentation/devicetree/bindings/phy/phy-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-14 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 17:35 Mauro Carvalho Chehab [this message]
2021-01-14 17:35 ` [PATCH v2 4/4] phy: phy-hi3670-usb3: move driver from staging into phy Mauro Carvalho Chehab
2021-01-14 22:54 ` Rob Herring
2021-01-15 1:47 ` Rob Herring
2021-01-19 10:26 ` Mauro Carvalho Chehab
2021-01-22 14:51 ` Rob Herring
2021-01-22 15:57 ` Mauro Carvalho Chehab
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.1610645385.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).