From: Thomas Monjalon <thomas@monjalon.net>
To: 'Stephen Hemminger' <stephen@networkplumber.org>,
Jiawen Wu <jiawenwu@trustnetic.com>
Cc: dev@dpdk.org, zaiyuwang@trustnetic.com
Subject: Re: [PATCH] net/txgbe: fix the missing old mailbox interface calls
Date: Wed, 26 Nov 2025 09:29:56 +0100 [thread overview]
Message-ID: <8941560.lvqk35OSZv@thomas> (raw)
In-Reply-To: <011a01dc5e9d$cf400cf0$6dc026d0$@trustnetic.com>
26/11/2025 07:27, Jiawen Wu:
> Hi, this fix patch is crucial for the new merged feature in this release.
>
> > -----Original Message-----
> > From: Jiawen Wu <jiawenwu@trustnetic.com>
> > Sent: Monday, November 24, 2025 10:03 AM
> > To: 'Stephen Hemminger' <stephen@networkplumber.org>
> > Cc: dev@dpdk.org; zaiyuwang@trustnetic.com
> > Subject: RE: [PATCH] net/txgbe: fix the missing old mailbox interface calls
> >
> > On Thu, Nov 20, 2025 2:25 PM, Jiawen Wu wrote:
> > > On Thu, Nov 20, 2025 1:48 PM, Stephen Hemminger wrote:
> > > > On Wed, 19 Nov 2025 16:56:24 +0800
> > > > Jiawen Wu <jiawenwu@trustnetic.com> wrote:
> > > >
> > > > > @@ -28,6 +29,9 @@ void txgbe_init_ops_aml40(struct txgbe_hw *hw)
> > > > > mac->init_mac_link_ops = txgbe_init_mac_link_ops_aml40;
> > > > > mac->get_link_capabilities = txgbe_get_link_capabilities_aml40;
> > > > > mac->check_link = txgbe_check_mac_link_aml40;
> > > > > +
> > > > > + /* MAILBOX */
> > > > > + mbx->host_interface_command = txgbe_host_interface_command_aml;
> > > > > }
> > > >
> > > > Maybe that comment means something to you, but it seems like something
> > > > the next maintainer would not know what it means. Could you explain it more?
> > >
> > > For different devices, the mailbox flow between software and firmware is
> > > different. There are several mailbox command in the txgbe driver, but only
> > > txgbe_hic_sr_read() was changed to use the new flow in commit
> > > 6a139ade82e7 ("net/txgbe: add new SW-FW mailbox interface"). Because
> > > this function invoke the txgbe_hic_unlocked() directly without SW-FW
> > > semaphore, I guess.
> > >
> > > It lead to other mailbox commands timeout for Amber-Lite devices, which
> > > is required to use the new flow. So this patch fills in the missing part.
> > >
> > > For the sake of code tidy, txgbe_hic_sr_read() should change to use the
> > > locked function txgbe_host_interface_command(), and this function could
> > > be change to pointer in struct txgbe_mbx_info for different devices.
> >
> > Hi Stephen Hemminger,
> >
> > Does this explanation is sufficient? Should I send v2 patch with these logs?
Yes you should send a v2 with a better comment in the code,
and maybe a longer explanation in the commit log.
next prev parent reply other threads:[~2025-11-26 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 8:56 Jiawen Wu
2025-11-20 5:47 ` Stephen Hemminger
2025-11-20 6:24 ` Jiawen Wu
2025-11-24 2:03 ` Jiawen Wu
2025-11-26 6:27 ` Jiawen Wu
2025-11-26 8:29 ` Thomas Monjalon [this message]
2025-11-26 8:56 ` [PATCH v2] " Jiawen Wu
2025-11-26 21:43 ` Stephen Hemminger
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=8941560.lvqk35OSZv@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jiawenwu@trustnetic.com \
--cc=stephen@networkplumber.org \
--cc=zaiyuwang@trustnetic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).