From: kernel test robot <lkp@intel.com>
To: Kiran K <kiran.k@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-bluetooth@vger.kernel.org,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Vijay Satija <vijay.satija@intel.com>
Subject: [bluetooth-next:master 28/29] drivers/bluetooth/btintel_pcie.c:134:58: warning: shift count >= width of type
Date: Thu, 27 Feb 2025 15:11:45 +0800 [thread overview]
Message-ID: <202502271502.37Q8TE9Q-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
head: 978777bfa2d88998f2ffa2d3405ee20b7276890a
commit: 3104ae5ad1b732140847f1f29534a448b6804d8e [28/29] Bluetooth: btintel_pcie: Setup buffers for firmware traces
config: powerpc-randconfig-001-20250227 (https://download.01.org/0day-ci/archive/20250227/202502271502.37Q8TE9Q-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502271502.37Q8TE9Q-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/202502271502.37Q8TE9Q-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/bluetooth/btintel_pcie.c:134:58: warning: shift count >= width of type [-Wshift-count-overflow]
134 | db_frag.bufs[i].buf_addr_msb = (u32)((buf->data_p_addr >> 32) & 0xffffffff);
| ^ ~~
drivers/bluetooth/btintel_pcie.c:419:20: warning: unused function 'btintel_pcie_in_rom' [-Wunused-function]
419 | static inline bool btintel_pcie_in_rom(struct btintel_pcie_data *data)
| ^~~~~~~~~~~~~~~~~~~
2 warnings generated.
vim +134 drivers/bluetooth/btintel_pcie.c
90
91 /* This function initializes the memory for DBGC buffers and formats the
92 * DBGC fragment which consists header info and DBGC buffer's LSB, MSB and
93 * size as the payload
94 */
95 static int btintel_pcie_setup_dbgc(struct btintel_pcie_data *data)
96 {
97 struct btintel_pcie_dbgc_ctxt db_frag;
98 struct data_buf *buf;
99 int i;
100
101 data->dbgc.count = BTINTEL_PCIE_DBGC_BUFFER_COUNT;
102 data->dbgc.bufs = devm_kcalloc(&data->pdev->dev, data->dbgc.count,
103 sizeof(*buf), GFP_KERNEL);
104 if (!data->dbgc.bufs)
105 return -ENOMEM;
106
107 data->dbgc.buf_v_addr = dmam_alloc_coherent(&data->pdev->dev,
108 data->dbgc.count *
109 BTINTEL_PCIE_DBGC_BUFFER_SIZE,
110 &data->dbgc.buf_p_addr,
111 GFP_KERNEL | __GFP_NOWARN);
112 if (!data->dbgc.buf_v_addr)
113 return -ENOMEM;
114
115 data->dbgc.frag_v_addr = dmam_alloc_coherent(&data->pdev->dev,
116 sizeof(struct btintel_pcie_dbgc_ctxt),
117 &data->dbgc.frag_p_addr,
118 GFP_KERNEL | __GFP_NOWARN);
119 if (!data->dbgc.frag_v_addr)
120 return -ENOMEM;
121
122 data->dbgc.frag_size = sizeof(struct btintel_pcie_dbgc_ctxt);
123
124 db_frag.magic_num = BTINTEL_PCIE_MAGIC_NUM;
125 db_frag.ver = BTINTEL_PCIE_DBGC_FRAG_VERSION;
126 db_frag.total_size = BTINTEL_PCIE_DBGC_FRAG_PAYLOAD_SIZE;
127 db_frag.num_buf = BTINTEL_PCIE_DBGC_FRAG_BUFFER_COUNT;
128
129 for (i = 0; i < data->dbgc.count; i++) {
130 buf = &data->dbgc.bufs[i];
131 buf->data_p_addr = data->dbgc.buf_p_addr + i * BTINTEL_PCIE_DBGC_BUFFER_SIZE;
132 buf->data = data->dbgc.buf_v_addr + i * BTINTEL_PCIE_DBGC_BUFFER_SIZE;
133 db_frag.bufs[i].buf_addr_lsb = (u32)(buf->data_p_addr & 0xffffffff);
> 134 db_frag.bufs[i].buf_addr_msb = (u32)((buf->data_p_addr >> 32) & 0xffffffff);
135 db_frag.bufs[i].buf_size = BTINTEL_PCIE_DBGC_BUFFER_SIZE;
136 }
137
138 memcpy(data->dbgc.frag_v_addr, &db_frag, sizeof(db_frag));
139 return 0;
140 }
141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-27 7:12 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=202502271502.37Q8TE9Q-lkp@intel.com \
--to=lkp@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luiz.von.dentz@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vijay.satija@intel.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