Hi Stephen, Please ignore this. This is valid wrt to DPAA.
Thanks! > -----Original Message----- > From: Stephen Hemminger <step...@networkplumber.org> > Sent: 11 June 2025 22:21 > To: Vanshika Shukla <vanshika.shu...@nxp.com> > Cc: dev@dpdk.org; Hemant Agrawal <hemant.agra...@nxp.com>; Sachin > Saxena <sachin.sax...@nxp.com>; Jun Yang <jun.y...@nxp.com> > Subject: [EXT] Re: [v4 02/10] bus/dpaa: add FMan node > > Caution: This is an external email. Please take care when clicking links or > opening attachments. When in doubt, report the message using the 'Report > this email' button > > > On Wed, 11 Jun 2025 12:40:31 +0530 > vanshika.shu...@nxp.com wrote: > > > From: Jun Yang <jun.y...@nxp.com> > > > > Add FMan node(s) and associate FMan to it's interface(port). > > This method describes FMan attributes and avoid accessing FMan from > > port directly. > > Logically, something like IEEE 1588 is FMan global resource, which is > > in range of 0xF_E000–0xF_EFFF. > > Port specific resource is in range of 0x8_0000–0xB_FFFF. > > > > Signed-off-by: Jun Yang <jun.y...@nxp.com> > > This looks like a typo > > ### [PATCH] bus/dpaa: add FMan node > > WARNING:TYPO_SPELLING: 'contextA' may be misspelled - perhaps 'context'? > #147: FILE: drivers/bus/dpaa/base/fman/fman.c:125: > + * Set A2V, OVOM, EBD bits in contextA to allow external > ^^^^^^^^
