From: Minwoo Im <minwoo.im@samsung.com>
To: Jeuk Kim <jeuk20.kim@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
gost.dev@samsung.com, Jeuk Kim <jeuk20.kim@samsung.com>,
Hanna Reitz <hreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Minwoo Im <minwoo.im@samsung.com>
Subject: Re: [PATCH 2/2] hw/ufs: Add support MCQ of UFSHCI 4.0
Date: Tue, 28 May 2024 10:54:13 +0900 [thread overview]
Message-ID: <ZlU5RbH9aV8fji8q@localhost> (raw)
In-Reply-To: <dd406b1d-94d2-4b4e-8053-07d8237994df@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
On 24-05-28 10:00:35, Jeuk Kim wrote:
> Thanks for your contribution!
>
> There are only two minor comments.
Thanks for your review.
>
> Please check it and send patch v2.
>
>
> Thank you!
>
> On 5/21/2024 8:05 PM, Minwoo Im wrote:
> > @@ -1288,12 +1717,21 @@ static void ufs_exit(PCIDevice *pci_dev)
> > ufs_clear_req(&u->req_list[i]);
> > }
> > g_free(u->req_list);
> > +
> > + for (int i = 0; i < ARRAY_SIZE(u->sq); i++) {
> > + ufs_mcq_delete_sq(u, i);
>
> Isn't it possible that trace_ufs_err_mcq_delete_cq_not_exists is printed
> even in a normal shutdown situation?
>
> If true, please fix it so that the ufs_err log is not printed in normal
> situation.
I will make sure that the normal shut-down case will not print out the error
event trace.
>
> > + }
> > + for (int i = 0; i < ARRAY_SIZE(u->cq); i++) {
> > + ufs_mcq_delete_cq(u, i);
> > + }
> > }
> > static Property ufs_props[] = {
> > DEFINE_PROP_STRING("serial", UfsHc, params.serial),
> > DEFINE_PROP_UINT8("nutrs", UfsHc, params.nutrs, 32),
> > DEFINE_PROP_UINT8("nutmrs", UfsHc, params.nutmrs, 8),
> > + DEFINE_PROP_BOOL("mcq", UfsHc, params.mcq, false),
> > + DEFINE_PROP_UINT8("mcq-maxq", UfsHc, params.mcq_maxq, 1),
> Please change this value to a value greater than or equal to 2.
Oh yeah, it should be to support device command handling in MCQ mode. I will
update it in v2.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2024-05-28 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240521111643epcas2p119387edb838377d98d269e62d994cc3a@epcas2p1.samsung.com>
2024-05-21 11:05 ` [PATCH 0/2] hw/ufs: Add support MCQ Minwoo Im
[not found] ` <CGME20240521111643epcas2p3c86343fde1fdd6dbd868d09188084ae0@epcas2p3.samsung.com>
2024-05-21 11:05 ` [PATCH 1/2] hw/ufs: Update MCQ-related fields to block/ufs.h Minwoo Im
[not found] ` <CGME20240521111643epcas2p4ab1c2610d26878c405288e9006bc4f92@epcas2p4.samsung.com>
2024-05-21 11:05 ` [PATCH 2/2] hw/ufs: Add support MCQ of UFSHCI 4.0 Minwoo Im
2024-05-28 1:00 ` Jeuk Kim
2024-05-28 1:54 ` Minwoo Im [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=ZlU5RbH9aV8fji8q@localhost \
--to=minwoo.im@samsung.com \
--cc=gost.dev@samsung.com \
--cc=hreitz@redhat.com \
--cc=jeuk20.kim@gmail.com \
--cc=jeuk20.kim@samsung.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).