From: Christoph Hellwig <hch@infradead.org>
To: Sayali Lokhande <sayalil@codeaurora.org>
Cc: subhashj@codeaurora.org, cang@codeaurora.org,
vivek.gautam@codeaurora.org, rnayak@codeaurora.org,
vinholikatti@gmail.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com, asutoshd@codeaurora.org,
evgreen@chromium.org, riteshh@codeaurora.org,
linux-scsi@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 2/3] scsi: ufs: Add ufs provisioning support
Date: Thu, 14 Jun 2018 08:39:14 -0700 [thread overview]
Message-ID: <20180614153914.GA3906@infradead.org> (raw)
In-Reply-To: <1528981432-23065-3-git-send-email-sayalil@codeaurora.org>
On Thu, Jun 14, 2018 at 06:33:51PM +0530, Sayali Lokhande wrote:
> A new api ufshcd_do_config_device() is added in driver
> to support UFS provisioning at runtime. Configfs support
> is added to trigger provisioning.
> Device and Unit configurable parameters are parsed from
> vendor specific provisioning data or file and
> passed via configfs node at runtime to provision ufs device.
>
> Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
Please make that code conditionally compiled based on a config option.
For most UFS users there is no need to ever enable it.
next prev parent reply other threads:[~2018-06-14 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1528981432-23065-1-git-send-email-sayalil@codeaurora.org>
2018-06-14 13:03 ` [PATCH V3 1/3] scsi: ufs: set the device reference clock setting Sayali Lokhande
2018-06-20 7:26 ` Adrian Hunter
2018-06-20 18:01 ` Rob Herring
2018-06-21 9:11 ` sayali
2018-06-21 9:19 ` Adrian Hunter
2018-06-14 13:03 ` [PATCH V3 2/3] scsi: ufs: Add ufs provisioning support Sayali Lokhande
2018-06-14 15:39 ` Christoph Hellwig [this message]
2018-06-15 2:58 ` Kyuho Choi
2018-06-21 9:17 ` sayali
2018-06-14 13:03 ` [PATCH V3 3/3] scsi: ufs: Add configfs support for ufs provisioning Sayali Lokhande
2018-06-14 15:29 ` kbuild test robot
2018-06-14 17:53 ` kbuild test robot
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=20180614153914.GA3906@infradead.org \
--to=hch@infradead.org \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=riteshh@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=sayalil@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=vivek.gautam@codeaurora.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