Adds support for SPI controller found in Tesla FSD SoC

- Changes since v2
* Addressed review comments of Andi
* rebased on Krzysztof's v6 spi schema changes
* Added tags

-Changes since v1
* Splited SPI changes from a larger inital patch set
* Rebased on Krzysztof's latest (v5) SPI schema changes
* Added tag

Note: This series is depended on [1] patches which adds
support of FSD SoC and on Krzysztof's v6 [2] of spi schema changes

[1] https://lkml.org/lkml/2022/1/24/583
[2] https://lkml.org/lkml/2022/1/24/120


Alim Akhtar (2):
  spi: dt-bindings: samsung: Add fsd spi compatible
  spi: s3c64xx: Add spi port configuration for Tesla FSD SoC

Aswani Reddy (1):
  arm64: dts: fsd: Add SPI device nodes

 .../devicetree/bindings/spi/samsung,spi.yaml  |  1 +
 arch/arm64/boot/dts/tesla/fsd.dtsi            | 57 +++++++++++++++++++
 drivers/spi/spi-s3c64xx.c                     | 13 +++++
 3 files changed, 71 insertions(+)

-- 
2.25.1

On Tue, Jan 25, 2022 at 08:46:01AM +0530, Alim Akhtar wrote:

> Note: This series is depended on [1] patches which adds
> support of FSD SoC and on Krzysztof's v6 [2] of spi schema changes
> 
> [1] https://lkml.org/lkml/2022/1/24/583
> [2] https://lkml.org/lkml/2022/1/24/120

Please resend this when it can be applied, either wait until the
dependencies are in place or rebase on top of current code.  In general
only build time dependencies matter here, the SoC support being merged
shouldn't be an issue one way or another.

Hi Mark and Lee Jones

>-----Original Message-----
>From: Mark Brown [mailto:broonie@kernel.org]
>Sent: Tuesday, January 25, 2022 7:25 PM
>To: Alim Akhtar <alim.akhtar@samsung.com>
>Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
>devicetree@vger.kernel.org; linus.walleij@linaro.org; robh+dt@kernel.org;
>krzysztof.kozlowski@canonical.com; linux-samsung-soc@vger.kernel.org;
>pankaj.dubey@samsung.com; andi@etezian.org; linux-spi@vger.kernel.org
>Subject: Re: [PATCH v3 0/3] Add FSD SPI support
>
>On Tue, Jan 25, 2022 at 08:46:01AM +0530, Alim Akhtar wrote:
>
>> Note: This series is depended on [1] patches which adds support of FSD
>> SoC and on Krzysztof's v6 [2] of spi schema changes
>>
>> [1]
>> https://protect2.fireeye.com/v1/url?k=43e76061-1c7c5970-43e6eb2e-0cc47
>> a31cdbc-d2d9ba5a4358198f&q=1&e=9e61db9b-cfb7-4110-a13c-
>a1cb0d92a251&u=
>> https%3A%2F%2Flkml.org%2Flkml%2F2022%2F1%2F24%2F583
>> [2]
>> https://protect2.fireeye.com/v1/url?k=e2ddfc2b-bd46c53a-e2dc7764-0cc47
>> a31cdbc-0d6dbb90b0110bab&q=1&e=9e61db9b-cfb7-4110-a13c-
>a1cb0d92a251&u=
>> https%3A%2F%2Flkml.org%2Flkml%2F2022%2F1%2F24%2F120
>
>Please resend this when it can be applied, either wait until the
dependencies
>are in place or rebase on top of current code.  In general only build time
>dependencies matter here, the SoC support being merged shouldn't be an
>issue one way or another.

I re-send these patches (couple of them) as I see the dependencies has
landed into MFD tree.
Because of the immutable branch between MFD, SPI and DT due to the current
merge window, I assume this will go via MFD tree. Let me know if any
concerns. 
Thanks!

On Tue, 25 Jan 2022 08:46:01 +0530, Alim Akhtar wrote:
> Adds support for SPI controller found in Tesla FSD SoC
> 
> - Changes since v2
> * Addressed review comments of Andi
> * rebased on Krzysztof's v6 spi schema changes
> * Added tags
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: dt-bindings: samsung: Add fsd spi compatible
      commit: 363d3c51bc5b3243b5b035a1f50d6d994a1b203f
[2/3] spi: s3c64xx: Add spi port configuration for Tesla FSD SoC
      commit: 4ebb15a15799da4954f1d4926fcd3263ea46e417

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