From: kernel test robot <lkp@intel.com>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Sasha Levin <sashal@kernel.org>
Subject: [stable:linux-5.10.y 9092/9999] arch/mips/alchemy/common/dbdma.c:632:14: error: 'dma_default_coherent' undeclared; did you mean 'dma_free_coherent'?
Date: Sat, 12 Aug 2023 06:47:53 +0800 [thread overview]
Message-ID: <202308120654.PVrwSCZ7-lkp@intel.com> (raw)
Hi Manuel,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.10.y
head: ec585727b63d12f9683140fe4b8eb8e564dd3aa0
commit: 619672bf2d04cdc1bc3925defd0312c2ef11e5d0 [9092/9999] MIPS: Alchemy: fix dbdma2
config: mips-randconfig-r025-20230812 (https://download.01.org/0day-ci/archive/20230812/202308120654.PVrwSCZ7-lkp@intel.com/config)
compiler: mipsel-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230812/202308120654.PVrwSCZ7-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/202308120654.PVrwSCZ7-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/mips/alchemy/common/dbdma.c: In function 'au1xxx_dbdma_put_source':
>> arch/mips/alchemy/common/dbdma.c:632:14: error: 'dma_default_coherent' undeclared (first use in this function); did you mean 'dma_free_coherent'?
632 | if (!dma_default_coherent)
| ^~~~~~~~~~~~~~~~~~~~
| dma_free_coherent
arch/mips/alchemy/common/dbdma.c:632:14: note: each undeclared identifier is reported only once for each function it appears in
arch/mips/alchemy/common/dbdma.c: In function 'au1xxx_dbdma_put_dest':
arch/mips/alchemy/common/dbdma.c:695:14: error: 'dma_default_coherent' undeclared (first use in this function); did you mean 'dma_free_coherent'?
695 | if (!dma_default_coherent)
| ^~~~~~~~~~~~~~~~~~~~
| dma_free_coherent
vim +632 arch/mips/alchemy/common/dbdma.c
586
587 /*
588 * Put a source buffer into the DMA ring.
589 * This updates the source pointer and byte count. Normally used
590 * for memory to fifo transfers.
591 */
592 u32 au1xxx_dbdma_put_source(u32 chanid, dma_addr_t buf, int nbytes, u32 flags)
593 {
594 chan_tab_t *ctp;
595 au1x_ddma_desc_t *dp;
596
597 /*
598 * I guess we could check this to be within the
599 * range of the table......
600 */
601 ctp = *(chan_tab_t **)chanid;
602
603 /*
604 * We should have multiple callers for a particular channel,
605 * an interrupt doesn't affect this pointer nor the descriptor,
606 * so no locking should be needed.
607 */
608 dp = ctp->put_ptr;
609
610 /*
611 * If the descriptor is valid, we are way ahead of the DMA
612 * engine, so just return an error condition.
613 */
614 if (dp->dscr_cmd0 & DSCR_CMD0_V)
615 return 0;
616
617 /* Load up buffer address and byte count. */
618 dp->dscr_source0 = buf & ~0UL;
619 dp->dscr_cmd1 = nbytes;
620 /* Check flags */
621 if (flags & DDMA_FLAGS_IE)
622 dp->dscr_cmd0 |= DSCR_CMD0_IE;
623 if (flags & DDMA_FLAGS_NOIE)
624 dp->dscr_cmd0 &= ~DSCR_CMD0_IE;
625
626 /*
627 * There is an erratum on certain Au1200/Au1550 revisions that could
628 * result in "stale" data being DMA'ed. It has to do with the snoop
629 * logic on the cache eviction buffer. dma_default_coherent is set
630 * to false on these parts.
631 */
> 632 if (!dma_default_coherent)
633 dma_cache_wback_inv(KSEG0ADDR(buf), nbytes);
634 dp->dscr_cmd0 |= DSCR_CMD0_V; /* Let it rip */
635 wmb(); /* drain writebuffer */
636 dma_cache_wback_inv((unsigned long)dp, sizeof(*dp));
637 ctp->chan_ptr->ddma_dbell = 0;
638 wmb(); /* force doorbell write out to dma engine */
639
640 /* Get next descriptor pointer. */
641 ctp->put_ptr = phys_to_virt(DSCR_GET_NXTPTR(dp->dscr_nxtptr));
642
643 /* Return something non-zero. */
644 return nbytes;
645 }
646 EXPORT_SYMBOL(au1xxx_dbdma_put_source);
647
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-11 22:49 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=202308120654.PVrwSCZ7-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=manuel.lauss@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=tsbogend@alpha.franken.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 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.