From: Mark Brown <broonie@kernel.org>
To: Michael Walle <michael@walle.cc>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Yogesh Gaur <yogeshgaur.83@gmail.com>,
Kuldeep Singh <kuldeep.singh@nxp.com>,
Ashish Kumar <ashish.kumar@nxp.com>
Subject: Re: [PATCH] spi: spi-nxp-fspi: don't depend on a specific node name erratum workaround
Date: Sat, 2 Oct 2021 02:37:05 +0100 [thread overview]
Message-ID: <163313862170.2275998.17835551600191166035.b4-ty@kernel.org> (raw)
In-Reply-To: <20211001212726.159437-1-michael@walle.cc>
On Fri, 1 Oct 2021 23:27:26 +0200, Michael Walle wrote:
> In commit 7e71b85473f8 ("arm64: dts: ls1028a: fix node name for the
> sysclk") the sysclk node name was renamed and broke the erratum
> workaround because it tries to fetch a device tree node by its name,
> which is very fragile in general. We don't even need the sysclk node
> because the only possible sysclk frequency input is 100MHz. In fact, the
> erratum says it applies if SYS_PLL_RAT is 3, not that the platform clock
> is 300 MHz. Make the workaround more reliable and just drop the unneeded
> sysclk lookup.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-nxp-fspi: don't depend on a specific node name erratum workaround
commit: 67a12ae52599c9f2f24ef14adb43fc3b164792b5
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
next prev parent reply other threads:[~2021-10-02 1:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 21:27 [PATCH] spi: spi-nxp-fspi: don't depend on a specific node name erratum workaround Michael Walle
2021-10-02 1:37 ` Mark Brown [this message]
2021-10-02 1:37 ` Vladimir Oltean
2021-10-02 8:58 ` Michael Walle
2021-10-02 9:23 ` Vladimir Oltean
2021-10-02 9:34 ` Michael Walle
2021-10-02 9:55 ` Vladimir Oltean
2021-10-02 12:41 ` Michael Walle
2021-10-04 10:53 ` Kuldeep Singh
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=163313862170.2275998.17835551600191166035.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=ashish.kumar@nxp.com \
--cc=kuldeep.singh@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@walle.cc \
--cc=vladimir.oltean@nxp.com \
--cc=yogeshgaur.83@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.