linux-kernel - Re: [PATCH v2] spi: spi-mtk-nor: Optimize timeout for dma read

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <166850622037.114886.18108936961480983517.b4-ty@kernel.org>
Date:   Tue, 15 Nov 2022 09:57:00 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Ikjoon Jang <ikjn@...omium.org>,
        Bayi Cheng <bayi.cheng@...iatek.com>,
        Matthias Brugger <matthias.bgg@...il.com>
Cc:     Project_Global_Chrome_Upstream_Group@...iatek.com,
        linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH v2] spi: spi-mtk-nor: Optimize timeout for dma read

On Mon, 14 Nov 2022 16:13:27 +0800, Bayi Cheng wrote:
> From: bayi cheng <bayi.cheng@...iatek.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