public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	"Allen-KH Cheng" <allen-kh.cheng@mediatek.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 0/3] Fixes for dtbs_check warnings on Mediatek XHCI nodes
Date: Fri, 17 Jun 2022 18:29:13 -0400	[thread overview]
Message-ID: <20220617222916.2435618-1-nfraprado@collabora.com> (raw)


The two first patches fix inconsistencies in the mtk-xhci dt-binding,
while the third patch is a DTS change to use the clock order required by
the binding (and that was fixed in patch 2).

This series gets rid of a couple dtbs_check warnings on mt8192.dtsi and
another on mt8195.dtsi.


Nícolas F. R. A. Prado (3):
  dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be
    optional
  dt-bindings: usb: mtk-xhci: Allow middle optional clocks to be missing
  arm64: dts: mt8192: Follow clock order for XHCI

 .../devicetree/bindings/usb/mediatek,mtk-xhci.yaml     | 10 ++++++++--
 arch/arm64/boot/dts/mediatek/mt8192.dtsi               |  6 +++---
 2 files changed, 11 insertions(+), 5 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-06-17 22:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 22:29 Nícolas F. R. A. Prado [this message]
2022-06-17 22:29 ` [PATCH 1/3] dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be optional Nícolas F. R. A. Prado
2022-06-18  1:30   ` Krzysztof Kozlowski
2022-06-19  7:47   ` Chunfeng Yun
2022-06-17 22:29 ` [PATCH 2/3] dt-bindings: usb: mtk-xhci: Allow middle optional clocks to be missing Nícolas F. R. A. Prado
2022-06-18  1:25   ` Krzysztof Kozlowski
2022-06-19  7:46     ` Chunfeng Yun
2022-06-19 12:05       ` Krzysztof Kozlowski
2022-06-20  6:59         ` Chunfeng Yun
2022-06-20  8:50           ` Krzysztof Kozlowski
2022-06-20 15:50             ` Nícolas F. R. A. Prado
2022-06-21  7:14               ` Krzysztof Kozlowski
2022-06-22  1:57                 ` Chunfeng Yun
2022-06-22  6:10                   ` Wenbin Mei
2022-06-22 13:22                     ` Nícolas F. R. A. Prado
2022-06-19  7:40   ` Chunfeng Yun
2022-06-19 11:49     ` Krzysztof Kozlowski

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=20220617222916.2435618-1-nfraprado@collabora.com \
    --to=nfraprado@collabora.com \
    --cc=allen-kh.cheng@mediatek.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