From: Rob Herring <robh@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: memory: fsl: convert ifc binding to yaml schema
Date: Tue, 26 Oct 2021 16:17:13 -0500 [thread overview]
Message-ID: <YXhwWR7fDrv9L+mY@robh.at.kernel.org> (raw)
In-Reply-To: <20211015005707.1996-2-leoyang.li@nxp.com>
On Thu, 14 Oct 2021 19:57:06 -0500, Li Yang wrote:
> Convert the txt binding to yaml format and add description. Drop the
> "simple-bus" compatible string from the example and not allowed by the
> binding any more. This will help to enforce the correct probe order
> between parent device and child devices, but will require the ifc driver
> to probe the child devices to work properly.
>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
> ---
> .../memory-controllers/fsl/fsl,ifc.yaml | 113 ++++++++++++++++++
> .../bindings/memory-controllers/fsl/ifc.txt | 82 -------------
> 2 files changed, 113 insertions(+), 82 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/memory-controllers/fsl/fsl,ifc.yaml
> delete mode 100644 Documentation/devicetree/bindings/memory-controllers/fsl/ifc.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-10-26 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 0:57 [PATCH v2 0/2] convert ifc binding to yaml and drop "simple-bus" Li Yang
2021-10-15 0:57 ` [PATCH v2 1/2] dt-bindings: memory: fsl: convert ifc binding to yaml schema Li Yang
2021-10-26 21:17 ` Rob Herring [this message]
2021-10-15 0:57 ` [PATCH v2 2/2] memory: fsl_ifc: populate child devices without relying on simple-bus Li Yang
2021-11-16 10:35 ` Krzysztof Kozlowski
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=YXhwWR7fDrv9L+mY@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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