linux-kernel - Re: [PATCH] spi: spi-geni-qcom: Don't set the cs if it was already right

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <159345952500.3556.3923328803896561754.b4-ty@kernel.org>
Date:   Mon, 29 Jun 2020 20:38:50 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Douglas Anderson <dianders@...omium.org>
Cc:     Andy Gross <agross@...nel.org>, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org, Dilip Kota <dkota@...eaurora.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-arm-msm@...r.kernel.org, swboyd@...omium.org
Subject: Re: [PATCH] spi: spi-geni-qcom: Don't set the cs if it was already right

On Fri, 26 Jun 2020 15:19:50 -0700, Douglas Anderson wrote:
> Setting the chip select on the Qualcomm geni SPI controller isn't
> exactly cheap.  Let's cache the current setting and avoid setting the
> chip select if it's already right.
> 
> Using "flashrom" to read or write the EC firmware on a Chromebook
> shows roughly a 25% reduction in interrupts and a 15% speedup.

Applied to

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

Thanks!

[1/1] spi: spi-geni-qcom: Don't set the cs if it was already right
      commit: 638d8488ae00d2e5dd5033804e82b458d3cf85b1

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