public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: Paul Gazzillo <paul@pgazz.com>,
	Necip Fazil Yildiran <fazilyildiran@gmail.com>,
	<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: Re: kismet: WARNING: unmet direct dependencies detected for AX45MP_L2_CACHE when selected by ARCH_R9A07G043
Date: Wed, 10 Dec 2025 14:45:14 +0000	[thread overview]
Message-ID: <20251210144514.000021ed@huawei.com> (raw)
In-Reply-To: <202512100411.WxJU2No9-lkp@intel.com>

On Wed, 10 Dec 2025 04:42:42 +0100
kernel test robot <lkp@intel.com> wrote:

> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   c9b47175e9131118e6f221cc8fb81397d62e7c91
> commit: 4d1608d0ab3365d1ef9447bdbc0cb4c0962f1774 cache: Make top level Kconfig menu a boolean dependent on RISCV
> date:   3 weeks ago
> config: riscv-kismet-CONFIG_AX45MP_L2_CACHE-CONFIG_ARCH_R9A07G043-0-0 (https://download.01.org/0day-ci/archive/20251210/202512100411.WxJU2No9-lkp@intel.com/config)
> reproduce: (https://download.01.org/0day-ci/archive/20251210/202512100411.WxJU2No9-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/202512100411.WxJU2No9-lkp@intel.com/
> 
> kismet warnings: (new ones prefixed by >>)
> >> kismet: WARNING: unmet direct dependencies detected for AX45MP_L2_CACHE when selected by ARCH_R9A07G043  
>    WARNING: unmet direct dependencies detected for AX45MP_L2_CACHE
>      Depends on [n]: CACHEMAINT_FOR_DMA [=n]
>      Selected by [y]:
>      - ARCH_R9A07G043 [=y] && SOC_RENESAS [=y] && RISCV [=y] && NONPORTABLE [=y] && !DMA_DIRECT_REMAP [=n] && RISCV_ALTERNATIVE [=y] && !RISCV_ISA_ZICBOM [=n] && RISCV_SBI [=y]
> 

Thanks for the report!

I think we need a select CACHEMAINT_FOR_DMA in 
config ARCH_R9A07G043

By exposing an explicit option to enable these drivers so we could hang the riscv
dependency off it I broke this particular combination.
It won't break simple builds with old .config due to the default=y but it
still possible to unset CONFIG CACHEMAINT_FOR_DMA

Sorry, I'd missed these were selected though thinking about it that is kind
of obvious given they are needed for correct functionality of those CPUs
if any non coherent DMA devices are present.

Similar applies to CONFIG_ERRATA_STARFIVE_JH7100

I'll spin a patch but I'm not setup to test these properly and that will take
a little more time.

Jonathan

  reply	other threads:[~2025-12-10 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10  3:42 kismet: WARNING: unmet direct dependencies detected for AX45MP_L2_CACHE when selected by ARCH_R9A07G043 kernel test robot
2025-12-10 14:45 ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-11 22:21 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=20251210144514.000021ed@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=conor.dooley@microchip.com \
    --cc=fazilyildiran@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paul@pgazz.com \
    /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