devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	sboyd@kernel.org, mturquette@baylibre.com, shawnguo@kernel.org,
	s.hauer@pengutronix.de
Cc: aisheng.dong@nxp.com, l.stach@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V4 4/7] soc: imx: add i.MX93 SRC power domain driver
Date: Thu, 9 Jun 2022 07:06:12 -0700	[thread overview]
Message-ID: <098e206c-8c52-747c-6261-e7ef96df2652@infradead.org> (raw)
In-Reply-To: <20220609125100.3496633-5-peng.fan@oss.nxp.com>



On 6/9/22 05:50, Peng Fan (OSS) wrote:
> diff --git a/drivers/soc/imx/Kconfig b/drivers/soc/imx/Kconfig
> index a840494e849a..5bfc1dfea28b 100644
> --- a/drivers/soc/imx/Kconfig
> +++ b/drivers/soc/imx/Kconfig
> @@ -20,4 +20,14 @@ config SOC_IMX8M
>  	  support, it will provide the SoC info like SoC family,
>  	  ID and revision etc.
>  
> +config SOC_IMX9
> +	tristate "i.MX9 SoC family support"
> +	depends on ARCH_MXC || COMPILE_TEST
> +	default ARCH_MXC && ARM64
> +	select SOC_BUS
> +	select PM_GENERIC_DOMAINS
> +	help
> +	  If you say yes here you get support for the NXP i.MX9 family
> +	  support.

One too many "support". Maybe:

> +	help
> +	  If you say yes here you get support for the NXP i.MX9 SoC family.



-- 
~Randy

  reply	other threads:[~2022-06-09 14:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 12:50 [PATCH V4 0/7] imx: support i.MX93 SRC and mediamix blk ctrl Peng Fan (OSS)
2022-06-09 12:50 ` [PATCH V4 1/7] dt-bindings: soc: add i.MX93 SRC Peng Fan (OSS)
2022-06-14 21:39   ` Rob Herring
2022-06-14 23:22     ` Peng Fan
2022-06-15  1:37       ` Rob Herring
2022-06-15  3:51         ` Peng Fan
2022-06-09 12:50 ` [PATCH V4 2/7] dt-bindings: soc: add i.MX93 mediamix blk ctrl Peng Fan (OSS)
2022-06-09 12:50 ` [PATCH V4 3/7] clk: export of_clk_bulk_get_all Peng Fan (OSS)
2022-06-10  9:02   ` Peng Fan (OSS)
2022-07-04  1:05     ` Peng Fan (OSS)
2022-06-09 12:50 ` [PATCH V4 4/7] soc: imx: add i.MX93 SRC power domain driver Peng Fan (OSS)
2022-06-09 14:06   ` Randy Dunlap [this message]
2022-06-10  2:11     ` Peng Fan
2022-06-09 12:50 ` [PATCH V4 5/7] soc: imx: add i.MX93 media blk ctrl driver Peng Fan (OSS)
2022-06-09 12:50 ` [PATCH V4 6/7] arm64: dts: imx93: add src node Peng Fan (OSS)
2022-06-09 12:51 ` [PATCH V4 7/7] arm64: dts: imx93: add mediamix blk ctrl node 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=098e206c-8c52-747c-6261-e7ef96df2652@infradead.org \
    --to=rdunlap@infradead.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=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --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).