From: Mark Brown <broonie@kernel.org>
To: Ikjoon Jang <ikjn@chromium.org>,
Bayi Cheng <bayi.cheng@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2] spi: spi-mtk-nor: Optimize timeout for dma read
Date: Tue, 15 Nov 2022 09:57:00 +0000 [thread overview]
Message-ID: <166850622037.114886.18108936961480983517.b4-ty@kernel.org> (raw)
In-Reply-To: <20221114081327.25750-1-bayi.cheng@mediatek.com>
On Mon, 14 Nov 2022 16:13:27 +0800, Bayi Cheng wrote:
> From: bayi cheng <bayi.cheng@mediatek.com>
>
> The timeout value of the current dma read is unreasonable. For example,
> If the spi flash clock is 26Mhz, It will takes about 1.3ms to read a
> 4KB data in spi mode. But the actual measurement exceeds 50s when a
> dma read timeout is encountered.
>
> [...]
Applied to
broonie/spi.git for-next
Thanks!
[1/1] spi: spi-mtk-nor: Optimize timeout for dma read
commit: d52a826b40604387d3e24b54e12e404867902fbb
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-11-15 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 8:13 [PATCH v2] spi: spi-mtk-nor: Optimize timeout for dma read Bayi Cheng
2022-11-14 11:32 ` AngeloGioacchino Del Regno
2022-11-15 9:57 ` 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=166850622037.114886.18108936961480983517.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=bayi.cheng@mediatek.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