From: kernel test robot <lkp@intel.com>
To: Junhui Liu <junhui.liu@pigmoral.tech>,
Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Inochi Amaoto <inochiama@gmail.com>,
Yuntao Dai <d1581209858@live.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, sophgo@lists.linux.dev,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v3 3/3] mailbox: sophgo: add mailbox driver for CV18XX series SoC
Date: Wed, 7 May 2025 14:06:20 +0800 [thread overview]
Message-ID: <202505071325.uHimwt0g-lkp@intel.com> (raw)
In-Reply-To: <20250428-cv18xx-mbox-v3-3-ed18dfd836d1@pigmoral.tech>
Hi Junhui,
kernel test robot noticed the following build warnings:
[auto build test WARNING on b4432656b36e5cc1d50a1f2dc15357543add530e]
url: https://github.com/intel-lab-lkp/linux/commits/Junhui-Liu/dt-bindings-mailbox-add-Sophgo-CV18XX-series-SoC/20250428-221604
base: b4432656b36e5cc1d50a1f2dc15357543add530e
patch link: https://lore.kernel.org/r/20250428-cv18xx-mbox-v3-3-ed18dfd836d1%40pigmoral.tech
patch subject: [PATCH v3 3/3] mailbox: sophgo: add mailbox driver for CV18XX series SoC
config: m68k-randconfig-r121-20250429 (https://download.01.org/0day-ci/archive/20250507/202505071325.uHimwt0g-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 7.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250507/202505071325.uHimwt0g-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/202505071325.uHimwt0g-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/mailbox/cv1800-mailbox.c:64:50: sparse: sparse: cast removes address space '__iomem' of expression
drivers/mailbox/cv1800-mailbox.c:89:33: sparse: sparse: cast removes address space '__iomem' of expression
>> drivers/mailbox/cv1800-mailbox.c:88:42: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected unsigned long long [noderef] [usertype] __iomem * @@ got unsigned long long [usertype] * @@
drivers/mailbox/cv1800-mailbox.c:88:42: sparse: expected unsigned long long [noderef] [usertype] __iomem *
drivers/mailbox/cv1800-mailbox.c:88:42: sparse: got unsigned long long [usertype] *
drivers/mailbox/cv1800-mailbox.c:109:21: sparse: sparse: cast removes address space '__iomem' of expression
>> drivers/mailbox/cv1800-mailbox.c:109:21: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *dst @@ got unsigned long long [usertype] * @@
drivers/mailbox/cv1800-mailbox.c:109:21: sparse: expected void volatile [noderef] __iomem *dst
drivers/mailbox/cv1800-mailbox.c:109:21: sparse: got unsigned long long [usertype] *
vim +/__iomem +64 drivers/mailbox/cv1800-mailbox.c
54
55 static irqreturn_t cv1800_mbox_isr(int irq, void *dev_id)
56 {
57 struct cv1800_mbox *mbox = (struct cv1800_mbox *)dev_id;
58 size_t i;
59 int ret = IRQ_NONE;
60
61 for (i = 0; i < MAILBOX_MAX_CHAN; i++) {
62 if (mbox->content[i] && mbox->chans[i].cl) {
63 mbox_chan_received_data(&mbox->chans[i],
> 64 (void *)mbox->content[i]);
65 mbox->content[i] = NULL;
66 ret = IRQ_HANDLED;
67 }
68 }
69
70 return ret;
71 }
72
73 static irqreturn_t cv1800_mbox_irq(int irq, void *dev_id)
74 {
75 struct cv1800_mbox *mbox = (struct cv1800_mbox *)dev_id;
76 u8 set, valid;
77 size_t i;
78 int ret = IRQ_NONE;
79
80 set = readb(mbox->mbox_base + MBOX_SET_INT_REG(RECV_CPU));
81
82 if (!set)
83 return ret;
84
85 for (i = 0; i < MAILBOX_MAX_CHAN; i++) {
86 valid = set & BIT(i);
87 if (valid) {
> 88 mbox->content[i] =
89 MBOX_CONTEXT_BASE_INDEX(mbox->mbox_base, i);
90 writeb(valid,
91 mbox->mbox_base + MBOX_SET_CLR_REG(RECV_CPU));
92 writeb(~valid, mbox->mbox_base + MBOX_EN_REG(RECV_CPU));
93 ret = IRQ_WAKE_THREAD;
94 }
95 }
96
97 return ret;
98 }
99
100 static int cv1800_mbox_send_data(struct mbox_chan *chan, void *data)
101 {
102 struct cv1800_mbox_chan_priv *priv =
103 (struct cv1800_mbox_chan_priv *)chan->con_priv;
104 struct cv1800_mbox *mbox = dev_get_drvdata(chan->mbox->dev);
105 int idx = priv->idx;
106 int cpu = priv->cpu;
107 u8 en, valid;
108
> 109 memcpy_toio(MBOX_CONTEXT_BASE_INDEX(mbox->mbox_base, idx),
110 data, 8);
111
112 valid = BIT(idx);
113 writeb(valid, mbox->mbox_base + MBOX_SET_CLR_REG(cpu));
114 en = readb(mbox->mbox_base + MBOX_EN_REG(cpu));
115 writeb(en | valid, mbox->mbox_base + MBOX_EN_REG(cpu));
116 writeb(valid, mbox->mbox_base + MBOX_SET_REG);
117
118 return 0;
119 }
120
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-05-07 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 12:39 [PATCH v3 0/3] riscv: sophgo: add mailbox support for CV18XX series SoC Junhui Liu
2025-04-28 12:39 ` [PATCH v3 1/3] dt-bindings: mailbox: add Sophgo " Junhui Liu
2025-04-28 16:52 ` Conor Dooley
2025-04-29 2:05 ` Junhui Liu
2025-04-28 12:39 ` [PATCH v3 2/3] riscv: dts: add mailbox for " Junhui Liu
2025-04-28 16:55 ` Conor Dooley
2025-04-29 2:44 ` Junhui Liu
2025-05-07 12:12 ` Inochi Amaoto
2025-05-07 13:14 ` Junhui Liu
2025-04-28 12:39 ` [PATCH v3 3/3] mailbox: sophgo: add mailbox driver for " Junhui Liu
2025-05-07 6:06 ` 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=202505071325.uHimwt0g-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=d1581209858@live.com \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=junhui.liu@pigmoral.tech \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.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