From: kernel test robot <lkp@intel.com>
To: Katta Dhanunjanrao <katta.dhanunjanrao@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, git@amd.com,
Michal Simek <monstr@monstr.eu>
Subject: [xilinx-xlnx:xlnx_rebase_v6.1_LTS 1216/1363] drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c:812: warning: Function parameter or member 'bx' not described in 'xhdcp1x_cipher_setb'
Date: Wed, 20 Sep 2023 02:29:12 +0800 [thread overview]
Message-ID: <202309200212.AZDbCXZz-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx xlnx_rebase_v6.1_LTS
head: 4f412ed20fd2c5353c1e878ef9ed77952a5040a1
commit: e6f04926dcd85fb353928a9c899a54e023bf4e69 [1216/1363] staging: xlnx_hdcp1x: Add HDCP1x cipher common functionality
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230920/202309200212.AZDbCXZz-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230920/202309200212.AZDbCXZz-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/202309200212.AZDbCXZz-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c:812: warning: Function parameter or member 'bx' not described in 'xhdcp1x_cipher_setb'
>> drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c:812: warning: Function parameter or member 'by' not described in 'xhdcp1x_cipher_setb'
>> drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c:812: warning: Function parameter or member 'bz' not described in 'xhdcp1x_cipher_setb'
>> drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c:812: warning: Excess function parameter 'x' description in 'xhdcp1x_cipher_setb'
>> drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c:812: warning: Excess function parameter 'y' description in 'xhdcp1x_cipher_setb'
>> drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c:812: warning: Excess function parameter 'z' description in 'xhdcp1x_cipher_setb'
vim +812 drivers/staging/xlnx_hdcp1x/xilinx-hdcp1x-cipher.c
799
800 /**
801 * xhdcp1x_cipher_setb - This function writes the contents of the B register in BM0.
802 * @ref: reference to cipher instance
803 * @x: is the value to be written to bx.
804 * @y: is the value to be written to by.
805 * @z: is the value to be written to bz.
806 *
807 * @return:
808 * - SUCCESS if successful.
809 * - NON_ZERO otherwise.
810 */
811 int xhdcp1x_cipher_setb(void *ref, u32 bx, u32 by, u32 bz)
> 812 {
813 struct xhdcp1x_cipher *cipher = (struct xhdcp1x_cipher *)ref;
814 u32 value = 0;
815
816 if (!(xhdcp1x_cipher_is_enabled(cipher)))
817 return -EINVAL;
818
819 /* Clear the register update bit */
820 value = xhdcp1x_cipher_read(cipher, XHDCP1X_CIPHER_REG_CONTROL);
821 value &= ~XHDCP1X_CIPHER_BITMASK_CONTROL_UPDATE;
822 xhdcp1x_cipher_write(cipher, XHDCP1X_CIPHER_REG_CONTROL, value);
823
824 /* Update the Bx */
825 value = (bx & XHDCP1X_CIPHER_SET_B);
826 xhdcp1x_cipher_write(cipher, XHDCP1X_CIPHER_REG_CIPHER_BX, value);
827
828 /* Update the By */
829 value = (by & XHDCP1X_CIPHER_SET_B);
830 xhdcp1x_cipher_write(cipher, XHDCP1X_CIPHER_REG_CIPHER_BY, value);
831
832 /* Update the Bz */
833 value = (bz & XHDCP1X_CIPHER_SET_B);
834 xhdcp1x_cipher_write(cipher, XHDCP1X_CIPHER_REG_CIPHER_BZ, value);
835
836 /* Set the register update bit */
837 value = xhdcp1x_cipher_read(cipher, XHDCP1X_CIPHER_REG_CONTROL);
838 value |= XHDCP1X_CIPHER_BITMASK_CONTROL_UPDATE;
839 xhdcp1x_cipher_write(cipher, XHDCP1X_CIPHER_REG_CONTROL, value);
840
841 return 0;
842 }
843 EXPORT_SYMBOL_GPL(xhdcp1x_cipher_setb);
844
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-19 18:30 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=202309200212.AZDbCXZz-lkp@intel.com \
--to=lkp@intel.com \
--cc=git@amd.com \
--cc=katta.dhanunjanrao@amd.com \
--cc=monstr@monstr.eu \
--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 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.