netdev - Re: [PATCH net-next v5 09/14] net: ethernet: oa_tc6: implement transmit path to transfer tx ethernet frames

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <36ac502f-e24e-4aaf-a905-4036e8ea1ea3@lunn.ch>
Date: Sun, 11 Aug 2024 17:54:03 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Parthiban Veerasooran <Parthiban.Veerasooran@...rochip.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
	pabeni@...hat.com, horms@...nel.org, saeedm@...dia.com,
	anthony.l.nguyen@...el.com, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, corbet@....net,
	linux-doc@...r.kernel.org, robh+dt@...nel.org,
	krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
	devicetree@...r.kernel.org, horatiu.vultur@...rochip.com,
	ruanjinjie@...wei.com, steen.hegelund@...rochip.com,
	vladimir.oltean@....com, masahiroy@...nel.org,
	alexanderduyck@...com, krzk+dt@...nel.org, robh@...nel.org,
	rdunlap@...radead.org, hkallweit1@...il.com, linux@...linux.org.uk,
	UNGLinuxDriver@...rochip.com, Thorsten.Kummermehr@...rochip.com,
	Pier.Beruto@...emi.com, Selvamani.Rajagopal@...emi.com,
	Nicolas.Ferre@...rochip.com, benjamin.bigler@...nformulastudent.ch,
	linux@...ler.io
Subject: Re: [PATCH net-next v5 09/14] net: ethernet: oa_tc6: implement
 transmit path to transfer tx ethernet frames

On Tue, Jul 30, 2024 at 09:39:01AM +0530, Parthiban Veerasooran wrote:
> The transmit ethernet frame will be converted into multiple transmit data
> chunks. Each transmit data chunk consists of a 4 bytes header followed by
> a 64 bytes transmit data chunk payload. The 4 bytes data header occurs at
> the beginning of each transmit data chunk on MOSI. The data header
> contains the information needed to determine the validity and location of
> the transmit frame data within the data chunk payload. The number of
> transmit data chunks transmitted to mac-phy is limited to the number
> transmit credits available in the mac-phy. Initially the transmit credits
> will be updated from the buffer status register and then it will be
> updated from the footer received on each spi data transfer. The received
> footer will be examined for the transmit errors if any.
> 
> Signed-off-by: Parthiban Veerasooran <Parthiban.Veerasooran@...rochip.com>
Reviewed-by: Andrew Lunn <andrew@...n.ch>

    Andrew