devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kernel@pengutronix.de,
	festevam@gmail.com, linux-imx@nxp.com, aisheng.dong@nxp.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V3 1/8] dt-bindings: soc: imx: add binding for i.MX93 syscon
Date: Fri, 2 Sep 2022 15:57:21 -0500	[thread overview]
Message-ID: <20220902205721.GA399775-robh@kernel.org> (raw)
In-Reply-To: <20220831141418.38532-2-peng.fan@oss.nxp.com>

On Wed, Aug 31, 2022 at 10:14:11PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
> 
> Add binding doc for i.MX93 blk_ctrl_ns_aonmix and blk_ctrl_wakeupmix

Is this complete or you expect to add to it? If complete, just add the 
compatible strings to syscon.yaml. If not complete, why not?

Rob

  reply	other threads:[~2022-09-02 20:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 14:14 [PATCH V3 0/8] arm64: dts: imx93: add several nodes Peng Fan (OSS)
2022-08-31 14:14 ` [PATCH V3 1/8] dt-bindings: soc: imx: add binding for i.MX93 syscon Peng Fan (OSS)
2022-09-02 20:57   ` Rob Herring [this message]
2022-09-05  0:57     ` Peng Fan
2022-08-31 14:14 ` [PATCH V3 2/8] arm64: dts: imx93: correct SDHC clk entry Peng Fan (OSS)
2022-08-31 14:14 ` [PATCH V3 3/8] arm64: dts: imx93: add gpio clk Peng Fan (OSS)
2022-08-31 14:14 ` [PATCH V3 4/8] arm64: dts: imx93: add s4 mu node Peng Fan (OSS)
2022-09-05  3:05   ` Shawn Guo
2022-08-31 14:14 ` [PATCH V3 5/8] arm64: dts: imx93: add blk ctrl node Peng Fan (OSS)
2022-08-31 14:14 ` [PATCH V3 6/8] arm64: dts: imx93: add a55 pmu Peng Fan (OSS)
2022-08-31 14:14 ` [PATCH V3 7/8] arm64: dts: imx93: add lpi2c nodes Peng Fan (OSS)
2022-08-31 14:14 ` [PATCH V3 8/8] arm64: dts: imx93: add lpspi nodes Peng Fan (OSS)

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=20220902205721.GA399775-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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).