From: "Rob Herring (Arm)" <robh@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
devicetree@vger.kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/1] dt-bindings: soc: add vf610 reboot syscon controller
Date: Tue, 19 Aug 2025 16:06:07 -0500 [thread overview]
Message-ID: <175563756689.1312101.13704825031197649543.robh@kernel.org> (raw)
In-Reply-To: <20250819165317.3739366-1-Frank.Li@nxp.com>
On Tue, 19 Aug 2025 12:53:16 -0400, Frank Li wrote:
> Add vf610 reboot controller, which used to reboot whole system. Fix below
> CHECK_DTB warnings:
>
> arch/arm/boot/dts/nxp/vf/vf610-bk4.dtb: /soc/bus@40000000/src@4006e000:
> failed to match any schema with compatible: ['fsl,vf610-src', 'syscon']
>
> IC reference manual calls it as system reset controller(SRC), but it is not
> module as reset controller, which used to reset individual device. SRC
> works as reboot controller, which reboots whole system. It provides a
> syscon interface to syscon-reboot.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> change in v3
> - add missed 's' at description
> - remove duplicate / at path
>
> Change in v2
> - change description to avoid confuse about reset controller.
> - it is legacy device, more than 10 year. So try keep existed dts as it.
> ---
> .../bindings/soc/fsl/fsl,vf610-src.yaml | 47 +++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/fsl/fsl,vf610-src.yaml
>
Applied, thanks!
prev parent reply other threads:[~2025-08-19 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 16:53 [PATCH v3 1/1] dt-bindings: soc: add vf610 reboot syscon controller Frank Li
2025-08-19 21:06 ` Rob Herring (Arm) [this message]
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=175563756689.1312101.13704825031197649543.robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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