From: Bean Huo <huobean@gmail.com>
To: alim.akhtar@samsung.com, avri.altman@wdc.com,
pedrom.sousa@synopsys.com, 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,
Bean Huo <huobean@gmail.com>
Subject: [PATCH v1 0/3] use UFS device indicated maximum LU number
Date: Fri, 10 Jan 2020 19:36:03 +0100 [thread overview]
Message-ID: <20200110183606.10102-1-huobean@gmail.com> (raw)
According to Jedec standard UFS 3.0 and UFS 2.1 Spec, Maximum
number of logical units supported by the UFS device is specified
by parameter bMaxNumberLU in Geometry Descriptor. This series
of patches is to delete macro definition UFS_UPIU_MAX_GENERAL_LUN,
and switch to use indicated value in descriptor instead.
Bean Huo (3):
scsi: ufs: add max_lu_supported in struct ufs_dev_info
scsi: ufs: initialize max_lu_supported while booting
scsi: ufs: use UFS device indicated maximum LU number
drivers/scsi/ufs/ufs-sysfs.c | 2 +-
drivers/scsi/ufs/ufs.h | 14 +++++++---
drivers/scsi/ufs/ufshcd.c | 51 +++++++++++++++++++++++++++++++++---
3 files changed, 60 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2020-01-10 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 18:36 Bean Huo [this message]
2020-01-10 18:36 ` [PATCH 1/3] scsi: ufs: add max_lu_supported in struct ufs_dev_info Bean Huo
2020-01-11 22:43 ` Bart Van Assche
2020-01-13 18:43 ` asutoshd
2020-01-10 18:36 ` [PATCH 2/3] scsi: ufs: initialize max_lu_supported while booting Bean Huo
2020-01-11 22:42 ` Bart Van Assche
2020-01-12 8:41 ` Avri Altman
2020-01-12 9:52 ` [EXT] " Bean Huo (beanhuo)
2020-01-13 18:44 ` asutoshd
2020-01-10 18:36 ` [PATCH 3/3] scsi: ufs: use UFS device indicated maximum LU number Bean Huo
2020-01-11 22:50 ` Bart Van Assche
2020-01-13 18:45 ` asutoshd
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=20200110183606.10102-1-huobean@gmail.com \
--to=huobean@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pedrom.sousa@synopsys.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).