From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
John Stultz <john.stultz@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/8] Add a staging driver for Hikey 970 PHY laywer
Date: Thu, 17 Sep 2020 12:42:04 +0200 [thread overview]
Message-ID: <cover.1600338981.git.mchehab+huawei@kernel.org> (raw)
Hi Greg,
This series add the phy layer needed for the USB stack to work
on Hikey 970.
The main difference against v3 is that I'm sending this one via
staging.
In order for this phy to actually work properly, we still need to
apply one quirk patch at dwc3, which fixes some issues with
USB HID driver.
I'm working with Felipe and Rob in order to add the quirk on
an approach that would be acceptable for both DT and dwc3
maintainers.
Due to that, I'm not sending the final patch that adds the
the needed dt bindings for this board.
Thanks!
Mauro
Mauro Carvalho Chehab (6):
staging: hikey9xx: add build for the Kirin 970 PHY driver
staging: hikey9xx: phy-hi3670-usb3: use a consistent namespace
staging: hikey9xx: phy-hi3670-usb3.txt: use a consistent namespace
staging: hikey9xx: phy-hi3670-usb3: fix coding style
staging: hikey9xx: phy-hi3670-usb3: change some DT properties
staging: hikey9xx: convert phy-kirin970-usb3.txt to yaml
Yu Chen (2):
staging: hikey9xx: add USB physical layer for Kirin 3670
staging: hikey9xx: phy-hi3670-usb3: fix some issues at the init code
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 ++
4 files changed, 756 insertions(+)
create mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.c
create mode 100644 drivers/staging/hikey9xx/phy-hi3670-usb3.yaml
--
2.26.2
next reply other threads:[~2020-09-17 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 10:42 Mauro Carvalho Chehab [this message]
2020-09-17 10:42 ` [PATCH v4 1/8] staging: hikey9xx: add USB physical layer for Kirin 3670 Mauro Carvalho Chehab
2020-09-17 10:42 ` [PATCH v4 2/8] staging: hikey9xx: add build for the Kirin 970 PHY driver Mauro Carvalho Chehab
2020-09-17 10:42 ` [PATCH v4 3/8] staging: hikey9xx: phy-hi3670-usb3: fix some issues at the init code Mauro Carvalho Chehab
2020-09-17 10:42 ` [PATCH v4 4/8] staging: hikey9xx: phy-hi3670-usb3: use a consistent namespace Mauro Carvalho Chehab
2020-09-17 10:42 ` [PATCH v4 5/8] staging: hikey9xx: phy-hi3670-usb3.txt: " Mauro Carvalho Chehab
2020-09-17 10:42 ` [PATCH v4 6/8] staging: hikey9xx: phy-hi3670-usb3: fix coding style Mauro Carvalho Chehab
2020-09-17 10:42 ` [PATCH v4 7/8] staging: hikey9xx: phy-hi3670-usb3: change some DT properties Mauro Carvalho Chehab
2020-09-17 10:42 ` [PATCH v4 8/8] staging: hikey9xx: convert phy-kirin970-usb3.txt to yaml 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.1600338981.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mani@kernel.org \
--cc=mauro.chehab@huawei.com \
--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).