From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>, <kernel@collabora.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: Re: [PATCH 1/3] dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be optional
Date: Sun, 19 Jun 2022 15:47:25 +0800 [thread overview]
Message-ID: <77a81d8ac29263da965950c9f43240836291f5a4.camel@mediatek.com> (raw)
In-Reply-To: <20220617222916.2435618-2-nfraprado@collabora.com>
On Fri, 2022-06-17 at 18:29 -0400, Nícolas F. R. A. Prado wrote:
> Add missing "minItems: 1" to the interrupt-names property to allow
> the
> second interrupt-names, "wakeup", to be optional.
>
> Fixes: fe8e488058c4 ("dt-bindings: usb: mtk-xhci: add wakeup
> interrupt")
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
>
> ---
>
> Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/mediatek,mtk-
> xhci.yaml b/Documentation/devicetree/bindings/usb/mediatek,mtk-
> xhci.yaml
> index 892718459d25..63cbc2b62d18 100644
> --- a/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml
> +++ b/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml
> @@ -57,6 +57,7 @@ properties:
> - description: optional, wakeup interrupt used to support
> runtime PM
>
> interrupt-names:
> + minItems: 1
> items:
> - const: host
> - const: wakeup
Acked-by: Chunfeng Yun <chunfeng.yun@mediatek.com>
Thanks
next prev parent reply other threads:[~2022-06-19 7:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 22:29 [PATCH 0/3] Fixes for dtbs_check warnings on Mediatek XHCI nodes Nícolas F. R. A. Prado
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 [this message]
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
2022-06-17 22:29 ` [PATCH 3/3] arm64: dts: mt8192: Follow clock order for XHCI 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=77a81d8ac29263da965950c9f43240836291f5a4.camel@mediatek.com \
--to=chunfeng.yun@mediatek.com \
--cc=angelogioacchino.delregno@collabora.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=nfraprado@collabora.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