From: Mark Brown <broonie@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Ikjoon Jang <ikjn@chromium.org>,
Bayi Cheng <bayi.cheng@mediatek.com>
Cc: linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Chuanhong Guo <gch981213@gmail.com>,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v2] spi: spi-mtk-nor: Add recovery mechanism for dma read timeout
Date: Wed, 07 Dec 2022 16:21:06 +0000 [thread overview]
Message-ID: <167043006609.286366.2467608192853584896.b4-ty@kernel.org> (raw)
In-Reply-To: <20221207055435.30557-1-bayi.cheng@mediatek.com>
On Wed, 07 Dec 2022 13:54:35 +0800, Bayi Cheng wrote:
> The state machine of MTK spi nor controller may be disturbed by some
> glitch signals from the relevant BUS during dma read, Although the
> possibility of causing the dma read to fail is next to nothing,
> However, if error-handling is not implemented, which makes the feature
> somewhat risky.
>
> Add an error-handling mechanism here, reset the state machine and
> re-read the data when an error occurs.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-mtk-nor: Add recovery mechanism for dma read timeout
commit: 8330e9e8269bb76dd502e84efb5f351016512cf8
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
prev parent reply other threads:[~2022-12-07 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 5:54 [PATCH v2] spi: spi-mtk-nor: Add recovery mechanism for dma read timeout Bayi Cheng
2022-12-07 13:21 ` AngeloGioacchino Del Regno
2022-12-07 16:21 ` Mark Brown [this message]
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=167043006609.286366.2467608192853584896.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=bayi.cheng@mediatek.com \
--cc=gch981213@gmail.com \
--cc=ikjn@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox