linux-kernel - Re: [PATCH 1/1] spi: spi-cadence: Enable spi refclk in slave mode

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]

Date: Thu, 20 Jun 2024 21:04:26 +0100
From: Mark Brown <broonie@...nel.org>
To: Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, git@....com, 
 amitrkcian2002@...il.com
Subject: Re: [PATCH 1/1] spi: spi-cadence: Enable spi refclk in slave mode

On Mon, 17 Jun 2024 21:08:37 +0530, Amit Kumar Mahapatra wrote:
> When spi-cadence is configured as a slave, it requires the SPI refclk to
> detect the synchronization start condition while communicating with the
> master. However, the spi-cadence driver never enables the SPI refclk in
> slave mode, causing the refclk to remain disabled if the
> "clk_ignore_unused" kernel parameter is not passed through bootargs.
> As a result, the slave cannot detect data sent by the master, leading to
> communication failure. Update driver to enable the SPI refclk in both
> master and slave configurations.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-cadence: Enable spi refclk in slave mode
      commit: 78b05172b42d14a4c6fc6b75b31590b8977900dc

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