From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linuxarm@huawei.com, mauro.chehab@huawei.com,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: [PATCH v15 0/3] Move HiSilicon 6421v600 SPMI and USB drivers out of staging
Date: Fri, 23 Jul 2021 09:40:05 +0200 [thread overview]
Message-ID: <cover.1627025657.git.mchehab+huawei@kernel.org> (raw)
Hi Greg,
Those are the remaining patches needed for USB3 to start working on HiKey 970.
I would prefer to have those merged during this cycle, as the PCIe patchset
currently under review depends on patch 1 and 2 of this series.
So, I dropped the cleanup patch from this series, due to a merge conflict with
the regulator's tree. I'll re-submit it against the mfd tree after the merge window.
Mauro Carvalho Chehab (3):
mfd: hi6421-spmi-pmic: move driver from staging
dts: hisilicon: add support for the PMIC found on Hikey 970
dts: hisilicon: add support for USB3 on Hikey 970
.../mfd/hisilicon,hi6421-spmi-pmic.yaml | 136 ++++++++++++++++++
MAINTAINERS | 7 +
.../boot/dts/hisilicon/hi3670-hikey970.dts | 129 ++++++++++++++---
arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 56 ++++++++
.../boot/dts/hisilicon/hikey970-pmic.dtsi | 86 +++++++++++
drivers/mfd/Kconfig | 16 +++
drivers/mfd/Makefile | 1 +
drivers/mfd/hi6421-spmi-pmic.c | 72 ++++++++++
drivers/staging/Kconfig | 2 -
drivers/staging/Makefile | 1 -
drivers/staging/hikey9xx/Kconfig | 19 ---
drivers/staging/hikey9xx/Makefile | 3 -
drivers/staging/hikey9xx/TODO | 5 -
drivers/staging/hikey9xx/hi6421-spmi-pmic.c | 72 ----------
.../hikey9xx/hisilicon,hi6421-spmi-pmic.yaml | 136 ------------------
15 files changed, 484 insertions(+), 257 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mfd/hisilicon,hi6421-spmi-pmic.yaml
create mode 100644 arch/arm64/boot/dts/hisilicon/hikey970-pmic.dtsi
create mode 100644 drivers/mfd/hi6421-spmi-pmic.c
delete mode 100644 drivers/staging/hikey9xx/Kconfig
delete mode 100644 drivers/staging/hikey9xx/Makefile
delete mode 100644 drivers/staging/hikey9xx/TODO
delete mode 100644 drivers/staging/hikey9xx/hi6421-spmi-pmic.c
delete mode 100644 drivers/staging/hikey9xx/hisilicon,hi6421-spmi-pmic.yaml
--
2.31.1
next reply other threads:[~2021-07-23 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 7:40 Mauro Carvalho Chehab [this message]
2021-07-23 7:40 ` [PATCH v15 1/3] mfd: hi6421-spmi-pmic: move driver from staging Mauro Carvalho Chehab
2021-07-23 22:30 ` Rob Herring
2021-07-23 7:40 ` [PATCH v15 2/3] dts: hisilicon: add support for the PMIC found on Hikey 970 Mauro Carvalho Chehab
2021-07-23 7:40 ` [PATCH v15 3/3] dts: hisilicon: add support for USB3 " Mauro Carvalho Chehab
2021-07-23 8:14 ` [PATCH v15 0/3] Move HiSilicon 6421v600 SPMI and USB drivers out of staging Greg Kroah-Hartman
2021-07-23 22:32 ` Rob Herring
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.1627025657.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linuxarm@huawei.com \
--cc=mauro.chehab@huawei.com \
--cc=robh+dt@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).