All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hari Nagalla <hnagalla@ti.com>
Cc: oe-kbuild-all@lists.linux.dev, vigneshr@ti.com, nm@ti.com,
	Udit Kumar <u-kumar1@ti.com>
Subject: [ti:ti-linux-6.1.y-wip 5/22] drivers/remoteproc/ti_k3_dsp_remoteproc.c:40: warning: Function parameter or member 'core' not described in 'is_core_in_wfi'
Date: Sun, 18 Feb 2024 09:43:49 +0800	[thread overview]
Message-ID: <202402180929.RTjyopeO-lkp@intel.com> (raw)

tree:   git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-linux-6.1.y-wip
head:   77aa27cbdca359bf0735b36ada464ec65b520943
commit: a2313a78eb2ed03046aae3ac604a49c0556ac839 [5/22] remoteproc: k3-dsp: Introduce PM suspend/resume handlers
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20240218/202402180929.RTjyopeO-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240218/202402180929.RTjyopeO-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/202402180929.RTjyopeO-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/remoteproc/ti_k3_dsp_remoteproc.c:40: warning: Function parameter or member 'core' not described in 'is_core_in_wfi'
>> drivers/remoteproc/ti_k3_dsp_remoteproc.c:40: warning: Excess function parameter 'kproc' description in 'is_core_in_wfi'


vim +40 drivers/remoteproc/ti_k3_dsp_remoteproc.c

    31	
    32	/**
    33	 * is_core_in_wfi - local utility function to check core status
    34	 * @kproc: remote core pointer used for checking core status
    35	 *
    36	 * This utility function is invoked by the shutdown sequence to ensure
    37	 * the remote core is in wfi, before asserting a reset.
    38	 */
    39	static int is_core_in_wfi(struct k3_rproc *core)
  > 40	{
    41		int ret;
    42		u64 boot_vec;
    43		u32 cfg, ctrl, stat;
    44	
    45		ret = ti_sci_proc_get_status(core->tsp, &boot_vec, &cfg, &ctrl, &stat);
    46	
    47		if (ret < 0)
    48			return 0;
    49	
    50		return (stat & PROC_BOOT_STATUS_FLAG_CPU_WFI);
    51	}
    52	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2024-02-18  1:44 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=202402180929.RTjyopeO-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hnagalla@ti.com \
    --cc=nm@ti.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.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 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.