From: kernel test robot <lkp@intel.com>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: oe-kbuild-all@lists.linux.dev, Vinod Koul <vkoul@kernel.org>
Subject: [linux-next:master 4870/6658] drivers/dma/bcm2835-dma.c:878:12: warning: 'bcm2835_dma_suspend_late' defined but not used
Date: Tue, 7 Jan 2025 15:39:24 +0800 [thread overview]
Message-ID: <202501071533.yrFb156H-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4e16367cfe0ce395f29d0482b78970cce8e1db73
commit: 9602a843cb3a16df8930eb9b046aa7aeb769521b [4870/6658] dmaengine: bcm2835-dma: Prevent suspend if DMA channel is busy
config: arm-randconfig-004-20250107 (https://download.01.org/0day-ci/archive/20250107/202501071533.yrFb156H-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250107/202501071533.yrFb156H-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/202501071533.yrFb156H-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/dma/bcm2835-dma.c:878:12: warning: 'bcm2835_dma_suspend_late' defined but not used [-Wunused-function]
878 | static int bcm2835_dma_suspend_late(struct device *dev)
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/bcm2835_dma_suspend_late +878 drivers/dma/bcm2835-dma.c
877
> 878 static int bcm2835_dma_suspend_late(struct device *dev)
879 {
880 struct bcm2835_dmadev *od = dev_get_drvdata(dev);
881 struct bcm2835_chan *c, *next;
882
883 list_for_each_entry_safe(c, next, &od->ddev.channels,
884 vc.chan.device_node) {
885 void __iomem *chan_base = c->chan_base;
886
887 /* Check if DMA channel is busy */
888 if (readl(chan_base + BCM2835_DMA_ADDR))
889 return -EBUSY;
890 }
891
892 return 0;
893 }
894
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-07 7:40 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=202501071533.yrFb156H-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vkoul@kernel.org \
--cc=wahrenst@gmx.net \
/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.