Message ID | 20250214054702.1073139-1-parvathi@couthit.com (mailing list archive) |
---|---|
Headers | show |
Series | PRU-ICSSM Ethernet Driver | expand |
On Fri, 14 Feb 2025 11:16:52 +0530 parvathi wrote: > The Programmable Real-Time Unit Industrial Communication Sub-system (PRU-ICSS) > is available on the TI SOCs in two flavors: Gigabit ICSS (ICSSG) and the older > Megabit ICSS (ICSSM). Every individual patch must build cleanly with W=1. Otherwise doing git bisections is a miserable experience.
Hi, > On Fri, 14 Feb 2025 11:16:52 +0530 parvathi wrote: >> The Programmable Real-Time Unit Industrial Communication Sub-system (PRU-ICSS) >> is available on the TI SOCs in two flavors: Gigabit ICSS (ICSSG) and the older >> Megabit ICSS (ICSSM). > > Every individual patch must build cleanly with W=1. > Otherwise doing git bisections is a miserable experience. > -- As we mentioned in cover letter we have dependency with SOC patch. "These patches have a dependency on an SOC patch, which we are including at the end of this series for reference. The SOC patch has been submitted in a separate thread [2] and we are awaiting for it to be merged." SOC patch need to be applied prior applying the "net" patches. We have changed the order and appended the SOC patch at the end, because SOC changes need to go into linux-next but not into net-next. We have make sure every individual patch has compiled successfully with W=1 if we apply SOC patch prior to the "net" patches. Thanks and Regards, Parvathi.
On Tue, 18 Feb 2025 15:36:20 +0530 (IST) Parvathi Pudi wrote: > > On Fri, 14 Feb 2025 11:16:52 +0530 parvathi wrote: > >> The Programmable Real-Time Unit Industrial Communication Sub-system (PRU-ICSS) > >> is available on the TI SOCs in two flavors: Gigabit ICSS (ICSSG) and the older > >> Megabit ICSS (ICSSM). > > > > Every individual patch must build cleanly with W=1. > > Otherwise doing git bisections is a miserable experience. > > -- > > As we mentioned in cover letter we have dependency with SOC patch. > > "These patches have a dependency on an SOC patch, which we are including at the > end of this series for reference. The SOC patch has been submitted in a separate > thread [2] and we are awaiting for it to be merged." > > SOC patch need to be applied prior applying the "net" patches. We have changed the > order and appended the SOC patch at the end, because SOC changes need to go into > linux-next but not into net-next. > > We have make sure every individual patch has compiled successfully with W=1 if we > apply SOC patch prior to the "net" patches. Please resubmit after the merge window.
Hi Parvathi, On 18/02/25 3:36 pm, Parvathi Pudi wrote: > > Hi, > >> On Fri, 14 Feb 2025 11:16:52 +0530 parvathi wrote: >>> The Programmable Real-Time Unit Industrial Communication Sub-system (PRU-ICSS) >>> is available on the TI SOCs in two flavors: Gigabit ICSS (ICSSG) and the older >>> Megabit ICSS (ICSSM). >> >> Every individual patch must build cleanly with W=1. >> Otherwise doing git bisections is a miserable experience. >> -- > > As we mentioned in cover letter we have dependency with SOC patch. > > "These patches have a dependency on an SOC patch, which we are including at the > end of this series for reference. The SOC patch has been submitted in a separate > thread [2] and we are awaiting for it to be merged." > > SOC patch need to be applied prior applying the "net" patches. We have changed the > order and appended the SOC patch at the end, because SOC changes need to go into > linux-next but not into net-next. > > We have make sure every individual patch has compiled successfully with W=1 if we > apply SOC patch prior to the "net" patches. > If there is any dependency in the series, the pre-requisite patch should come before the dependent patch. In this series, SoC Patch should have been the patch 1/10 and the warnings could have been avoided. > > Thanks and Regards, > Parvathi.
On 11:16-20250214, parvathi wrote: [...] > The patches presented in this series have gone through the patch verification > tools and no warnings or errors are reported. Sample test logs verifying the > functionality on Linux next kernel are available here: > > [Interface up Testing](https://gist.github.com/ParvathiPudi/f481837cc6994e400284cb4b58972804) > > [Ping Testing](https://gist.github.com/ParvathiPudi/a121aad402defcef389e93f303d79317) > > [Iperf Testing](https://gist.github.com/ParvathiPudi/581db46b0e9814ddb5903bdfee73fc6f) > I am looking at https://lore.kernel.org/all/20250214085315.1077108-11-parvathi@couthit.com/ and wondering if i can see the test log for am335x and am47xx to make sure that PRUs are functional on those two?
Hi, > On 18/02/25 3:36 pm, Parvathi Pudi wrote: >> >> Hi, >> >>> On Fri, 14 Feb 2025 11:16:52 +0530 parvathi wrote: >>>> The Programmable Real-Time Unit Industrial Communication Sub-system (PRU-ICSS) >>>> is available on the TI SOCs in two flavors: Gigabit ICSS (ICSSG) and the older >>>> Megabit ICSS (ICSSM). >>> >>> Every individual patch must build cleanly with W=1. >>> Otherwise doing git bisections is a miserable experience. >>> -- >> >> As we mentioned in cover letter we have dependency with SOC patch. >> >> "These patches have a dependency on an SOC patch, which we are including at the >> end of this series for reference. The SOC patch has been submitted in a separate >> thread [2] and we are awaiting for it to be merged." >> >> SOC patch need to be applied prior applying the "net" patches. We have changed >> the >> order and appended the SOC patch at the end, because SOC changes need to go into >> linux-next but not into net-next. >> >> We have make sure every individual patch has compiled successfully with W=1 if >> we >> apply SOC patch prior to the "net" patches. >> > > If there is any dependency in the series, the pre-requisite patch should > come before the dependent patch. In this series, SoC Patch should have > been the patch 1/10 and the warnings could have been avoided. > Sure, we will change the order and resubmit the patches in the next version. Thanks and Regards, Parvathi.
Hi, > On 11:16-20250214, parvathi wrote: > [...] >> The patches presented in this series have gone through the patch verification >> tools and no warnings or errors are reported. Sample test logs verifying the >> functionality on Linux next kernel are available here: >> >> [Interface up >> Testing](https://gist.github.com/ParvathiPudi/f481837cc6994e400284cb4b58972804) >> >> [Ping >> Testing](https://gist.github.com/ParvathiPudi/a121aad402defcef389e93f303d79317) >> >> [Iperf >> Testing](https://gist.github.com/ParvathiPudi/581db46b0e9814ddb5903bdfee73fc6f) >> > > > I am looking at > https://lore.kernel.org/all/20250214085315.1077108-11-parvathi@couthit.com/ > and wondering if i can see the test log for am335x and am47xx to make > sure that PRUs are functional on those two? > In this patch series we have added support for PRU-ICSS on the AM57x SOC. Hence the test log was only included for the AM57x SOC. We are working in parallel to add support for PRU-ICSS on the AM33x and AM43x SOC's as well. We will send it as a separate patch series at a later time. Thanks and Regards, Parvathi.
Hi, >> On 11:16-20250214, parvathi wrote: >> [...] >>> The patches presented in this series have gone through the patch verification >>> tools and no warnings or errors are reported. Sample test logs verifying the >>> functionality on Linux next kernel are available here: >>> >>> [Interface up >>> Testing](https://gist.github.com/ParvathiPudi/f481837cc6994e400284cb4b58972804) >>> >>> [Ping >>> Testing](https://gist.github.com/ParvathiPudi/a121aad402defcef389e93f303d79317) >>> >>> [Iperf >>> Testing](https://gist.github.com/ParvathiPudi/581db46b0e9814ddb5903bdfee73fc6f) >>> >> >> >> I am looking at >> https://lore.kernel.org/all/20250214085315.1077108-11-parvathi@couthit.com/ >> and wondering if i can see the test log for am335x and am47xx to make >> sure that PRUs are functional on those two? >> > > In this patch series we have added support for PRU-ICSS on the AM57x SOC. > Hence the test log was only included for the AM57x SOC. We are working in > parallel > to add support for PRU-ICSS on the AM33x and AM43x SOC's as well. We will send > it as > a separate patch series at a later time. > Further update: We have successfully cross compiled the kernel (linux-next) with this patch series for AM335x and AM437x SOC respectively. Kernel is booting well on both the SOCs and we have verified PRU functionality by loading simple example application (pru_addition.elf) on the PRU cores, by using "remoteproc" driver from mainline kernel. Below are the logs for the SOCs with boot log and running PRU with elf file specified above: AM335x test log: <https://gist.github.com/ParvathiPudi/87d7ddf949913b80f022ed99706337ac> AM437x test log: <https://gist.github.com/ParvathiPudi/b2d556829cb4a9e3b6b4c5656dbdd594> Thanks and Regards, Parvathi.
On 19:13-20250306, Parvathi Pudi wrote: > Hi, > > >> On 11:16-20250214, parvathi wrote: > >> [...] > >>> The patches presented in this series have gone through the patch verification > >>> tools and no warnings or errors are reported. Sample test logs verifying the > >>> functionality on Linux next kernel are available here: > >>> > >>> [Interface up > >>> Testing](https://gist.github.com/ParvathiPudi/f481837cc6994e400284cb4b58972804) > >>> > >>> [Ping > >>> Testing](https://gist.github.com/ParvathiPudi/a121aad402defcef389e93f303d79317) > >>> > >>> [Iperf > >>> Testing](https://gist.github.com/ParvathiPudi/581db46b0e9814ddb5903bdfee73fc6f) > >>> > >> > >> > >> I am looking at > >> https://lore.kernel.org/all/20250214085315.1077108-11-parvathi@couthit.com/ > >> and wondering if i can see the test log for am335x and am47xx to make > >> sure that PRUs are functional on those two? > >> > > > > In this patch series we have added support for PRU-ICSS on the AM57x SOC. > > Hence the test log was only included for the AM57x SOC. We are working in > > parallel > > to add support for PRU-ICSS on the AM33x and AM43x SOC's as well. We will send > > it as > > a separate patch series at a later time. > > > > Further update: > > We have successfully cross compiled the kernel (linux-next) with this patch series > for AM335x and AM437x SOC respectively. > > Kernel is booting well on both the SOCs and we have verified PRU functionality by > loading simple example application (pru_addition.elf) on the PRU cores, by using > "remoteproc" driver from mainline kernel. > > Below are the logs for the SOCs with boot log and running PRU with elf file specified > above: > > AM335x test log: <https://gist.github.com/ParvathiPudi/87d7ddf949913b80f022ed99706337ac> > AM437x test log: <https://gist.github.com/ParvathiPudi/b2d556829cb4a9e3b6b4c5656dbdd594> Thanks for testing this, I just got some time to dig further, I will respond on the standalone patch https://lore.kernel.org/all/20250108125937.10604-2-basharath@couthit.com/