linux-kernel - Re: [PATCH] spi: fsl-dspi: add cs-gpios support

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: <166868570908.694164.13311249993591941854.b4-ty@kernel.org>
Date:   Thu, 17 Nov 2022 11:48:29 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Vladimir Oltean <vladimir.oltean@....com>,
        linux-spi@...r.kernel.org
Cc:     Vladimir Oltean <olteanv@...il.com>, linux-kernel@...r.kernel.org,
        "Radu Pirea (NXP OSS)" <radu-nicolae.pirea@....nxp.com>
Subject: Re: [PATCH] spi: fsl-dspi: add cs-gpios support

On Fri, 11 Nov 2022 23:13:56 +0200, Vladimir Oltean wrote:
> From: "Radu Pirea (NXP OSS)" <radu-nicolae.pirea@....nxp.com>
> 
> Make the driver be able to bit-bang a GPIO for the Chip Select pin of
> select peripherals.
> 
> The GPIO value is driven by the driver in that case, and none of the
> hardware Chip Select bits will be populated in the PUSHR register for
> the TX commands constructed for this peripheral.
> 
> [...]

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: fsl-dspi: add cs-gpios support
      commit: 84b60f2bce1f0416617c4dbc015b5da906b8e2ad

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