From: Philip Li <philip.li@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: drivers/memory/emif.c:70: warning: Function parameter or struct member 'lpmode' not described in 'emif_data'
Date: Sat, 28 Dec 2024 18:54:57 +0800 [thread overview]
Message-ID: <Z2/ZAVLdUD4hyryn@rli9-mobl> (raw)
In-Reply-To: <202412281715.ZOR40f8d-lkp@intel.com>
On Sat, Dec 28, 2024 at 05:55:47PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: fd0584d220fe285dc45be43eede55df89ad6a3d9
> commit: ea0c0ad6b6eb36726088991d97a55b99cae456d0 memory: Enable compile testing for most of the drivers
> date: 4 years, 4 months ago
> config: sparc-randconfig-001-20241212 (https://download.01.org/0day-ci/archive/20241228/202412281715.ZOR40f8d-lkp@intel.com/config)
> compiler: sparc-linux-gcc (GCC) 12.4.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241228/202412281715.ZOR40f8d-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/202412281715.ZOR40f8d-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
Sorry, please ignore this report, it is not the actual cause.
>
> >> drivers/memory/emif.c:70: warning: Function parameter or struct member 'lpmode' not described in 'emif_data'
> drivers/memory/emif.c:70: warning: Function parameter or struct member 'irq_state' not described in 'emif_data'
> drivers/memory/emif.c:70: warning: Function parameter or struct member 'addressing' not described in 'emif_data'
>
>
> vim +70 drivers/memory/emif.c
>
> 7ec944538dde3d Aneesh V 2012-04-27 30
> 7ec944538dde3d Aneesh V 2012-04-27 31 /**
> 7ec944538dde3d Aneesh V 2012-04-27 32 * struct emif_data - Per device static data for driver's use
> 7ec944538dde3d Aneesh V 2012-04-27 33 * @duplicate: Whether the DDR devices attached to this EMIF
> 7ec944538dde3d Aneesh V 2012-04-27 34 * instance are exactly same as that on EMIF1. In
> 7ec944538dde3d Aneesh V 2012-04-27 35 * this case we can save some memory and processing
> 7ec944538dde3d Aneesh V 2012-04-27 36 * @temperature_level: Maximum temperature of LPDDR2 devices attached
> 7ec944538dde3d Aneesh V 2012-04-27 37 * to this EMIF - read from MR4 register. If there
> 7ec944538dde3d Aneesh V 2012-04-27 38 * are two devices attached to this EMIF, this
> 7ec944538dde3d Aneesh V 2012-04-27 39 * value is the maximum of the two temperature
> 7ec944538dde3d Aneesh V 2012-04-27 40 * levels.
> 7ec944538dde3d Aneesh V 2012-04-27 41 * @node: node in the device list
> 7ec944538dde3d Aneesh V 2012-04-27 42 * @base: base address of memory-mapped IO registers.
> 7ec944538dde3d Aneesh V 2012-04-27 43 * @dev: device pointer.
> a93de288aad3b0 Aneesh V 2012-04-27 44 * @addressing table with addressing information from the spec
> a93de288aad3b0 Aneesh V 2012-04-27 45 * @regs_cache: An array of 'struct emif_regs' that stores
> a93de288aad3b0 Aneesh V 2012-04-27 46 * calculated register values for different
> a93de288aad3b0 Aneesh V 2012-04-27 47 * frequencies, to avoid re-calculating them on
> a93de288aad3b0 Aneesh V 2012-04-27 48 * each DVFS transition.
> a93de288aad3b0 Aneesh V 2012-04-27 49 * @curr_regs: The set of register values used in the last
> a93de288aad3b0 Aneesh V 2012-04-27 50 * frequency change (i.e. corresponding to the
> a93de288aad3b0 Aneesh V 2012-04-27 51 * frequency in effect at the moment)
> 7ec944538dde3d Aneesh V 2012-04-27 52 * @plat_data: Pointer to saved platform data.
> aac10aaa8cc65a Aneesh V 2012-04-27 53 * @debugfs_root: dentry to the root folder for EMIF in debugfs
> e6b42eb6a66c18 Aneesh V 2012-08-17 54 * @np_ddr: Pointer to ddr device tree node
> 7ec944538dde3d Aneesh V 2012-04-27 55 */
> 7ec944538dde3d Aneesh V 2012-04-27 56 struct emif_data {
> 7ec944538dde3d Aneesh V 2012-04-27 57 u8 duplicate;
> 7ec944538dde3d Aneesh V 2012-04-27 58 u8 temperature_level;
> a93de288aad3b0 Aneesh V 2012-04-27 59 u8 lpmode;
> 7ec944538dde3d Aneesh V 2012-04-27 60 struct list_head node;
> a93de288aad3b0 Aneesh V 2012-04-27 61 unsigned long irq_state;
> 7ec944538dde3d Aneesh V 2012-04-27 62 void __iomem *base;
> 7ec944538dde3d Aneesh V 2012-04-27 63 struct device *dev;
> a93de288aad3b0 Aneesh V 2012-04-27 64 const struct lpddr2_addressing *addressing;
> a93de288aad3b0 Aneesh V 2012-04-27 65 struct emif_regs *regs_cache[EMIF_MAX_NUM_FREQUENCIES];
> a93de288aad3b0 Aneesh V 2012-04-27 66 struct emif_regs *curr_regs;
> 7ec944538dde3d Aneesh V 2012-04-27 67 struct emif_platform_data *plat_data;
> aac10aaa8cc65a Aneesh V 2012-04-27 68 struct dentry *debugfs_root;
> e6b42eb6a66c18 Aneesh V 2012-08-17 69 struct device_node *np_ddr;
> 7ec944538dde3d Aneesh V 2012-04-27 @70 };
> 7ec944538dde3d Aneesh V 2012-04-27 71
>
> :::::: The code at line 70 was first introduced by commit
> :::::: 7ec944538dde3d7f490bd4d2619051789db5c3c3 memory: emif: add basic infrastructure for EMIF driver
>
> :::::: TO: Aneesh V <aneesh@ti.com>
> :::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
next prev parent reply other threads:[~2024-12-28 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 9:55 kernel test robot
2024-12-28 10:54 ` Philip Li [this message]
2025-01-02 17:28 kernel test robot
2025-04-18 8:12 kernel test robot
2025-04-29 22:50 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=Z2/ZAVLdUD4hyryn@rli9-mobl \
--to=philip.li@intel.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®