All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parvathi Pudi <parvathi@couthit.com>
To: ALOK TIWARI <alok.a.tiwari@oracle.com>
Cc: pratheesh <pratheesh@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>, praneeth <praneeth@ti.com>,
	edumazet <edumazet@google.com>, glaroque <glaroque@baylibre.com>,
	pmohan <pmohan@couthit.com>, diogo ivo <diogo.ivo@siemens.com>,
	robh <robh@kernel.org>,
	javier carrasco cruz <javier.carrasco.cruz@gmail.com>,
	saikrishnag <saikrishnag@marvell.com>,
	m-karicheri2 <m-karicheri2@ti.com>,
	jacob e keller <jacob.e.keller@intel.com>, kuba <kuba@kernel.org>,
	pabeni <pabeni@redhat.com>,
	richardcochran <richardcochran@gmail.com>,
	devicetree <devicetree@vger.kernel.org>,
	conor+dt <conor+dt@kernel.org>, mohan <mohan@couthit.com>,
	s hauer <s.hauer@pengutronix.de>,
	Prajith Jayarajan <prajith@ti.com>, rogerq <rogerq@kernel.org>,
	basharath <basharath@couthit.com>, ssantosh <ssantosh@kernel.org>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	rogerq <rogerq@ti.com>, srk <srk@ti.com>,
	kory maincent <kory.maincent@bootlin.com>,
	m-malladi <m-malladi@ti.com>, netdev <netdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	danishanwar <danishanwar@ti.com>, afd <afd@ti.com>,
	andrew+netdev <andrew+netdev@lunn.ch>,
	parvathi <parvathi@couthit.com>, horms <horms@kernel.org>,
	krishna <krishna@couthit.com>, krzk+dt <krzk+dt@kernel.org>,
	davem <davem@davemloft.net>
Subject: Re: [PATCH net-next v12 3/5] net: ti: prueth: Adds PRUETH HW and SW configuration
Date: Thu, 31 Jul 2025 19:41:09 +0530 (IST)	[thread overview]
Message-ID: <1942226614.78018.1753971069296.JavaMail.zimbra@couthit.local> (raw)
In-Reply-To: <743eddd9-1f63-4c6c-8ba3-5007bd897ae1@oracle.com>

Hi,

>> +/* NRT Buffer descriptor definition
>> + * Each buffer descriptor points to a max 32 byte block and has 32 bit in size
>> + * to have atomic operation.
>> + * PRU can address bytewise into memory.
>> + * Definition of 32 bit descriptor is as follows
>> + *
>> + * Bits		Name			Meaning
>> + *
>> =============================================================================
>> + * 0..7		Index		points to index in buffer queue, max 256 x 32
>> + *				byte blocks can be addressed
>> + * 6		LookupSuccess	For switch, FDB lookup was successful (source
>> + *				MAC address found in FDB).
>> + *				For RED, NodeTable lookup was successful.
>> + * 7		Flood		Packet should be flooded (destination MAC
>> + *				address found in FDB). For switch only.
>> + * 8..12	Block_length	number of valid bytes in this specific block.
>> + *				Will be <=32 bytes on last block of packet
>> + * 13		More		"More" bit indicating that there are more blocks
>> + * 14		Shadow		indicates that "index" is pointing into shadow
>> + *				buffer
>> + * 15		TimeStamp	indicates that this packet has time stamp in
>> + *				separate buffer - only needed of PTCP runs on
> 
> only needed if PTCP runs on host
> 

Sure, We will address this.

>> + *				host
>> + * 16..17	Port		different meaning for ingress and egress,
>> + *				Ingress: Port = 0 indicates phy port 1 and
>> + *				Port = 1 indicates phy port 2.
>> + *				Egress: 0 sends on phy port 1 and 1 sends on
>> + *				phy port 2. Port = 2 goes over MAC table
>> + *				look-up
>> + * 18..28	Length		11 bit of total packet length which is put into
>> + *				first BD only so that host access only one BD
>> + * 29		VlanTag		indicates that packet has Length/Type field of
>> + *				0x08100 with VLAN tag in following byte
>> + * 30		Broadcast	indicates that packet goes out on both physical
>> + *				ports,	there will be two bd but only one buffer
>> + * 31		Error		indicates there was an error in the packet
>> + */
>> +#define PRUETH_BD_START_FLAG_MASK	BIT(0)
>> +#define PRUETH_BD_START_FLAG_SHIFT	0
>> +
>> +#define PRUETH_BD_HSR_FRAME_MASK	BIT(4)
>> +#define PRUETH_BD_HSR_FRAME_SHIFT	4
>> +
>> +#define PRUETH_BD_SUP_HSR_FRAME_MASK	BIT(5)
>> +#define PRUETH_BD_SUP_HSR_FRAME_SHIFT	5
>> +
>> +#define PRUETH_BD_LOOKUP_SUCCESS_MASK	BIT(6)
>> +#define PRUETH_BD_LOOKUP_SUCCESS_SHIFT	6
>> +
>> +#define PRUETH_BD_SW_FLOOD_MASK		BIT(7)
>> +#define PRUETH_BD_SW_FLOOD_SHIFT	7
>> +
>> +#define	PRUETH_BD_SHADOW_MASK		BIT(14)
>> +#define	PRUETH_BD_SHADOW_SHIFT		14
>> +
>> +#define PRUETH_BD_TIMESTAMP_MASK	BIT(15)
>> +#define PRUETH_BD_TIMESTAMP_SHIT	15
> 
> typo PRUETH_BD_TIMESTAMP_SHIT -> PRUETH_BD_TIMESTAMP_SHIFT
> 

