From: Sayali Lokhande <sayalil@codeaurora.org>
To: Avri Altman <Avri.Altman@wdc.com>,
"subhashj@codeaurora.org" <subhashj@codeaurora.org>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"vivek.gautam@codeaurora.org" <vivek.gautam@codeaurora.org>,
"rnayak@codeaurora.org" <rnayak@codeaurora.org>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"evgreen@chromium.org" <evgreen@chromium.org>,
"riteshh@codeaurora.org" <riteshh@codeaurora.org>
Cc: "stummala@codeaurora.org" <stummala@codeaurora.org>,
"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"jlbec@evilplan.org" <jlbec@evilplan.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V14 2/2] scsi: ufs: Add configfs support for UFS provisioning
Date: Thu, 4 Oct 2018 16:10:27 +0530 [thread overview]
Message-ID: <4aca5fe6-43db-c7b0-b255-622ccec4d1fc@codeaurora.org> (raw)
In-Reply-To: <SN6PR04MB4925D198F7AE8961254F43C9FC170@SN6PR04MB4925.namprd04.prod.outlook.com>
On 9/24/2018 3:33 PM, Avri Altman wrote:
>> obj-$(CONFIG_SCSI_UFS_QCOM) += ufs-qcom.o
>> obj-$(CONFIG_SCSI_UFSHCD) += ufshcd-core.o
>> ufshcd-core-objs := ufshcd.o ufs-sysfs.o
>> +obj-$(CONFIG_SCSI_UFS_PROVISION) += ufs-configfs.o
> Isn't ufs-configfs should be part of ufshcd-core? like ufs-sysfs ?
Agree. Will update.
>
>
>> +static ssize_t ufs_config_desc_show(struct config_item *item, char *buf,
>> + u8 index)
>> +{
> The read part already exist in ufs-sysfs.
User can just read the existing desc here and update the required fields
as per need and write updated buffer to same configfs path.
I think its better to have both r/w functionality here.
>
>> +ssize_t ufshcd_desc_configfs_store(struct config_item *item, const char *buf,
>> + size_t count, u8 index)
>> +{
>
>> +
>> + /*
>> + * First read the current configuration descriptor
>> + * and then update with user provided parameters
>> + */
> if originally only lun0 was configured, and you want to configure a new set of luns -
> luns 8 to 15 (config index 0x1) - won't the read fail in that case?
Let me try it out on my setup internally and update once I test this
scenario
>
> Thanks,
> Avri
next prev parent reply other threads:[~2018-10-04 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1537770516-28410-1-git-send-email-sayalil@codeaurora.org>
2018-09-24 6:28 ` [PATCH V14 1/2] scsi: ufs: set the device reference clock setting Sayali Lokhande
2018-09-24 7:58 ` Avri Altman
2018-09-24 8:47 ` Sayali Lokhande
2018-10-12 22:50 ` Doug Anderson
2018-10-15 10:57 ` Sayali Lokhande
2018-09-24 6:28 ` [PATCH V14 2/2] scsi: ufs: Add configfs support for UFS provisioning Sayali Lokhande
2018-09-24 10:03 ` Avri Altman
2018-10-04 10:40 ` Sayali Lokhande [this message]
2018-09-24 20:38 ` Evan Green
2018-10-03 18:01 ` Evan Green
2018-10-04 7:39 ` Sayali Lokhande
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=4aca5fe6-43db-c7b0-b255-622ccec4d1fc@codeaurora.org \
--to=sayalil@codeaurora.org \
--cc=Avri.Altman@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=jlbec@evilplan.org \
--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=stummala@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