Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     Matthias Brugger <matthias.bgg@gmail.com>,
        Mason Zhang <mason.zhang@mediatek.com>
Cc:     Mark Brown <broonie@kernel.org>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        Mason Zhang <Mason.Zhang@mediatek.com>,
        linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com,
        linux-spi@vger.kernel.org, leilk.liu@mediatek.com
Subject: Re: [PATCH 1/2] spi: mediatek: add no_need_unprepare support
Date:   Mon, 12 Jul 2021 11:45:43 +0100
Message-Id: <162608669456.4543.1877349027408478150.b4-ty@kernel.org>
In-Reply-To: <20210629100814.21402-1-mason.zhang@mediatek.com>
References: <20210629100814.21402-1-mason.zhang@mediatek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 29 Jun 2021 18:08:15 +0800, Mason Zhang wrote:
> This patch add no_need_unprepare support for spi, if spi src clk is
> MAIN PLL, it can keep the clk_prepare and will not cause low power
> issue. So we no need do clk_prepare/clk_unprepare in runtime pm,
> and it will get better performance, because clk_prepare has called
> mutex lock.
> In the same way,
> clk_get_rate also has called mutex lock, so we moved it to spi_probe.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/2] spi: mediatek: add no_need_unprepare support
      commit: 162a31effc4182dd5a0675d9fd0336d5096e0ad3

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark