[0/8] arm64: dts: ti: j7: Add device-tree nodes for MCSPI

Message ID 20230320053022.11093-1-vaishnav.a@ti.com
Headers
Series arm64: dts: ti: j7: Add device-tree nodes for MCSPI |

Message

Vaishnav Achath March 20, 2023, 5:30 a.m. UTC
  This series adds device tree nodes for Multi Channel Serial Peripheral
Interface (MCSPI) on J721E, J7200, J721S2 and J784S4 platforms. All the
MCSPI instances are disabled by default and can be enabled through overlays
as required, the changes were tested using spidev loopback test for all
instances and the data verified only for main_spi4 which is connected
internally as slave to mcu_spi2 for all existing J7 devices.

Vaishnav Achath (8):
  arm64: dts: ti: k3-j721e-main: Add MCSPI nodes
  arm64: dts: ti: k3-j721e-mcu-wakeup: Add MCSPI nodes
  arm64: dts: ti: k3-j7200-main: Add MCSPI nodes
  arm64: dts: ti: k3-j7200-mcu-wakeup: Add MCSPI nodes
  arm64: dts: ti: k3-j721s2-main: Add MCSPI nodes
  arm64: dts: ti: k3-j721s2-mcu-wakeup: Add MCSPI nodes
  arm64: dts: ti: k3-j784s4-main: Add MCSPI nodes
  arm64: dts: ti: k3-j784s4-mcu-wakeup: Add MCSPI nodes

 arch/arm64/boot/dts/ti/k3-j7200-main.dtsi     | 88 +++++++++++++++++++
 .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi      | 33 +++++++
 arch/arm64/boot/dts/ti/k3-j721e-main.dtsi     | 88 +++++++++++++++++++
 .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi      | 33 +++++++
 arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi    | 88 +++++++++++++++++++
 .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi     | 33 +++++++
 arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi    | 88 +++++++++++++++++++
 .../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi     | 33 +++++++
 8 files changed, 484 insertions(+)
  

Comments

Nishanth Menon March 20, 2023, 3:16 p.m. UTC | #1
On 11:00-20230320, Vaishnav Achath wrote:
> This series adds device tree nodes for Multi Channel Serial Peripheral
> Interface (MCSPI) on J721E, J7200, J721S2 and J784S4 platforms. All the
> MCSPI instances are disabled by default and can be enabled through overlays
> as required, the changes were tested using spidev loopback test for all
> instances and the data verified only for main_spi4 which is connected
> internally as slave to mcu_spi2 for all existing J7 devices.
> 
> Vaishnav Achath (8):
>   arm64: dts: ti: k3-j721e-main: Add MCSPI nodes
>   arm64: dts: ti: k3-j721e-mcu-wakeup: Add MCSPI nodes
>   arm64: dts: ti: k3-j7200-main: Add MCSPI nodes
>   arm64: dts: ti: k3-j7200-mcu-wakeup: Add MCSPI nodes
>   arm64: dts: ti: k3-j721s2-main: Add MCSPI nodes
>   arm64: dts: ti: k3-j721s2-mcu-wakeup: Add MCSPI nodes
>   arm64: dts: ti: k3-j784s4-main: Add MCSPI nodes
>   arm64: dts: ti: k3-j784s4-mcu-wakeup: Add MCSPI nodes

Why split the patches per bus? why not club the patches at SoC level?
  
Vaishnav Achath March 21, 2023, 6:59 a.m. UTC | #2
Hi Nishanth,

On 20/03/23 20:46, Nishanth Menon wrote:
> On 11:00-20230320, Vaishnav Achath wrote:
>> This series adds device tree nodes for Multi Channel Serial Peripheral
>> Interface (MCSPI) on J721E, J7200, J721S2 and J784S4 platforms. All the
>> MCSPI instances are disabled by default and can be enabled through overlays
>> as required, the changes were tested using spidev loopback test for all
>> instances and the data verified only for main_spi4 which is connected
>> internally as slave to mcu_spi2 for all existing J7 devices.
>>
>> Vaishnav Achath (8):
>>   arm64: dts: ti: k3-j721e-main: Add MCSPI nodes
>>   arm64: dts: ti: k3-j721e-mcu-wakeup: Add MCSPI nodes
>>   arm64: dts: ti: k3-j7200-main: Add MCSPI nodes
>>   arm64: dts: ti: k3-j7200-mcu-wakeup: Add MCSPI nodes
>>   arm64: dts: ti: k3-j721s2-main: Add MCSPI nodes
>>   arm64: dts: ti: k3-j721s2-mcu-wakeup: Add MCSPI nodes
>>   arm64: dts: ti: k3-j784s4-main: Add MCSPI nodes
>>   arm64: dts: ti: k3-j784s4-mcu-wakeup: Add MCSPI nodes
> 
> Why split the patches per bus? why not club the patches at SoC level?
> 

I split them initially since the changes were in two different files, I have
combined the changes at SoC level and send a V2,

https://lore.kernel.org/all/20230321065447.6997-1-vaishnav.a@ti.com/#r