[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <896abe03-4fcd-003f-1273-209daafc5635@acm.org>
Date: Wed, 28 Jun 2023 15:50:44 -0700
From: Bart Van Assche <bvanassche@....org>
To: Arthur Simchaev <arthur.simchaev@....com>,
martin.petersen@...cle.com
Cc: avri.altman@....com, Avi.Shchislowski@....com, beanhuo@...ron.com,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RESEND v2] ufs: core: Add support for qTimestamp attribute
On 6/26/23 03:33, Arthur Simchaev wrote:
> +/**
> + * struct utp_upiu_query_v4_0 - upiu request buffer structure for
> + * query request >= UFS 4.0 spec.
> + * @opcode: command to perform B-0
> + * @idn: a value that indicates the particular type of data B-1
> + * @index: Index to further identify data B-2
> + * @selector: Index to further identify data B-3
> + * @osf4: spec field B-5
> + * @osf5: spec field B 6,7
> + * @osf6: spec field DW 8,9
> + * @osf7: spec field DW 10,11
> + */
> +struct utp_upiu_query_v4_0 {
> + __u8 opcode;
> + __u8 idn;
> + __u8 index;
> + __u8 selector;
> + __u8 osf3;
> + __u8 osf4;
> + __be16 osf5;
> + __be32 osf6;
> + __be32 osf7;
> + __be32 reserved;
> +};
Is this structure useful for user space software? If not, please move it
into another header file.
Thanks,
Bart.
Powered by blists - more mailing lists