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: <29a888dc-b523-4140-2e5c-c322fc4ad49d@ti.com>
Date:   Tue, 21 Mar 2023 12:29:42 +0530
From:   Vaishnav Achath <vaishnav.a@...com>
To:     Nishanth Menon <nm@...com>
CC:     <vigneshr@...com>, <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <j-keerthy@...com>, <u-kumar1@...com>
Subject: Re: [PATCH 0/8] arm64: dts: ti: j7: Add device-tree nodes for MCSPI

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

-- 
Regards,
Vaishnav

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