From: Biju Das <biju.das.jz@bp.renesas.com>
To: kernel test robot <lkp@intel.com>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Wolfram Sang <wsa-dev@sang-engineering.com>
Subject: RE: drivers/mmc/host/renesas_sdhi_core.c:951: undefined reference to `rdev_get_drvdata'
Date: Sat, 29 Mar 2025 06:41:38 +0000 [thread overview]
Message-ID: <TY3PR01MB11346FEE53574DBF768BA9B8686A32@TY3PR01MB11346.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <202503290554.zASQT70Q-lkp@intel.com>
Hi all,
> -----Original Message-----
> From: kernel test robot <lkp@intel.com>
> Sent: 28 March 2025 21:44
> Subject: drivers/mmc/host/renesas_sdhi_core.c:951: undefined reference to `rdev_get_drvdata'
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: acb4f33713b9f6cadb6143f211714c343465411c
> commit: fae80a99dc0320be854aa789cbe7ed0e1e574c61 mmc: renesas_sdhi: Add support for RZ/G3E SoC
> date: 2 weeks ago
> config: arm-randconfig-r111-20250328 (https://download.01.org/0day-
> ci/archive/20250329/202503290554.zASQT70Q-lkp@intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
> reproduce: (https://download.01.org/0day-ci/archive/20250329/202503290554.zASQT70Q-
> lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of the same
> patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes:
> | https://lore.kernel.org/oe-kbuild-all/202503290554.zASQT70Q-lkp@intel.
> | com/
>
> All errors (new ones prefixed by >>):
>
> arm-linux-gnueabi-ld: drivers/mmc/host/renesas_sdhi_core.o: in function
> `renesas_sdhi_regulator_is_enabled':
> >> drivers/mmc/host/renesas_sdhi_core.c:951: undefined reference to `rdev_get_drvdata'
> arm-linux-gnueabi-ld: drivers/mmc/host/renesas_sdhi_core.o: in function
> `renesas_sdhi_regulator_get_voltage':
> drivers/mmc/host/renesas_sdhi_core.c:961: undefined reference to `rdev_get_drvdata'
> arm-linux-gnueabi-ld: drivers/mmc/host/renesas_sdhi_core.o: in function
> `renesas_sdhi_regulator_disable':
> drivers/mmc/host/renesas_sdhi_core.c:927: undefined reference to `rdev_get_drvdata'
> arm-linux-gnueabi-ld: drivers/mmc/host/renesas_sdhi_core.o: in function
> `renesas_sdhi_regulator_enable':
> drivers/mmc/host/renesas_sdhi_core.c:939: undefined reference to `rdev_get_drvdata'
> arm-linux-gnueabi-ld: drivers/mmc/host/renesas_sdhi_core.o: in function
> `renesas_sdhi_regulator_set_voltage':
> drivers/mmc/host/renesas_sdhi_core.c:973: undefined reference to `rdev_get_drvdata'
> arm-linux-gnueabi-ld: drivers/mmc/host/renesas_sdhi_core.o: in function `renesas_sdhi_probe':
> >> drivers/mmc/host/renesas_sdhi_core.c:1177: undefined reference to `devm_regulator_register'
CONFIG_REGULATOR is not enabled in arm-randconfig-r111-20250328 that is leading
to this build issue.
I will send a fix by "select REGULATOR" in config MMC_SDHI
Cheers,
Biju
>
>
> vim +951 drivers/mmc/host/renesas_sdhi_core.c
>
> 948
> 949 static int renesas_sdhi_regulator_is_enabled(struct regulator_dev *rdev)
> 950 {
> > 951 struct tmio_mmc_host *host = rdev_get_drvdata(rdev);
> 952 u32 sd_status;
> 953
> 954 sd_status = sd_ctrl_read32(host, CTL_SD_STATUS);
> 955
> 956 return (sd_status & SD_STATUS_PWEN) ? 1 : 0;
> 957 }
> 958
> 959 static int renesas_sdhi_regulator_get_voltage(struct regulator_dev *rdev)
> 960 {
> > 961 struct tmio_mmc_host *host = rdev_get_drvdata(rdev);
> 962 u32 sd_status;
> 963
> 964 sd_status = sd_ctrl_read32(host, CTL_SD_STATUS);
> 965
> 966 return (sd_status & SD_STATUS_IOVS) ? 1800000 : 3300000;
> 967 }
> 968
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-29 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 21:43 kernel test robot
2025-03-29 6:41 ` Biju Das [this message]
2025-03-29 7:17 ` Wolfram Sang
2025-03-29 7:24 ` Biju Das
2025-03-29 7:28 ` Wolfram Sang
2025-03-29 7:37 ` Biju Das
2025-03-29 7:47 ` Wolfram Sang
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=TY3PR01MB11346FEE53574DBF768BA9B8686A32@TY3PR01MB11346.jpnprd01.prod.outlook.com \
--to=biju.das.jz@bp.renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ulf.hansson@linaro.org \
--cc=wsa-dev@sang-engineering.com \
/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
all inboxes | Powered by JetHome®