Sure, We will address this.


Thanks and Regards,
Parvathi.


WARNING: multiple messages have this Message-ID (diff)
From: Parvathi Pudi <parvathi@couthit.com>
To: ALOK TIWARI <alok.a.tiwari@oracle.com>
Cc: parvathi <parvathi@couthit.com>, danishanwar <danishanwar@ti.com>,
	 rogerq <rogerq@kernel.org>,
	andrew+netdev <andrew+netdev@lunn.ch>,
	 davem <davem@davemloft.net>, edumazet <edumazet@google.com>,
	 kuba <kuba@kernel.org>, pabeni <pabeni@redhat.com>,
	 robh <robh@kernel.org>, krzk+dt <krzk+dt@kernel.org>,
	 conor+dt <conor+dt@kernel.org>, ssantosh <ssantosh@kernel.org>,
	 richardcochran <richardcochran@gmail.com>,
	 s hauer <s.hauer@pengutronix.de>,
	m-karicheri2 <m-karicheri2@ti.com>,
	 glaroque <glaroque@baylibre.com>, afd <afd@ti.com>,
	 saikrishnag <saikrishnag@marvell.com>,
	m-malladi <m-malladi@ti.com>,
	 jacob e keller <jacob.e.keller@intel.com>,
	 kory maincent <kory.maincent@bootlin.com>,
	 diogo ivo <diogo.ivo@siemens.com>,
	 javier carrasco cruz <javier.carrasco.cruz@gmail.com>,
	 horms <horms@kernel.org>, s-anna <s-anna@ti.com>,
	 basharath <basharath@couthit.com>,
	 linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	 netdev <netdev@vger.kernel.org>,
	 devicetree <devicetree@vger.kernel.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	 Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	 pratheesh <pratheesh@ti.com>, Prajith Jayarajan <prajith@ti.com>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	praneeth <praneeth@ti.com>,  srk <srk@ti.com>,
	rogerq <rogerq@ti.com>,  krishna <krishna@couthit.com>,
	pmohan <pmohan@couthit.com>,  mohan <mohan@couthit.com>
Subject: Re: [PATCH net-next v12 3/5] net: ti: prueth: Adds PRUETH HW and SW configuration
Date: Thu, 31 Jul 2025 19:41:09 +0530 (IST)	[thread overview]
Message-ID: <1942226614.78018.1753971069296.JavaMail.zimbra@couthit.local> (raw)
In-Reply-To: <743eddd9-1f63-4c6c-8ba3-5007bd897ae1@oracle.com>

Hi,

