From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
kernel@collabora.com,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Chunfeng Yun" <chunfeng.yun@mediatek.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-usb@vger.kernel.org
Subject: [PATCH v2 0/4] Fixes for dtbs_check warnings on Mediatek XHCI nodes
Date: Thu, 23 Jun 2022 15:36:58 -0400 [thread overview]
Message-ID: <20220623193702.817996-1-nfraprado@collabora.com> (raw)
The two first patches fix inconsistencies in the mtk-xhci dt-binding,
while the last two tweak the Mediatek devicetrees to fill in the missing
XHCI fixed clocks.
This series gets rid of a couple dtbs_check warnings on mt8192.dtsi and
another on mt8195.dtsi.
v1: https://lore.kernel.org/all/20220617222916.2435618-1-nfraprado@collabora.com
Changes in v2:
- Made all clocks required in the binding
- Instead of simply reordering the clocks on mt8192, added missing fixed
clocks for all arm64 dts
- Added missing fixed clocks for all arm dts
Nícolas F. R. A. Prado (4):
dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be
optional
dt-bindings: usb: mtk-xhci: Make all clocks required
arm64: dts: mediatek: Set fixed-clock for missing XHCI clocks
arm: dts: mediatek: Set fixed-clock for missing XHCI clocks
.../bindings/usb/mediatek,mtk-xhci.yaml | 5 ++---
arch/arm/boot/dts/mt2701.dtsi | 14 ++++++++++----
arch/arm/boot/dts/mt7623.dtsi | 14 ++++++++++----
arch/arm/boot/dts/mt7629.dtsi | 6 ++++--
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 18 ++++++++++++++----
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 5 +++--
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 9 +++++++--
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 8 ++++++--
arch/arm64/boot/dts/mediatek/mt8192.dtsi | 9 ++++++---
arch/arm64/boot/dts/mediatek/mt8195.dtsi | 18 ++++++++++++++----
10 files changed, 76 insertions(+), 30 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-23 19:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 19:36 Nícolas F. R. A. Prado [this message]
2022-06-23 19:36 ` [PATCH v2 1/4] dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be optional Nícolas F. R. A. Prado
2022-06-23 19:37 ` [PATCH v2 2/4] dt-bindings: usb: mtk-xhci: Make all clocks required Nícolas F. R. A. Prado
2022-06-27 19:12 ` Rob Herring
2022-06-28 0:57 ` Chunfeng Yun
2022-06-29 18:55 ` Nícolas F. R. A. Prado
2022-07-01 21:37 ` Rob Herring
2022-07-02 8:24 ` Chunfeng Yun
2022-07-05 20:36 ` Nícolas F. R. A. Prado
2022-07-07 1:10 ` Chunfeng Yun
2022-06-23 19:37 ` [PATCH v2 3/4] arm64: dts: mediatek: Set fixed-clock for missing XHCI clocks Nícolas F. R. A. Prado
2022-06-23 19:37 ` [PATCH v2 4/4] arm: " Nícolas F. R. A. Prado
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=20220623193702.817996-1-nfraprado@collabora.com \
--to=nfraprado@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.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
all inboxes | Powered by JetHome®