From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> To: Rob Herring <robh@kernel.org>, John Stultz <john.stultz@linaro.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 Subject: [PATCH v2 0/3] Make USB ports to work on HiKey960/970 Date: Wed, 1 Sep 2021 14:23:36 +0200 [thread overview] Message-ID: <cover.1630498020.git.mchehab+huawei@kernel.org> (raw) Hi Rob, It follows a second version for the patch adding a DT schema needed to power on and to use the integrated USB HUB found on HiKey 960 and Hikey 970 boards. The entire series, which contains the remaining patches to support PCI and USB on HiKey970, and USB on HiKey960 is at: https://github.com/mchehab/linux/commits/linux-next John, The primary reason why I added the HiKey960/970 bindings on this series is because the Hikey960 one came from your tree: https://git.linaro.org/people/john.stultz/android-dev.git/commit/?h=dev/hikey960-mainline-WIP&id=fac6d20f0fee01eaaca36a8c52a44c741c6cbe78 Yet, you forgot to add your SoB there. Could you please reply to such patch with your SoB ? Thanks! Mauro --- v2: - changed the compatible strings to better reflect the names; - dropped the GPIO pin for Hikey960 power supply. It should use, instead, a regulator; - changed the names of the two gpio properties to better reflect that they're gpio; - use "-" instead of "_" at the DT property names; - Added DTS patches. John Stultz (1): arm64: dts: hisilicon: Add usb mux hub for hikey960 Mauro Carvalho Chehab (1): arm64: dts: hisilicon: Add usb mux hub for hikey970 Yu Chen (1): dt-bindings: misc: add schema for USB hub on Kirin devices .../bindings/misc/hisilicon,hikey-usb.yaml | 108 ++++++++++++++++++ .../boot/dts/hisilicon/hi3660-hikey960.dts | 35 +++++- .../boot/dts/hisilicon/hi3670-hikey970.dts | 24 ++++ 3 files changed, 165 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/misc/hisilicon,hikey-usb.yaml -- 2.31.1
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> To: Rob Herring <robh@kernel.org>, John Stultz <john.stultz@linaro.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 Subject: [PATCH v2 0/3] Make USB ports to work on HiKey960/970 Date: Wed, 1 Sep 2021 14:23:36 +0200 [thread overview] Message-ID: <cover.1630498020.git.mchehab+huawei@kernel.org> (raw) Hi Rob, It follows a second version for the patch adding a DT schema needed to power on and to use the integrated USB HUB found on HiKey 960 and Hikey 970 boards. The entire series, which contains the remaining patches to support PCI and USB on HiKey970, and USB on HiKey960 is at: https://github.com/mchehab/linux/commits/linux-next John, The primary reason why I added the HiKey960/970 bindings on this series is because the Hikey960 one came from your tree: https://git.linaro.org/people/john.stultz/android-dev.git/commit/?h=dev/hikey960-mainline-WIP&id=fac6d20f0fee01eaaca36a8c52a44c741c6cbe78 Yet, you forgot to add your SoB there. Could you please reply to such patch with your SoB ? Thanks! Mauro --- v2: - changed the compatible strings to better reflect the names; - dropped the GPIO pin for Hikey960 power supply. It should use, instead, a regulator; - changed the names of the two gpio properties to better reflect that they're gpio; - use "-" instead of "_" at the DT property names; - Added DTS patches. John Stultz (1): arm64: dts: hisilicon: Add usb mux hub for hikey960 Mauro Carvalho Chehab (1): arm64: dts: hisilicon: Add usb mux hub for hikey970 Yu Chen (1): dt-bindings: misc: add schema for USB hub on Kirin devices .../bindings/misc/hisilicon,hikey-usb.yaml | 108 ++++++++++++++++++ .../boot/dts/hisilicon/hi3660-hikey960.dts | 35 +++++- .../boot/dts/hisilicon/hi3670-hikey970.dts | 24 ++++ 3 files changed, 165 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/misc/hisilicon,hikey-usb.yaml -- 2.31.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-09-01 12:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-01 12:23 Mauro Carvalho Chehab [this message] 2021-09-01 12:23 ` [PATCH v2 0/3] Make USB ports to work on HiKey960/970 Mauro Carvalho Chehab 2021-09-01 12:23 ` [PATCH v2 1/3] dt-bindings: misc: add schema for USB hub on Kirin devices Mauro Carvalho Chehab 2021-09-02 12:03 ` Rob Herring 2021-09-01 12:23 ` [PATCH v2 2/3] arm64: dts: hisilicon: Add usb mux hub for hikey970 Mauro Carvalho Chehab 2021-09-01 12:23 ` Mauro Carvalho Chehab 2021-09-01 12:23 ` [PATCH v2 3/3] arm64: dts: hisilicon: Add usb mux hub for hikey960 Mauro Carvalho Chehab 2021-09-01 12:23 ` Mauro Carvalho Chehab 2021-09-01 19:31 ` John Stultz 2021-09-01 19:31 ` John Stultz
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.1630498020.git.mchehab+huawei@kernel.org \ --to=mchehab+huawei@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=john.stultz@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxarm@huawei.com \ --cc=mauro.chehab@huawei.com \ --cc=robh+dt@kernel.org \ --cc=robh@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.