>> +/* NRT Buffer descriptor definition
>> + * Each buffer descriptor points to a max 32 byte block and has 32 bit in size
>> + * to have atomic operation.
>> + * PRU can address bytewise into memory.
>> + * Definition of 32 bit descriptor is as follows
>> + *
>> + * Bits		Name			Meaning
>> + *
>> =============================================================================
>> + * 0..7		Index		points to index in buffer queue, max 256 x 32
>> + *				byte blocks can be addressed
>> + * 6		LookupSuccess	For switch, FDB lookup was successful (source
>> + *				MAC address found in FDB).
>> + *				For RED, NodeTable lookup was successful.
>> + * 7		Flood		Packet should be flooded (destination MAC
>> + *				address found in FDB). For switch only.
>> + * 8..12	Block_length	number of valid bytes in this specific block.
>> + *				Will be <=32 bytes on last block of packet
>> + * 13		More		"More" bit indicating that there are more blocks
>> + * 14		Shadow		indicates that "index" is pointing into shadow
>> + *				buffer
>> + * 15		TimeStamp	indicates that this packet has time stamp in
>> + *				separate buffer - only needed of PTCP runs on
> 
> only needed if PTCP runs on host
> 

Sure, We will address this.

>> + *				host
>> + * 16..17	Port		different meaning for ingress and egress,
>> + *				Ingress: Port = 0 indicates phy port 1 and
>> + *				Port = 1 indicates phy port 2.
>> + *				Egress: 0 sends on phy port 1 and 1 sends on
>> + *				phy port 2. Port = 2 goes over MAC table
>> + *				look-up
>> + * 18..28	Length		11 bit of total packet length which is put into
>> + *				first BD only so that host access only one BD
>> + * 29		VlanTag		indicates that packet has Length/Type field of
>> + *				0x08100 with VLAN tag in following byte
>> + * 30		Broadcast	indicates that packet goes out on both physical
>> + *				ports,	there will be two bd but only one buffer
>> + * 31		Error		indicates there was an error in the packet
>> + */
>> +#define PRUETH_BD_START_FLAG_MASK	BIT(0)
>> +#define PRUETH_BD_START_FLAG_SHIFT	0
>> +
>> +#define PRUETH_BD_HSR_FRAME_MASK	BIT(4)
>> +#define PRUETH_BD_HSR_FRAME_SHIFT	4
>> +
>> +#define PRUETH_BD_SUP_HSR_FRAME_MASK	BIT(5)
>> +#define PRUETH_BD_SUP_HSR_FRAME_SHIFT	5
>> +
>> +#define PRUETH_BD_LOOKUP_SUCCESS_MASK	BIT(6)
>> +#define PRUETH_BD_LOOKUP_SUCCESS_SHIFT	6
>> +
>> +#define PRUETH_BD_SW_FLOOD_MASK		BIT(7)
>> +#define PRUETH_BD_SW_FLOOD_SHIFT	7
>> +
>> +#define	PRUETH_BD_SHADOW_MASK		BIT(14)
>> +#define	PRUETH_BD_SHADOW_SHIFT		14
>> +
>> +#define PRUETH_BD_TIMESTAMP_MASK	BIT(15)
>> +#define PRUETH_BD_TIMESTAMP_SHIT	15
> 
> typo PRUETH_BD_TIMESTAMP_SHIT -> PRUETH_BD_TIMESTAMP_SHIFT
> 

Sure, We will address this.


Thanks and Regards,
Parvathi.

  reply	other threads:[~2025-07-31 14:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24  7:23 [PATCH net-next v12 0/5] PRU-ICSSM Ethernet Driver Parvathi Pudi
2025-07-24  7:23 ` [PATCH net-next v12 1/5] dt-bindings: net: ti: Adds DUAL-EMAC mode support on PRU-ICSS2 for AM57xx, AM43xx and AM33xx SOCs Parvathi Pudi
2025-07-24  7:23 ` [PATCH net-next v12 2/5] net: ti: prueth: Adds ICSSM Ethernet driver Parvathi Pudi
2025-07-25 17:55   ` ALOK TIWARI
2025-07-31 14:15     ` Parvathi Pudi
2025-07-31 14:15       ` Parvathi Pudi
2025-08-06 13:40   ` Bastien Curutchet
2025-08-11 10:14     ` Parvathi Pudi
2025-08-11 10:14       ` Parvathi Pudi
2025-07-24  7:23 ` [PATCH net-next v12 3/5] net: ti: prueth: Adds PRUETH HW and SW configuration Parvathi Pudi
2025-07-25 17:43   ` ALOK TIWARI
2025-07-31 14:11     ` Parvathi Pudi [this message]
2025-07-31 14:11       ` Parvathi Pudi
2025-07-24  9:10 ` [PATCH net-next v12 4/5] net: ti: prueth: Adds link detection, RX and TX support Parvathi Pudi
2025-07-24  9:10 ` [PATCH net-next v12 5/5] net: ti: prueth: Adds IEP support for PRUETH on AM33x, AM43x and AM57x SOCs Parvathi Pudi
2025-07-25 14:04   ` ALOK TIWARI
2025-07-31 14:08     ` Parvathi Pudi
2025-07-31 14:08       ` Parvathi Pudi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1942226614.78018.1753971069296.JavaMail.zimbra@couthit.local \
    --to=parvathi@couthit.com \
    --cc=afd@ti.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=basharath@couthit.com \
    --cc=conor+dt@kernel.org \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=diogo.ivo@siemens.com \
    --cc=edumazet@google.com \
    --cc=glaroque@baylibre.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=kory.maincent@bootlin.com \
    --cc=krishna@couthit.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=m-malladi@ti.com \
    --cc=mohan@couthit.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pmohan@couthit.com \
    --cc=prajith@ti.com \
    --cc=praneeth@ti.com \
    --cc=pratheesh@ti.com \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=rogerq@ti.com \
    --cc=s.hauer@pengutronix.de \
    --cc=saikrishnag@marvell.com \
    --cc=srk@ti.com \
    --cc=ssantosh@kernel.org \
    --cc=vadim.fedorenko@linux.dev \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.