From: Li Yang <leoyang.li@nxp.com>
To: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Li Yang <leoyang.li@nxp.com>
Subject: [PATCH v3 0/2] convert ifc binding to yaml and drop "simple-bus"
Date: Tue, 16 Nov 2021 15:18:44 -0600 [thread overview]
Message-ID: <20211116211846.16335-1-leoyang.li@nxp.com> (raw)
Convert the ifc binding to yaml schema, in the mean while remove the
"simple-bus" compatible from the binding to make sure ifc device probes
before any of the child devices. Update the driver accordingly.
DTS changes should be submitted after binding/driver changes are merged.
Changes in v3:
- Rebased to v5.16-rc1
Changes in v2:
- Update endian property to type boolean
- Remove example subnodes that don't have yaml binding
- Spin DTS patches into a different series
Li Yang (2):
dt-bindings: memory: fsl: convert ifc binding to yaml schema
memory: fsl_ifc: populate child devices without relying on simple-bus
.../memory-controllers/fsl/fsl,ifc.yaml | 113 ++++++++++++++++++
.../bindings/memory-controllers/fsl/ifc.txt | 82 -------------
drivers/memory/fsl_ifc.c | 7 ++
3 files changed, 120 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
--
2.25.1
next reply other threads:[~2021-11-16 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 21:18 Li Yang [this message]
2021-11-16 21:18 ` [PATCH v3 1/2] dt-bindings: memory: fsl: convert ifc binding to yaml schema Li Yang
2021-11-16 21:18 ` [PATCH v3 2/2] memory: fsl_ifc: populate child devices without relying on simple-bus Li Yang
2021-11-17 9:13 ` [PATCH v3 0/2] convert ifc binding to yaml and drop "simple-bus" Krzysztof Kozlowski
2021-11-17 9:15 ` 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=20211116211846.16335-1-leoyang.li@nxp.com \
--to=leoyang.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).