Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1177274ybl; Sat, 18 Jan 2020 20:43:01 -0800 (PST) X-Google-Smtp-Source: APXvYqyh2/+GlaBcUdCeMVjzCp5l3WXgIt6y8hTH6YX1EwUv8zb897hA9lcukwOEX3SH6n+JbGYg X-Received: by 2002:a54:4713:: with SMTP id k19mr8940829oik.113.1579408981075; Sat, 18 Jan 2020 20:43:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579408981; cv=none; d=google.com; s=arc-20160816; b=rPQcmMyhDmbAIzKjcCiw5rJGJAXa7Dh96Lvd49gtgA1VK/Q9NfPyHKzpz2VauZ/XLX y6aluZ9Ri7tB4zDOpHPvfHTfDwy2rWM0amnclnwr4b36XdDp8VBR98wUC3cdDwMHg6fU zArMaGHJxYgvks7yjpJOGb3feQ2/ruQTM1Xg1u9MAJviQ1RJOVtCbM2n+D0n+Qipvr02 Vt67FOq6boMyyp3ggWd3YPabo4g47qtFYdDd4oHebz3Te5UGXqcSxDvSP2DVSC8wLzSr edK42nQ9H9EwEZxDQAsb8MJsWcmc8EOy7JFRsl/fYYpmd9RF4p3LsYsaxfXhKVSL0qic 1eVw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=mrVtIGWJwkOZNC1CEGskb3pHdiV7yfBFUjPb/kxYDzk=; b=r4zO/bueyYVP/5GP8MWxIpufnf0+mKlJPnWwrjB4C4rlZEA3VoESfud+dIprUxR7K+ GWCjY6r8X8Udy5+fut+BjSE3+K0YfUTk4RXDzqENI70zVt5H72c0y3LSaryIXwwIv6N4 xo7iQowZna6dSIHSOGm6e5n/DTvxliHVTUmagr9tZ9Qvd0schX5hQ9AH9ng93Ha2fL0b lB4UieyqZu7sKi4Ax2ahRNwjdNZKp4cOwrXml+YcpcGfVuRbQN/mOw9NQvOPu/yJS0rl /sBGNHsGSWIJcmF2M2RNKkHmlV99ahZOhXD9DXoDrKRYlK8eJTmgrdo2BXhtv4spy5vf oS3A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NdPk8RHB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i12si18038409otk.215.2020.01.18.20.42.38; Sat, 18 Jan 2020 20:43:01 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NdPk8RHB; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726476AbgASEkf (ORCPT + 99 others); Sat, 18 Jan 2020 23:40:35 -0500 Received: from mail-vs1-f66.google.com ([209.85.217.66]:42877 "EHLO mail-vs1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726046AbgASEkf (ORCPT ); Sat, 18 Jan 2020 23:40:35 -0500 Received: by mail-vs1-f66.google.com with SMTP id b79so17148909vsd.9; Sat, 18 Jan 2020 20:40:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=mrVtIGWJwkOZNC1CEGskb3pHdiV7yfBFUjPb/kxYDzk=; b=NdPk8RHBNqTIJz2G3f9QCNmuyqD7QMqkGUGd6k4djmDn9RcSf94G2IOEIM1A+4Rhwr lrzdEIe/XJVB0ro59n2RTKSCVEZSU2H//t1kO7O8Oy06mENrr/n+j+NKHgCVLjZOmdIQ bxmeClXscB2tu9vnCfbT4oU80X8mgRzRMoBGYjpyqgu3jMEaS5zPnT+hV2iOoZBClHMg wegialB5Y83zraw+pb17lbLTr+cUBe8kgMU092M+tLdUa186Z8YCZ/SJW7vuZGlY1fVb iWEnjtdwiV37+HvohjrsiopkQ0W0TDAczF/SG26jY00PTWHYIE5qKUAXQLP8DvK4HSmS 40jA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=mrVtIGWJwkOZNC1CEGskb3pHdiV7yfBFUjPb/kxYDzk=; b=eXWFPLbA1Dw+9M5BDXQK482Y7gzizr7RZchrh8vZgeWZNSfZD66QdLGcj2Bgsxnu1N aiQVG6IV3epHVSJkAGcaI+O+NQGSrXx/vNcWsBmFzyQNm5u9GJo/n8kq+CoXeVpgp06+ Ev8jf6CZ0UmRhZ4/zt1oI0n9OPqWQMf9hV6syYhBGuxo9sFiRW9hm1ecRWaQOKGumtxS YVmRGOrCdUhc7hNmpQoaVVXwUo5TPb6TAbm15j8JVWDBJPrXY5Hog7uE8vtDEwxvQ2k1 AuBpIoaF4R2opXGRSJKkKSAIaN+TjzoxeZETdbFezHUt4oS6snSZcK6sarFDjBdxvzSB p3Gw== X-Gm-Message-State: APjAAAX3eh4D3G3bsKcUF4CGF0PRejG2f4QXDzZJvy1Le7lR0nLmgtGB UUkme5nznyqdrP4SpJg10xFUVh3osfj141YzIXM= X-Received: by 2002:a67:1447:: with SMTP id 68mr9174794vsu.76.1579408833735; Sat, 18 Jan 2020 20:40:33 -0800 (PST) MIME-Version: 1.0 References: <20200119001327.29155-1-huobean@gmail.com> In-Reply-To: <20200119001327.29155-1-huobean@gmail.com> From: Alim Akhtar Date: Sun, 19 Jan 2020 10:09:56 +0530 Message-ID: Subject: Re: [PATCH v3 0/8] Use UFS device indicated maximum LU number To: Bean Huo Cc: Alim Akhtar , Avri Altman , asutoshd@codeaurora.org, "James E.J. Bottomley" , "Martin K. Petersen" , Stanley Chu , "Bean Huo (beanhuo)" , Bart Van Assche , Tomas Winkler , Can Guo , linux-scsi@vger.kernel.org, open list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bean Your patches based on which tree? At least on Jame's for-next, it give compilation errors. (git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git) Looks like patch-2 introduces below error: =3D=3D=3D=3D=3D=3D=3D=3D drivers/scsi/ufs/ufs-qcom.c: In function =E2=80=98ufs_qcom_apply_dev_quirks= =E2=80=99: drivers/scsi/ufs/ufs-qcom.c:955:34: error: incompatible types when initializing type =E2=80=98struct ufs_dev_info *=E2=80=99 using type =E2=80= =98struct ufs_dev_info=E2=80=99 struct ufs_dev_info *dev_info =3D hba->dev_info; ^~~ drivers/scsi/ufs/ufs-qcom.c:957:14: error: =E2=80=98struct ufs_dev_info=E2= =80=99 has no member named =E2=80=98dev_quirks=E2=80=99 if (dev_info->dev_quirks & UFS_DEVICE_QUIRK_HOST_PA_SAVECONFIGTIME) ^~ scripts/Makefile.build:265: recipe for target 'drivers/scsi/ufs/ufs-qcom.o' failed make[3]: *** [drivers/scsi/ufs/ufs-qcom.o] Error 1 =3D=3D=3D=3D=3D=3D=3D=3D=3D On Sun, Jan 19, 2020 at 5:44 AM Bean Huo wrote: > > This series of patches is to simplify UFS driver initialization flow > and add a new parameter max_lu_supported used to specify how many LUs > supported by the UFS device. > This series of patches being tested on my two platforms, Qualcomm SOC > based and Hisilicon SOC based platforms. > > v1-v2: > 1. Split ufshcd_probe_hba() based on its called flow > 2. Delete two unnecessary functions > 3. Add a fixup patch > v2-v3: > 1. Combine patches 7/9 and 8/9 of v2 to patch 7/8 of v3 > 2. Change patches 1/8 and 5/8 subject > 3. Change the name of two functions in patch 7/8 > > Bean Huo (8): > scsi: ufs: Fix ufshcd_probe_hba() reture value in case > ufshcd_scsi_add_wlus() fails > scsi: ufs: Delete struct ufs_dev_desc > scsi: ufs: Split ufshcd_probe_hba() based on its called flow > scsi: ufs: move ufshcd_get_max_pwr_mode() to ufs_init_params() > scsi: ufs: Inline two functions into their callers > scsi: ufs: Delete is_init_prefetch from struct ufs_hba > scsi: ufs: Add max_lu_supported in struct ufs_dev_info > scsi: ufs: Use UFS device indicated maximum LU number > > drivers/scsi/ufs/ufs-mediatek.c | 7 +- > drivers/scsi/ufs/ufs-qcom.c | 6 +- > drivers/scsi/ufs/ufs-sysfs.c | 2 +- > drivers/scsi/ufs/ufs.h | 25 ++- > drivers/scsi/ufs/ufs_quirks.h | 9 +- > drivers/scsi/ufs/ufshcd.c | 276 +++++++++++++++++++------------- > drivers/scsi/ufs/ufshcd.h | 9 +- > 7 files changed, 196 insertions(+), 138 deletions(-) > > -- > 2.17.1 > --=20 Regards, Alim