From: Nishanth Menon <nm@ti.com>
To: Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: <afd@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<s-vadapalli@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 1/9] dt-bindings: mfd: ti,j721e-system-controller: Fix mux node regex
Date: Tue, 21 Feb 2023 07:41:20 -0600 [thread overview]
Message-ID: <20230221134120.hveyczujflmfjbsz@matted> (raw)
In-Reply-To: <20230221120612.27366-2-r-gunasekaran@ti.com>
On 17:36-20230221, Ravi Gunasekaran wrote:
> mux-controller nodes may not have "reg" property. Update the regex
> for such nodes to resolve the dtbs warnings
>
> Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
> ---
> .../bindings/mfd/ti,j721e-system-controller.yaml | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Are you expecting for me to pick this up? Looks like something
Lee Jones needs to pick up? He is'nt in the CC either?
If Lee Jones is willing to give me an immutable tag, I can pick the same
up and pick up dependent patches. Else, please split the series for each
of the maintainers to pick up without dependency.
>
> diff --git a/Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml b/Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml
> index 76ef4352e13c..532bfa45e6a0 100644
> --- a/Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml
> +++ b/Documentation/devicetree/bindings/mfd/ti,j721e-system-controller.yaml
> @@ -45,7 +45,7 @@ properties:
>
> patternProperties:
> # Optional children
> - "^mux-controller@[0-9a-f]+$":
> + "^mux-controller(@|-)[0-9a-f]+$":
> type: object
> description:
> This is the SERDES lane control mux.
> @@ -94,6 +94,12 @@ examples:
> /* SERDES4 lane0/1/2/3 select */
> };
>
> + usb_serdes_mux: mux-controller-80 {
> + compatible = "mmio-mux";
> + #mux-control-cells = <1>;
> + mux-reg-masks = <0x0 0x8000000>;
> + };
> +
> clock-controller@4140 {
> compatible = "ti,am654-ehrpwm-tbclk", "syscon";
> reg = <0x4140 0x18>;
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-21 13:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 12:06 [PATCH v10 0/9] arm64: j721s2: Add support for additional IPs Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 1/9] dt-bindings: mfd: ti,j721e-system-controller: Fix mux node regex Ravi Gunasekaran
2023-02-21 13:41 ` Nishanth Menon [this message]
2023-02-22 4:33 ` Ravi Gunasekaran
2023-02-21 13:59 ` Vignesh Raghavendra
2023-02-21 17:04 ` Rob Herring
2023-02-22 4:38 ` [EXTERNAL] Re: [PATCH v10 1/9] dt-bindings: mfd: ti, j721e-system-controller: " Ravi Gunasekaran
2023-02-22 4:35 ` [PATCH v10 1/9] dt-bindings: mfd: ti,j721e-system-controller: " Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 2/9] arm64: dts: ti: k3-j721s2-main: Add support for USB Ravi Gunasekaran
2023-02-21 13:58 ` Nishanth Menon
2023-02-22 4:51 ` Ravi Gunasekaran
2023-02-22 13:15 ` Nishanth Menon
2023-02-21 12:06 ` [PATCH v10 3/9] arm64: dts: ti: k3-j721s2-main: Add SERDES and WIZ device tree node Ravi Gunasekaran
2023-02-21 14:01 ` Nishanth Menon
2023-02-22 4:53 ` Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 4/9] arm64: dts: ti: k3-j721s2-mcu-wakeup: Add support of OSPI Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 5/9] arm64: dts: ti: k3-j721s2-common-proc-board: Enable SERDES0 Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 6/9] arm64: dts: ti: k3-j721s2-common-proc-board: Add USB support Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 7/9] arm64: dts: ti: k3-j721s2: Add support for OSPI Flashes Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 8/9] arm64: dts: ti: k3-j721s2-main: Add PCIe device tree node Ravi Gunasekaran
2023-02-21 12:06 ` [PATCH v10 9/9] arm64: dts: ti: k3-j721s2-common-proc-board: Enable PCIe Ravi Gunasekaran
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=20230221134120.hveyczujflmfjbsz@matted \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r-gunasekaran@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.com \
/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