Add QPIC SPI NAND support for IPQ5018

[PATCH 0/2] Add QPIC SPI NAND support for IPQ5018

Posted by George Moussalem via B4 Relay 9 months, 2 weeks ago

Add support for the QPIC SPI NAND controller found in IPQ5018 which is 
the same as the one found in IPQ5018.

Signed-off-by: George Moussalem <george.moussalem@outlook.com>
---
George Moussalem (2):
      dt-bindings: spi: spi-qpic-snand: Add IPQ5018 compatible
      arm64: dts: qcom: ipq5018: Add SPI nand support

 .../bindings/spi/qcom,spi-qpic-snand.yaml          |  8 +++--
 arch/arm64/boot/dts/qcom/ipq5018.dtsi              | 38 ++++++++++++++++++++++
 2 files changed, 44 insertions(+), 2 deletions(-)
---
base-commit: 8a2d53ce3c5f82683ad3df9a9a55822816fe64e7
change-id: 20250501-ipq5018-spi-qpic-snand-94965e899233

Best regards,
-- 
George Moussalem <george.moussalem@outlook.com>

Re: (subset) [PATCH 0/2] Add QPIC SPI NAND support for IPQ5018

Posted by Bjorn Andersson 6 months ago

On Thu, 01 May 2025 13:20:50 +0400, George Moussalem wrote:
> Add support for the QPIC SPI NAND controller found in IPQ5018 which is
> the same as the one found in IPQ5018.
> 
> 

Applied, thanks!

[2/2] arm64: dts: qcom: ipq5018: Add SPI nand support
      commit: 8d2a8e8dc448f218b36b3b9f3790c9c0dfaa2b74

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

Re: (subset) [PATCH 0/2] Add QPIC SPI NAND support for IPQ5018

Posted by Mark Brown 9 months, 1 week ago

On Thu, 01 May 2025 13:20:50 +0400, George Moussalem wrote:
> Add support for the QPIC SPI NAND controller found in IPQ5018 which is
> the same as the one found in IPQ5018.
> 
> 

Applied to

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

Thanks!

[1/2] dt-bindings: spi: spi-qpic-snand: Add IPQ5018 compatible
      commit: 2dbe74c63cb73829be0aab0d0e7e68b87071b5fa

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