From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Przemek Kitszel'" <przemyslaw.kitszel@intel.com>
Cc: <mengyuanlou@net-swift.com>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <linux@armlinux.org.uk>, <horms@kernel.org>,
<netdev@vger.kernel.org>
Subject: RE: [PATCH net-next v2 1/2] net: txgbe: Add basic support for new AML devices
Date: Tue, 14 Jan 2025 15:29:21 +0800 [thread overview]
Message-ID: <059d01db6656$07f4dcb0$17de9610$@trustnetic.com> (raw)
In-Reply-To: <0be63e70-74bb-465a-a933-0258a45033a8@intel.com>
> > + /* index to unique seq id for each mbox message */
> > + send_hdr->index = wx->swfw_index;
> > + send_cmd = send_hdr->cmd;
> > +
> > + dword_len = length >> 2;
> > + /* write data to SW-FW mbox array */
> > + for (i = 0; i < dword_len; i++) {
> > + wr32a(wx, WX_SW2FW_MBOX, i, (__force u32)cpu_to_le32(buffer[i]));
> > + /* write flush */
> > + rd32a(wx, WX_SW2FW_MBOX, i);
>
> do you really need to flush all registers?
Yes, hardware requires this.
>
> > + }
> > +
> > + /* generate interrupt to notify FW */
> > + wr32m(wx, WX_SW2FW_MBOX_CMD, WX_SW2FW_MBOX_CMD_VLD, 0);
> > + wr32m(wx, WX_SW2FW_MBOX_CMD, WX_SW2FW_MBOX_CMD_VLD, WX_SW2FW_MBOX_CMD_VLD);
> > +
> > + dword_len = hdr_size >> 2;
> > +
> > + /* polling reply from FW */
> > + timeout = 50;
> > + do {
> > + timeout--;
> > + usleep_range(1000, 2000);
> > +
> > + /* read hdr */
> > + for (bi = 0; bi < dword_len; bi++)
> > + buffer[bi] = rd32a(wx, WX_FW2SW_MBOX, bi);
>
> no need for le32_to_cpu()?
> (if so, reexamine whole patch)
Indeed need.
> > +/**
> > + * wx_host_interface_command - Issue command to manageability block
> > + * @wx: pointer to the HW structure
> > + * @buffer: contains the command to write and where the return status will
> > + * be placed
> > + * @length: length of buffer, must be multiple of 4 bytes
> > + * @timeout: time in ms to wait for command completion
> > + * @return_data: read and return data from the buffer (true) or not (false)
> > + * Needed because FW structures are big endian and decoding of
>
> In other places you were using cpu_to_le32(), this comment seems to
> contradict that
FW structures are big endian, and we agreed to transfer in the mailbox registers
according to 32-bit little endian. However, buffers contain 8 bits or 16 bits field
which is composed using CPU byte order. So we use cpu_to_le32() and le32_to_cpu()
in this driver.
prev parent reply other threads:[~2025-01-14 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 10:31 [PATCH net-next v2 1/2] net: txgbe: Add basic support for new AML devices Jiawen Wu
2025-01-13 10:31 ` [PATCH net-next v2 2/2] net: wangxun: Replace the judgement of MAC type with flags Jiawen Wu
2025-01-13 15:13 ` [PATCH net-next v2 1/2] net: txgbe: Add basic support for new AML devices Przemek Kitszel
2025-01-13 17:13 ` Andrew Lunn
2025-01-14 7:29 ` Jiawen Wu [this message]
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='059d01db6656$07f4dcb0$17de9610$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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).