From: kernel test robot <lkp@intel.com>
To: Bibek Kumar Patro <quic_bibekkum@quicinc.com>,
robdclark@gmail.com, will@kernel.org, robin.murphy@arm.com,
joro@8bytes.org, jgg@ziepe.ca, jsnitsel@redhat.com,
robh@kernel.org, krzysztof.kozlowski@linaro.org,
quic_c_gdjako@quicinc.com, dmitry.baryshkov@linaro.org,
konrad.dybcio@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, iommu@lists.linux.dev,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Bibek Kumar Patro <quic_bibekkum@quicinc.com>
Subject: Re: [PATCH v12 6/6] iommu/arm-smmu: add support for PRR bit setup
Date: Fri, 28 Jun 2024 13:18:18 +0800 [thread overview]
Message-ID: <202406281241.xEX0TWjt-lkp@intel.com> (raw)
In-Reply-To: <20240626143020.3682243-7-quic_bibekkum@quicinc.com>
Hi Bibek,
kernel test robot noticed the following build warnings:
[auto build test WARNING on joro-iommu/next]
[also build test WARNING on linus/master v6.10-rc5 next-20240627]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Bibek-Kumar-Patro/iommu-arm-smmu-re-enable-context-caching-in-smmu-reset-operation/20240627-074037
base: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git next
patch link: https://lore.kernel.org/r/20240626143020.3682243-7-quic_bibekkum%40quicinc.com
patch subject: [PATCH v12 6/6] iommu/arm-smmu: add support for PRR bit setup
config: arm64-randconfig-r113-20240628 (https://download.01.org/0day-ci/archive/20240628/202406281241.xEX0TWjt-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240628/202406281241.xEX0TWjt-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/202406281241.xEX0TWjt-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c:247:54: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void * @@
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c:247:54: sparse: expected void volatile [noderef] __iomem *addr
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c:247:54: sparse: got void *
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c:250:54: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void volatile [noderef] __iomem *addr @@ got void * @@
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c:250:54: sparse: expected void volatile [noderef] __iomem *addr
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c:250:54: sparse: got void *
drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/slab.h, ...):
include/linux/page-flags.h:240:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:240:46: sparse: sparse: self-comparison always evaluates to false
vim +247 drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
238
239 static void qcom_adreno_smmu_set_prr(const void *cookie, phys_addr_t page_addr, bool set)
240 {
241 struct arm_smmu_domain *smmu_domain = (void *)cookie;
242 struct arm_smmu_cfg *cfg = &smmu_domain->cfg;
243 struct arm_smmu_device *smmu = smmu_domain->smmu;
244 u32 reg = 0;
245
246 writel_relaxed(lower_32_bits(page_addr),
> 247 (void *)smmu->ioaddr + ARM_SMMU_GFX_PRR_CFG_LADDR);
248
249 writel_relaxed(upper_32_bits(page_addr),
250 (void *)smmu->ioaddr + ARM_SMMU_GFX_PRR_CFG_UADDR);
251
252 reg = arm_smmu_cb_read(smmu, cfg->cbndx, ARM_SMMU_CB_ACTLR);
253 reg &= ~GFX_ACTLR_PRR;
254 if (set)
255 reg |= FIELD_PREP(GFX_ACTLR_PRR, 1);
256 arm_smmu_cb_write(smmu, cfg->cbndx, ARM_SMMU_CB_ACTLR, reg);
257
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-06-28 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 14:30 [PATCH v12 0/6] iommu/arm-smmu: introduction of ACTLR implementation for Qualcomm SoCs Bibek Kumar Patro
2024-06-26 14:30 ` [PATCH v12 1/6] iommu/arm-smmu: re-enable context caching in smmu reset operation Bibek Kumar Patro
2024-06-26 14:30 ` [PATCH v12 2/6] iommu/arm-smmu: refactor qcom_smmu structure to include single pointer Bibek Kumar Patro
2024-06-26 14:30 ` [PATCH v12 3/6] iommu/arm-smmu: introduction of ACTLR for custom prefetcher settings Bibek Kumar Patro
2024-06-26 14:30 ` [PATCH v12 4/6] iommu/arm-smmu: add ACTLR data and support for SM8550 Bibek Kumar Patro
2024-06-26 14:30 ` [PATCH v12 5/6] iommu/arm-smmu: add ACTLR data and support for SC7280 Bibek Kumar Patro
2024-06-26 14:30 ` [PATCH v12 6/6] iommu/arm-smmu: add support for PRR bit setup Bibek Kumar Patro
2024-06-28 5:18 ` kernel test robot [this message]
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=202406281241.xEX0TWjt-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_bibekkum@quicinc.com \
--cc=quic_c_gdjako@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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