Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, kbuild-all@01.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [sound:topic/hda-bus-ops-cleanup 2/3] sound/hda/hdac_bus.c:228:6: error: implicit declaration of function 'readl'; did you mean 'd_real'?
Date: Fri, 9 Aug 2019 07:13:40 +0800	[thread overview]
Message-ID: <201908090737.NIHFkC40%lkp@intel.com> (raw)

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

tree:   https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound.git topic/hda-bus-ops-cleanup
head:   d4ff1b3917a529bdc75592af6b1504ad6c4029f7
commit: 19abfefd4c7604993d1c31e098a3f48bdafe334d [2/3] ALSA: hda: Direct MMIO accesses
config: arm-defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 19abfefd4c7604993d1c31e098a3f48bdafe334d
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=arm 

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

All errors (new ones prefixed by >>):

   sound/hda/hdac_bus.c: In function 'snd_hdac_aligned_read':
>> sound/hda/hdac_bus.c:228:6: error: implicit declaration of function 'readl'; did you mean 'd_real'? [-Werror=implicit-function-declaration]
     v = readl(aligned_addr);
         ^~~~~
         d_real
   sound/hda/hdac_bus.c: In function 'snd_hdac_aligned_write':
>> sound/hda/hdac_bus.c:244:2: error: implicit declaration of function 'writel' [-Werror=implicit-function-declaration]
     writel(v, aligned_addr);
     ^~~~~~
   cc1: some warnings being treated as errors

vim +228 sound/hda/hdac_bus.c

   218	
   219	#ifdef CONFIG_SND_HDA_ALIGNED_MMIO
   220	/* Helpers for aligned read/write of mmio space, for Tegra */
   221	unsigned int snd_hdac_aligned_read(void __iomem *addr, unsigned int mask)
   222	{
   223		void __iomem *aligned_addr =
   224			(void __iomem *)((unsigned long)(addr) & ~0x3);
   225		unsigned int shift = ((unsigned long)(addr) & 0x3) << 3;
   226		unsigned int v;
   227	
 > 228		v = readl(aligned_addr);
   229		return (v >> shift) & mask;
   230	}
   231	EXPORT_SYMBOL_GPL(snd_hdac_aligned_read);
   232	
   233	void snd_hdac_aligned_write(unsigned int val, void __iomem *addr,
   234				    unsigned int mask)
   235	{
   236		void __iomem *aligned_addr =
   237			(void __iomem *)((unsigned long)(addr) & ~0x3);
   238		unsigned int shift = ((unsigned long)(addr) & 0x3) << 3;
   239		unsigned int v;
   240	
   241		v = readl(aligned_addr);
   242		v &= ~(mask << shift);
   243		v |= val << shift;
 > 244		writel(v, aligned_addr);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



                 reply	other threads:[~2019-08-08 23:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201908090737.NIHFkC40%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kbuild-all@01.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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