From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Conor Dooley <conor@kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 2/2] dt-bindings: mfd: document syscons falling back to atmel,sama5d2-sfrbu
Date: Tue, 18 Nov 2025 09:38:16 +0100 [thread overview]
Message-ID: <e7f645da-0d77-4d7f-bcc6-c81e96589144@microchip.com> (raw)
In-Reply-To: <20251117-marlin-mustang-5ffda4d211c7@spud>
On 17/11/2025 at 17:29, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> The sfrbu on both sama7g5 and sama6d65 both fall back to sama5d2 in
> devicetrees, but the former two compatibles were undocumented. Now that
> syscon.yaml has easy support for multiple soc-specific compatibles, add
> both of these undocumented devices.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> CC: Nicolas Ferre <nicolas.ferre@microchip.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Thanks Conor for having added these compatibles!
Best regards,
Nicolas
> CC: Alexandre Belloni <alexandre.belloni@bootlin.com>
> CC: Claudiu Beznea <claudiu.beznea@tuxon.dev>
> CC: Lee Jones <lee@kernel.org>
> CC: Rob Herring <robh@kernel.org>
> CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
> CC: Conor Dooley <conor+dt@kernel.org>
> CC: devicetree@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: linux-arm-kernel@lists.infradead.org
> CC: linux-mediatek@lists.infradead.org
> Documentation/devicetree/bindings/mfd/syscon.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index 50f0012f4ebe..64829ecbb0b0 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -239,6 +239,12 @@ properties:
> - ti,j784s4-pcie-ctrl
> - ti,keystone-pllctrl
> - const: syscon
> + - items:
> + - enum:
> + - microchip,sama7g5-sfrbu
> + - microchip,sama7d65-sfrbu
> + - const: atmel,sama5d2-sfrbu
> + - const: syscon
> - items:
> - const: microchip,pic64gx-control-scb
> - const: microchip,mpfs-control-scb
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-11-18 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 16:29 [PATCH 1/2] dt-bindings: mfd: document control-scb and sysreg-scb on pic64gx Conor Dooley
2025-11-17 16:29 ` [PATCH 2/2] dt-bindings: mfd: document syscons falling back to atmel,sama5d2-sfrbu Conor Dooley
2025-11-17 22:45 ` Rob Herring (Arm)
2025-11-18 8:38 ` Nicolas Ferre [this message]
2025-11-17 22:44 ` [PATCH 1/2] dt-bindings: mfd: document control-scb and sysreg-scb on pic64gx Rob Herring (Arm)
2025-11-20 14:18 ` Lee Jones
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=e7f645da-0d77-4d7f-bcc6-c81e96589144@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh@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