From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Bean Huo'" <huobean@gmail.com>, <avri.altman@wdc.com>,
<asutoshd@codeaurora.org>, <jejb@linux.ibm.com>,
<martin.petersen@oracle.com>, <stanley.chu@mediatek.com>,
<beanhuo@micron.com>, <bvanassche@acm.org>,
<tomas.winkler@intel.com>, <cang@codeaurora.org>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scsi: ufs: change upiu_flags to be u8
Date: Mon, 6 Jul 2020 21:03:09 +0530 [thread overview]
Message-ID: <02e501d653aa$c38c35e0$4aa4a1a0$@samsung.com> (raw)
In-Reply-To: <20200706123936.24799-1-huobean@gmail.com>
Hi Bean
> -----Original Message-----
> From: Bean Huo <huobean@gmail.com>
> Sent: 06 July 2020 18:10
> To: alim.akhtar@samsung.com; avri.altman@wdc.com;
> asutoshd@codeaurora.org; jejb@linux.ibm.com; martin.petersen@oracle.com;
> stanley.chu@mediatek.com; beanhuo@micron.com; bvanassche@acm.org;
> tomas.winkler@intel.com; cang@codeaurora.org
> Cc: linux-scsi@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [PATCH] scsi: ufs: change upiu_flags to be u8
>
> From: Bean Huo <beanhuo@micron.com>
>
> According to the UFS Spec, the Flags in the UPIU is one-byte length, not
> 4 bytes. change it to be u8.
>
> Signed-off-by: Bean Huo <beanhuo@micron.com>
> ---
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Booted and tested on exynos7 board, tested basic read/write, so
Tested-by: Alim Akhtar <alim.akhtar@samsung.com>
Thanks,
> drivers/scsi/ufs/ufshcd.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c index
> 96d830bb900f..d7fd5891e81f 100644
> --- a/drivers/scsi/ufs/ufshcd.c
> +++ b/drivers/scsi/ufs/ufshcd.c
> @@ -2240,7 +2240,7 @@ static void ufshcd_disable_intr(struct ufs_hba *hba,
> u32 intrs)
> * @cmd_dir: requests data direction
> */
> static void ufshcd_prepare_req_desc_hdr(struct ufshcd_lrb *lrbp,
> - u32 *upiu_flags, enum dma_data_direction cmd_dir)
> + u8 *upiu_flags, enum dma_data_direction cmd_dir)
> {
> struct utp_transfer_req_desc *req_desc = lrbp->utr_descriptor_ptr;
> u32 data_direction;
> @@ -2286,7 +2286,7 @@ static void ufshcd_prepare_req_desc_hdr(struct
> ufshcd_lrb *lrbp,
> * @upiu_flags: flags
> */
> static
> -void ufshcd_prepare_utp_scsi_cmd_upiu(struct ufshcd_lrb *lrbp, u32
> upiu_flags)
> +void ufshcd_prepare_utp_scsi_cmd_upiu(struct ufshcd_lrb *lrbp, u8
> +upiu_flags)
> {
> struct scsi_cmnd *cmd = lrbp->cmd;
> struct utp_upiu_req *ucd_req_ptr = lrbp->ucd_req_ptr; @@ -2319,7
> +2319,7 @@ void ufshcd_prepare_utp_scsi_cmd_upiu(struct ufshcd_lrb *lrbp,
> u32 upiu_flags)
> * @upiu_flags: flags
> */
> static void ufshcd_prepare_utp_query_req_upiu(struct ufs_hba *hba,
> - struct ufshcd_lrb *lrbp, u32 upiu_flags)
> + struct ufshcd_lrb *lrbp, u8 upiu_flags)
> {
> struct utp_upiu_req *ucd_req_ptr = lrbp->ucd_req_ptr;
> struct ufs_query *query = &hba->dev_cmd.query; @@ -2376,7 +2376,7
> @@ static inline void ufshcd_prepare_utp_nop_upiu(struct ufshcd_lrb *lrbp)
> static int ufshcd_compose_devman_upiu(struct ufs_hba *hba,
> struct ufshcd_lrb *lrbp)
> {
> - u32 upiu_flags;
> + u8 upiu_flags;
> int ret = 0;
>
> if ((hba->ufs_version == UFSHCI_VERSION_10) || @@ -2404,7 +2404,7
> @@ static int ufshcd_compose_devman_upiu(struct ufs_hba *hba,
> */
> static int ufshcd_comp_scsi_upiu(struct ufs_hba *hba, struct ufshcd_lrb
*lrbp) {
> - u32 upiu_flags;
> + u8 upiu_flags;
> int ret = 0;
>
> if ((hba->ufs_version == UFSHCI_VERSION_10) || @@ -6124,7 +6124,7
> @@ static int ufshcd_issue_devman_upiu_cmd(struct ufs_hba *hba,
> int tag;
> struct completion wait;
> unsigned long flags;
> - u32 upiu_flags;
> + u8 upiu_flags;
>
> down_read(&hba->clk_scaling_lock);
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-07-06 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200706123959epcas5p27fe7e69ea9e26089cffb2784a45e02a6@epcas5p2.samsung.com>
2020-07-06 12:39 ` [PATCH] scsi: ufs: change upiu_flags to be u8 Bean Huo
2020-07-06 14:03 ` Avri Altman
2020-07-06 15:33 ` Alim Akhtar [this message]
2020-07-08 6:06 ` Martin K. Petersen
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='02e501d653aa$c38c35e0$4aa4a1a0$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=huobean@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@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).