linux-kernel - Re: [PATCH 1/2] spi: spi-mem: add spi_mem_dtr_supports

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 for Android: free password hash cracker in your pocket

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

Message-Id: <161306077271.51686.18172352701549316815.b4-ty@kernel.org>
Date:   Thu, 11 Feb 2021 16:26:12 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
        Pratyush Yadav <p.yadav@...com>
Cc:     zhengxunli@...c.com.tw, Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: [PATCH 1/2] spi: spi-mem: add spi_mem_dtr_supports_op()

On Thu, 4 Feb 2021 19:42:17 +0530, Pratyush Yadav wrote:
> spi_mem_default_supports_op() rejects DTR ops by default to ensure that
> the controller drivers that haven't been updated with DTR support
> continue to reject them. It also makes sure that controllers that don't
> support DTR mode at all (which is most of them at the moment) also
> reject them.
> 
> This means that controller drivers that want to support DTR mode can't
> use spi_mem_default_supports_op(). Driver authors have to roll their own
> supports_op() function and mimic the buswidth checks. See
> spi-cadence-quadspi.c for example. Or even worse, driver authors might
> skip it completely or get it wrong.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: spi-mem: add spi_mem_dtr_supports_op()
      commit: 539cf68cd51bfcd2987ce1c44e628e9da69de7c8
[2/2] spi: cadence-quadspi: Use spi_mem_dtr_supports_op()
      commit: d2275139649bc34b8b5c3e33d26d991ab8a1364c

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