public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel•org>
To: Dario Binacchi <dario.binacchi@amarulasolutions•com>
Cc: linux-kernel@vger•kernel.org,
	Michael Trimarchi <michael@amarulasolutions•com>,
	Fabio Estevam <festevam@gmail•com>,
	NXP Linux Team <linux-imx@nxp•com>,
	Pengutronix Kernel Team <kernel@pengutronix•de>,
	Rob Herring <robh+dt@kernel•org>,
	Sascha Hauer <s.hauer@pengutronix•de>,
	Stephen Boyd <sboyd@kernel•org>,
	devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org
Subject: Re: [RFC PATCH v3 1/4] ARM: dts: imx28: reparent gpmi clock to ref_gpmi
Date: Sat, 29 Jan 2022 13:46:30 +0800	[thread overview]
Message-ID: <20220129054629.GP4686@dragon> (raw)
In-Reply-To: <20220117161755.1863579-2-dario.binacchi@amarulasolutions.com>

On Mon, Jan 17, 2022 at 05:17:52PM +0100, Dario Binacchi wrote:
> Since ref_gpmi is sourced from pll0 (480MHz), It allows the GPMI
> controller to manage High-Speed ​​NAND Timing (edo mode 3,4 and 5).
> 
> Co-developed-by: Michael Trimarchi <michael@amarulasolutions•com>
> Signed-off-by: Michael Trimarchi <michael@amarulasolutions•com>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions•com>

Applied, thanks!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-01-29  5:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 16:17 [RFC PATCH v3 0/4] Fix and improve gpmi nand on mx28 Dario Binacchi
2022-01-17 16:17 ` [RFC PATCH v3 1/4] ARM: dts: imx28: reparent gpmi clock to ref_gpmi Dario Binacchi
2022-01-29  5:46   ` Shawn Guo [this message]
2022-01-18  8:34 ` [RFC PATCH v3 0/4] Fix and improve gpmi nand on mx28 Sascha Hauer

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=20220129054629.GP4686@dragon \
    --to=shawnguo@kernel$(echo .)org \
    --cc=dario.binacchi@amarulasolutions$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=festevam@gmail$(echo .)com \
    --cc=kernel@pengutronix$(echo .)de \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-imx@nxp$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=michael@amarulasolutions$(echo .)com \
    --cc=robh+dt@kernel$(echo .)org \
    --cc=s.hauer@pengutronix$(echo .)de \
    --cc=sboyd@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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