From: Jeuk Kim <jeuk20.kim@gmail.com>
To: yc01.jeong@samsung.com, Jeuk Kim <jeuk20.kim@samsung.com>
Cc: "thuth@redhat.com" <thuth@redhat.com>,
"lvivier@redhat.com" <lvivier@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"jeongyuchan0629@gmail.com" <jeongyuchan0629@gmail.com>
Subject: Re: [PATCH 1/4] hw/ufs: minor bug fixes related to ufs-test
Date: Thu, 22 Aug 2024 15:08:48 +0900 [thread overview]
Message-ID: <b4dc0999-3826-4b3c-8864-4904dafff2ec@gmail.com> (raw)
In-Reply-To: <20240822060010epcms1p6b10addc94bc16411c3a32d1f404c5978@epcms1p6>
On 8/22/2024 3:00 PM, Yoochan Jeong wrote:
> On 8/22/2024, Jeuk Kim wrote:
>> On 8/21/2024 11:32 AM, 정유찬 wrote:
>>> static void ufs_send_query(QUfs *ufs, uint8_t slot, uint8_t query_function,
>>> uint8_t query_opcode, uint8_t idn, uint8_t index,
>>> + uint8_t selector, uint32_t attr_value,
>> We use ufs_send_query() not only for attributes, but also descriptors
>> and flags.
>>
>> Please rename `attr_value` to `value`.
>>
>>
>
> I think this parameter name is okay, because this "value" in UPIU is
> only used when writing attributes. Writing flags do not require an
> actual value, and descriptor data will be stored in data segmentation
> area.
Okay. That's reasonable.
>
>>>
>> We might need to check condition here that `query_opcode !=
>> UFS_UPIU_QUERY_OPCODE_WRITE_DESC`, since
>>
>> it is not implemented yet.
>>
> in ufs_exec_query_write function in ufs.c, it already checks
> if it is trying to write a descriptor. Is there any particular
> reason that we should check it here in advance?
You're right. We don't need to check it here.
next prev parent reply other threads:[~2024-08-22 6:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240821022726epcms1p127d8cd71ca3e1354592de8a4a5c97a10@epcms1p4>
2024-08-21 2:30 ` [PATCH 0/4] hw/ufs: ufs device testing function added and modified 정유찬
[not found] ` <CGME20240821022726epcms1p127d8cd71ca3e1354592de8a4a5c97a10@epcms1p3>
2024-08-21 2:32 ` [PATCH 1/4] hw/ufs: minor bug fixes related to ufs-test 정유찬
2024-08-22 4:50 ` Jeuk Kim
[not found] ` <CGME20240821022726epcms1p127d8cd71ca3e1354592de8a4a5c97a10@epcms1p6>
2024-08-22 6:00 ` Yoochan Jeong
2024-08-22 6:08 ` Jeuk Kim [this message]
[not found] ` <CGME20240821022726epcms1p127d8cd71ca3e1354592de8a4a5c97a10@epcms1p5>
2024-08-21 2:34 ` [PATCH 2/4] hw/ufs: ufs flag read/write test implemented 정유찬
[not found] ` <CGME20240821022726epcms1p127d8cd71ca3e1354592de8a4a5c97a10@epcms1p1>
2024-08-21 2:27 ` [PATCH 0/4] hw/ufs: ufs device testing function added and modified 정유찬
2024-08-21 2:35 ` [PATCH 3/4] hw/ufs: ufs attribute read/write test implemented 정유찬
2024-08-22 1:39 ` [PATCH 4/4] hw/ufs: ufs descriptor read " Yoochan Jeong
2024-08-22 5:40 ` Jeuk Kim
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=b4dc0999-3826-4b3c-8864-4904dafff2ec@gmail.com \
--to=jeuk20.kim@gmail.com \
--cc=jeongyuchan0629@gmail.com \
--cc=jeuk20.kim@samsung.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=yc01.jeong@samsung.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).