From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: fan <nifan.cxl@gmail.com>, <vishal.l.verma@intel.com>,
<fan.ni@samsung.com>, <a.manzanares@samsung.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v2 -qemu] hw/cxl: Support firmware updates
Date: Fri, 21 Jun 2024 17:58:18 +0100 [thread overview]
Message-ID: <20240621175818.00007705@huawei.com> (raw)
In-Reply-To: <20240319204818.p6qbkyktgsadmkhi@offworld>
On Tue, 19 Mar 2024 13:48:18 -0700
Davidlohr Bueso <dave@stgolabs.net> wrote:
> On Tue, 19 Mar 2024, fan wrote:
>
> >> +/* CXL r3.1 section 8.2.9.3.2: Transfer FW (Opcode 0201h) */
> >> +#define CXL_FW_XFER_ALIGNMENT 128
> >> +
> >> +#define CXL_FW_XFER_ACTION_FULL 0x0
> >> +#define CXL_FW_XFER_ACTION_INIT 0x1
> >> +#define CXL_FW_XFER_ACTION_CONTINUE 0x2
> >> +#define CXL_FW_XFER_ACTION_END 0x3
> >> +#define CXL_FW_XFER_ACTION_ABORT 0x4
> >
> >The above definitions have "tab" used, cannot pass checkpatch check.
>
> I was not aware of a checkpatch for qemu, will clean up.
>
> >> +
> >> +static CXLRetCode cmd_firmware_update_transfer(const struct cxl_cmd *cmd,
> >> + uint8_t *payload_in,
> >> + size_t len,
> >> + uint8_t *payload_out,
> >> + size_t *len_out,
> >> + CXLCCI *cci)
> >> +{
> >> + struct {
> >> + uint8_t action;
> >> + uint8_t slot;
> >> + uint8_t caps;
> >
> >Based on table 8-66, I cannot find the field "caps" and it is unused.
>
> Hmm yep don't know how that snuck in, will get rid of it.
>
> Thanks,
> Davidlohr
I fixed both on my tree.
next prev parent reply other threads:[~2024-06-21 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 17:29 [PATCH v2 -qemu] hw/cxl: Support firmware updates Davidlohr Bueso
2024-03-19 16:28 ` Davidlohr Bueso
2024-03-19 17:56 ` fan
2024-03-19 20:48 ` Davidlohr Bueso
2024-06-21 16:58 ` Jonathan Cameron [this message]
2024-06-21 17:08 ` Jonathan Cameron
2024-04-22 15:51 ` Jonathan Cameron
2024-06-17 19:37 ` Davidlohr Bueso
2024-06-21 17:07 ` Jonathan Cameron
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=20240621175818.00007705@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nifan.cxl@gmail.com \
--cc=vishal.l.verma@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 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.