From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] phy: qcom-ufs: export symbols needed by main drivers
Date: Mon, 2 Feb 2015 20:07:56 +0530 [thread overview]
Message-ID: <54CF8BC4.8080200@ti.com> (raw)
In-Reply-To: <7dbea2dd0edafbb35cbd36f8a9b135ed.squirrel@www.codeaurora.org>
On Monday 02 February 2015 08:01 PM, ygardi at codeaurora.org wrote:
>> The qcom ufs phy support is split into three separate loadable
>> modules, however none of the interfaces are exported, resulting
>> in a link error:
>>
>> ERROR: "ufs_qcom_phy_power_off" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_power_on" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_exit" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_generic_probe" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_init_vregulators"
>> [drivers/phy/phy-qcom-ufs-qmp-20nm.ko] undefined!
>> ERROR: "ufs_qcom_phy_init_clks" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_calibrate" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_remove" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "get_ufs_qcom_phy" [drivers/phy/phy-qcom-ufs-qmp-20nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_power_off" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_power_on" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_exit" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_generic_probe" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_init_vregulators"
>> [drivers/phy/phy-qcom-ufs-qmp-14nm.ko] undefined!
>> ERROR: "ufs_qcom_phy_init_clks" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_calibrate" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>> ERROR: "ufs_qcom_phy_remove" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>> ERROR: "get_ufs_qcom_phy" [drivers/phy/phy-qcom-ufs-qmp-14nm.ko]
>> undefined!
>>
>> This exports all of the symbols that are provided by the base library
>> module and used by the two driver modules.
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> Fixes: adaafaa393ef ("phy: qcom-ufs: add support for QUALCOMM Technologies
>> UFS PHY drivers")
>> ---
>>
>> The broken patch is currently in the scsi tree, so if the phy maintainer
>> thinks that my fix is correct, it should go there too.
>
> I believe that exporting all interface functions is a good solution.
>
>>
>> An alternative approach would be to link all three phy-qcom-ufs source
>> files into a single module.
where is this driver merged? it's not in linux-phy.
-Kishon
next prev parent reply other threads:[~2015-02-02 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 16:18 [PATCH] phy: qcom-ufs: export symbols needed by main drivers Arnd Bergmann
2015-02-02 14:31 ` ygardi at codeaurora.org
2015-02-02 14:37 ` Kishon Vijay Abraham I [this message]
2015-02-02 14:42 ` ygardi at codeaurora.org
2015-02-02 15:30 ` James Bottomley
2015-02-02 16:26 ` hch at lst.de
2015-02-02 17:55 ` James Bottomley
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=54CF8BC4.8080200@ti.com \
--to=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).