From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: clang-built-linux@googlegroups.com, arm@kernel.org,
kbuild-all@lists.01.org, Maxime Ripard <maxime@cerno.tech>,
linux-arm-kernel@lists.infradead.org
Subject: [soc:sunxi/rework-mbus 8/8] drivers/soc/sunxi/sunxi_mbus.c:93:8: error: implicit declaration of function 'dma_direct_set_offset'
Date: Tue, 24 Nov 2020 23:20:06 +0800 [thread overview]
Message-ID: <202011242301.OdU4UNbm-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4631 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git sunxi/rework-mbus
head: 16fee29b07358293f135759d9fdbf1267da57ebd
commit: 16fee29b07358293f135759d9fdbf1267da57ebd [8/8] dma-mapping: remove the dma_direct_set_offset export
config: arm64-randconfig-r012-20201124 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project df9ae5992889560a8f3c6760b54d5051b47c7bf5)
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://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?id=16fee29b07358293f135759d9fdbf1267da57ebd
git remote add soc https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git
git fetch --no-tags soc sunxi/rework-mbus
git checkout 16fee29b07358293f135759d9fdbf1267da57ebd
# 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/soc/sunxi/sunxi_mbus.c:93:8: error: implicit declaration of function 'dma_direct_set_offset' [-Werror,-Wimplicit-function-declaration]
ret = dma_direct_set_offset(dev, PHYS_OFFSET, 0, SZ_4G);
^
1 error generated.
vim +/dma_direct_set_offset +93 drivers/soc/sunxi/sunxi_mbus.c
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 64
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 65 static int sunxi_mbus_notifier(struct notifier_block *nb,
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 66 unsigned long event, void *__dev)
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 67 {
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 68 struct device *dev = __dev;
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 69 int ret;
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 70
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 71 if (event != BUS_NOTIFY_ADD_DEVICE)
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 72 return NOTIFY_DONE;
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 73
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 74 /*
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 75 * Only the devices that need a large memory bandwidth do DMA
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 76 * directly over the memory bus (called MBUS), instead of going
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 77 * through the regular system bus.
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 78 */
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 79 if (!of_device_compatible_match(dev->of_node, sunxi_mbus_devices))
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 80 return NOTIFY_DONE;
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 81
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 82 /*
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 83 * Devices with an interconnects property have the MBUS
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 84 * relationship described in their DT and dealt with by
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 85 * of_dma_configure, so we can just skip them.
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 86 *
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 87 * Older DTs or SoCs who are not clearly understood need to set
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 88 * that DMA offset though.
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 89 */
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 90 if (of_find_property(dev->of_node, "interconnects", NULL))
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 91 return NOTIFY_DONE;
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 92
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 @93 ret = dma_direct_set_offset(dev, PHYS_OFFSET, 0, SZ_4G);
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 94 if (ret)
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 95 dev_err(dev, "Couldn't setup our DMA offset: %d\n", ret);
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 96
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 97 return NOTIFY_DONE;
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 98 }
b4bdc4fbf8d0122 Maxime Ripard 2020-11-06 99
:::::: The code at line 93 was first introduced by commit
:::::: b4bdc4fbf8d01227702068703ae2cd82ff25c3db soc: sunxi: Deal with the MBUS DMA offsets in a central place
:::::: TO: Maxime Ripard <maxime@cerno.tech>
:::::: CC: Maxime Ripard <maxime@cerno.tech>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39518 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-11-24 15:21 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=202011242301.OdU4UNbm-lkp@intel.com \
--to=lkp@intel.com \
--cc=arm@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
/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).