[V3,0/3] spi: tegra quad: Add Tegra Grace features

Message

Krishna Yarlagadda June 7, 2022, 11:46 a.m. UTC

Add multiple chip select lines supported on Tegra 241

Changes in v3:
Handle review comments.
Move controller's properties to "nvidia,tegra210-quad.yaml".
Fix style errors in peripheral yaml doc.
Changes in v2:
Split Wait polling changes to be handled later
Change chip name to convention followed (Grace to 241)
Add tegra qspi peripherals yaml file

Krishna Yarlagadda (3):
  spi: tegra210-quad: Multi-cs support
  spi: dt-bindings: split peripheral prods
  spi: dt-bindings: Add compatible for Tegra241 QSPI

 ...nvidia,tegra210-quad-peripheral-props.yaml | 33 +++++++++++++++++++
 .../bindings/spi/nvidia,tegra210-quad.yaml    | 22 +------------
 .../bindings/spi/spi-peripheral-props.yaml    |  1 +
 drivers/spi/spi-tegra210-quad.c               | 33 +++++++++++++++++--
 4 files changed, 66 insertions(+), 23 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/spi/nvidia,tegra210-quad-peripheral-props.yaml

Comments

Mark Brown June 13, 2022, 5:24 p.m. UTC | #1

On Tue, 7 Jun 2022 17:16:56 +0530, Krishna Yarlagadda wrote:
> Add multiple chip select lines supported on Tegra 241
> 
> Changes in v3:
> Handle review comments.
> Move controller's properties to "nvidia,tegra210-quad.yaml".
> Fix style errors in peripheral yaml doc.
> Changes in v2:
> Split Wait polling changes to be handled later
> Change chip name to convention followed (Grace to 241)
> Add tegra qspi peripherals yaml file
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: tegra210-quad: Multi-cs support
      commit: b76134178168b5104851b3c72d9b1092b7414ff9
[2/3] spi: dt-bindings: split peripheral prods
      commit: e23917822d3cb1f5270ab0d327da713cda72f8f2
[3/3] spi: dt-bindings: Add compatible for Tegra241 QSPI
      commit: 4f37809f4cdf0cdb8d4431e779f56d1f0dec3fb5

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