Agree. Will update.obj-$(CONFIG_SCSI_UFS_QCOM) += ufs-qcom.oIsn't ufs-configfs should be part of ufshcd-core? like ufs-sysfs ?
obj-$(CONFIG_SCSI_UFSHCD) += ufshcd-core.o
ufshcd-core-objs := ufshcd.o ufs-sysfs.o
+obj-$(CONFIG_SCSI_UFS_PROVISION) += ufs-configfs.o
User can just read the existing desc here and update the required fields as per need and write updated buffer to same configfs path.
+static ssize_t ufs_config_desc_show(struct config_item *item, char *buf,The read part already exist in ufs-sysfs.
+ u8 index)
+{
Let me try it out on my setup internally and update once I test this scenario
+ssize_t ufshcd_desc_configfs_store(struct config_item *item, const char *buf,
+ size_t count, u8 index)
+{
+if originally only lun0 was configured, and you want to configure a new set of luns -
+ /*
+ * First read the current configuration descriptor
+ * and then update with user provided parameters
+ */
luns 8 to 15 (config index 0x1) - won't the read fail in that case?
Thanks,
Avri