From: Yaniv Gardi <ygardi@codeaurora.org>
To: James.Bottomley@HansenPartnership.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org, akinobu.mita@gmail.com,
santoshsy@gmail.com, linux-scsi-owner@vger.kernel.org,
subhashj@codeaurora.org, ygardi@codeaurora.org,
pebolle@tiscali.nl, gbroner@codeaurora.org
Subject: [PATCH v3 0/4] fixing building errors and warnings when components
Date: Sun, 7 Jun 2015 19:27:00 +0300 [thread overview]
Message-ID: <1433694425-23478-1-git-send-email-ygardi@codeaurora.org> (raw)
V3:
In this version, in ufshcd-pltfrm.c probe and remove function, added:
__module_get(ufs_variant_pdev->dev.driver->owner);
module_put(ufs_variant_pdev->dev.driver->owner);
in order to maintain a reference counter to prevent unloading
ufs-qcom component if it is the variant that ufshcd-pltfrm is using.
V2:
In this Version, comments from reviewers were addressed
and also, added another change: PATCH v2 4/4
In this change we glue the variant attributes (vops, etc)
at the time of the platform probing, so they can be used
by the driver when it doing its initialization phase.
V1:
The following combination of components, when SCSI_UFS_QCOM=y
and PHY_QCOM_UFS=m is illegal and causes build errors.
The 3rd patch in the series enables the SCSI_UFS_QCOM component to
be compiled as a module (by changing its configuration to tristate).
So now, compiling SCSI_UFS_QCOM=m forces PHY_QCOM_UFS=m, and
SCSI_UFS_QCOM=y forces PHY_QCOM_UFS=y.
In addition, when PHY_QCOM_UFS=m, external functions in
phy-ufs-qcom.c should be exported. The 1st patch fixes it.
Another issue that we see when SCSI_UFS_QCOM=m is a warning that
the 2nd patch fixes.
notice:
checkpatch gives an error on the commit message of patch 1/3
in the series. Ignore as the commit message is the build errors
that this patch fixes.
Yaniv Gardi (4):
phy: qcom-ufs: fix build error when the component is built as a module
scsi: ufs-qcom: fix compilation warning if compiled as a module
scsi: ufs-qcom: update configuration option of SCSI_UFS_QCOM component
scsi: ufs: probe and init of variant driver from the platform device
.../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 8 ++++
drivers/phy/phy-qcom-ufs.c | 11 +++++
drivers/scsi/ufs/Kconfig | 2 +-
drivers/scsi/ufs/ufs-qcom.c | 48 +++++++++++++++++++++-
drivers/scsi/ufs/ufshcd-pltfrm.c | 45 ++++++++++++++------
5 files changed, 98 insertions(+), 16 deletions(-)
--
1.8.5.2
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next reply other threads:[~2015-06-07 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 16:27 Yaniv Gardi [this message]
2015-06-07 16:27 ` [PATCH v3 1/4] phy: qcom-ufs: fix build error when the component is built as a module Yaniv Gardi
2015-06-07 16:27 ` [PATCH v3 2/4] scsi: ufs-qcom: fix compilation warning if compiled " Yaniv Gardi
2015-06-07 16:27 ` [PATCH v3 3/4] scsi: ufs-qcom: update configuration option of SCSI_UFS_QCOM component Yaniv Gardi
2015-06-07 16:27 ` [PATCH v3 4/4] scsi: ufs: probe and init of variant driver from the platform device Yaniv Gardi
[not found] ` <1433694425-23478-5-git-send-email-ygardi-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-06-08 14:51 ` Akinobu Mita
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=1433694425-23478-1-git-send-email-ygardi@codeaurora.org \
--to=ygardi@codeaurora.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akinobu.mita@gmail.com \
--cc=gbroner@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=santoshsy@gmail.com \
--cc=subhashj@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