From: Ravi Gunasekaran <r-gunasekaran@ti.com>
To: Rob Herring <robh+dt@kernel.org>, Vignesh Raghavendra <vigneshr@ti.com>
Cc: <nm@ti.com>, <afd@ti.com>, <kristo@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: [EXTERNAL] Re: [PATCH v10 1/9] dt-bindings: mfd: ti, j721e-system-controller: Fix mux node regex
Date: Wed, 22 Feb 2023 10:08:13 +0530 [thread overview]
Message-ID: <fedc168f-d177-be1b-da0c-3a337857d923@ti.com> (raw)
In-Reply-To: <CAL_JsqKcktHkexxPaneZjaUt=XwLA_5ypZxSZKnX5TozdgJ+Kg@mail.gmail.com>
On 21/02/23 10:34 pm, Rob Herring wrote:
> On Tue, Feb 21, 2023 at 8:00 AM Vignesh Raghavendra <vigneshr@ti.com> wrote:
>> On 21/02/23 5:36 pm, 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>
>>> ---
>
> Where's the change history? I doubt I ignored the last 9 versions...
This change was added newly in v8.
But based on the review comments, dtbs warnings can be fixed without
changes to bindings document. So this patch will be dropped in the next
series.
Ravi
>
>>> .../bindings/mfd/ti,j721e-system-controller.yaml | 8 +++++++-
>>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>>
>>> 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]+$":
>>
>> Hmm. mmio-mux bindings allow reg property. Why can't we add the same to
>> mux-controller node in 2/9 ?
>
> Yes, do that.
>
> Rob
_______________________________________________
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-22 4:39 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
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 ` Ravi Gunasekaran [this message]
2023-02-22 4:35 ` 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=fedc168f-d177-be1b-da0c-3a337857d923@ti.com \
--to=r-gunasekaran@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=nm@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