All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH] mmc: sdhci: tegra: fix wrong unit with busy_timeout
Date: Sat, 14 Nov 2020 03:28:08 +0800	[thread overview]
Message-ID: <202011140321.m4XwckLC-lkp@intel.com> (raw)
In-Reply-To: <20201113125354.3507-1-wsa+renesas@sang-engineering.com>

[-- Attachment #1: Type: text/plain, Size: 3250 bytes --]

Hi Wolfram,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on tegra/for-next]
[also build test ERROR on v5.10-rc3 next-20201113]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Wolfram-Sang/mmc-sdhci-tegra-fix-wrong-unit-with-busy_timeout/20201113-205511
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
config: arm64-randconfig-r033-20201113 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project 9e0c35655b6e8186baef8840b26ba4090503b554)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/d5481f1c9768ea4e5a43617ef5a853dd716d00f1
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Wolfram-Sang/mmc-sdhci-tegra-fix-wrong-unit-with-busy_timeout/20201113-205511
        git checkout d5481f1c9768ea4e5a43617ef5a853dd716d00f1
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> drivers/mmc/host/sdhci-tegra.c:1275:39: error: use of undeclared identifier 'MSECS_PER_SEC'
           if (cmd && cmd->busy_timeout >= 11 * MSECS_PER_SEC)
                                                ^
   1 error generated.

vim +/MSECS_PER_SEC +1275 drivers/mmc/host/sdhci-tegra.c

  1255	
  1256	static void tegra_sdhci_set_timeout(struct sdhci_host *host,
  1257					    struct mmc_command *cmd)
  1258	{
  1259		u32 val;
  1260	
  1261		/*
  1262		 * HW busy detection timeout is based on programmed data timeout
  1263		 * counter and maximum supported timeout is 11s which may not be
  1264		 * enough for long operations like cache flush, sleep awake, erase.
  1265		 *
  1266		 * ERASE_TIMEOUT_LIMIT bit of VENDOR_MISC_CTRL register allows
  1267		 * host controller to wait for busy state until the card is busy
  1268		 * without HW timeout.
  1269		 *
  1270		 * So, use infinite busy wait mode for operations that may take
  1271		 * more than maximum HW busy timeout of 11s otherwise use finite
  1272		 * busy wait mode.
  1273		 */
  1274		val = sdhci_readl(host, SDHCI_TEGRA_VENDOR_MISC_CTRL);
> 1275		if (cmd && cmd->busy_timeout >= 11 * MSECS_PER_SEC)
  1276			val |= SDHCI_MISC_CTRL_ERASE_TIMEOUT_LIMIT;
  1277		else
  1278			val &= ~SDHCI_MISC_CTRL_ERASE_TIMEOUT_LIMIT;
  1279		sdhci_writel(host, val, SDHCI_TEGRA_VENDOR_MISC_CTRL);
  1280	
  1281		__sdhci_set_timeout(host, cmd);
  1282	}
  1283	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 43168 bytes --]

  parent reply	other threads:[~2020-11-13 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 12:53 [RFC PATCH] mmc: sdhci: tegra: fix wrong unit with busy_timeout Wolfram Sang
2020-11-13 16:38 ` Thierry Reding
2020-11-13 18:34   ` Sowjanya Komatineni
2020-11-13 19:57     ` Thierry Reding
2020-11-14  0:15       ` Wolfram Sang
2020-11-13 19:28 ` kernel test robot [this message]
2020-11-14  2:45 ` kernel test robot

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=202011140321.m4XwckLC-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.