From: kernel test robot <lkp@intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>,
quic_ajitpals@quicinc.com, quic_carlv@quicinc.com,
quic_pkanojiy@quicinc.com, stanislaw.gruszka@linux.intel.com,
ogabbay@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] accel/qaic: Add support for periodic timesync
Date: Thu, 12 Oct 2023 14:20:31 +0800 [thread overview]
Message-ID: <202310121429.uVQ0tmmi-lkp@intel.com> (raw)
In-Reply-To: <20231006163210.21319-2-quic_jhugo@quicinc.com>
Hi Jeffrey,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on next-20231011]
[cannot apply to linus/master v6.6-rc5]
[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/Jeffrey-Hugo/accel-qaic-Add-support-for-periodic-timesync/20231007-003324
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20231006163210.21319-2-quic_jhugo%40quicinc.com
patch subject: [PATCH 1/2] accel/qaic: Add support for periodic timesync
reproduce: (https://download.01.org/0day-ci/archive/20231012/202310121429.uVQ0tmmi-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/202310121429.uVQ0tmmi-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/accel/qaic/aic100.rst:227: WARNING: Unknown target name: "qaic_timesync".
vim +/qaic_timesync +227 Documentation/accel/qaic/aic100.rst
187
188 +----------------+---------+----------+----------------------------------------+
189 | Channel name | IDs | EEs | Purpose |
190 +================+=========+==========+========================================+
191 | QAIC_LOOPBACK | 0 & 1 | AMSS | Any data sent to the device on this |
192 | | | | channel is sent back to the host. |
193 +----------------+---------+----------+----------------------------------------+
194 | QAIC_SAHARA | 2 & 3 | SBL | Used by SBL to obtain the runtime |
195 | | | | firmware from the host. |
196 +----------------+---------+----------+----------------------------------------+
197 | QAIC_DIAG | 4 & 5 | AMSS | Used to communicate with QSM via the |
198 | | | | DIAG protocol. |
199 +----------------+---------+----------+----------------------------------------+
200 | QAIC_SSR | 6 & 7 | AMSS | Used to notify the host of subsystem |
201 | | | | restart events, and to offload SSR |
202 | | | | crashdumps. |
203 +----------------+---------+----------+----------------------------------------+
204 | QAIC_QDSS | 8 & 9 | AMSS | Used for the Qualcomm Debug Subsystem. |
205 +----------------+---------+----------+----------------------------------------+
206 | QAIC_CONTROL | 10 & 11 | AMSS | Used for the Neural Network Control |
207 | | | | (NNC) protocol. This is the primary |
208 | | | | channel between host and QSM for |
209 | | | | managing workloads. |
210 +----------------+---------+----------+----------------------------------------+
211 | QAIC_LOGGING | 12 & 13 | SBL | Used by the SBL to send the bootlog to |
212 | | | | the host. |
213 +----------------+---------+----------+----------------------------------------+
214 | QAIC_STATUS | 14 & 15 | AMSS | Used to notify the host of Reliability,|
215 | | | | Accessibility, Serviceability (RAS) |
216 | | | | events. |
217 +----------------+---------+----------+----------------------------------------+
218 | QAIC_TELEMETRY | 16 & 17 | AMSS | Used to get/set power/thermal/etc |
219 | | | | attributes. |
220 +----------------+---------+----------+----------------------------------------+
221 | QAIC_DEBUG | 18 & 19 | AMSS | Not used. |
222 +----------------+---------+----------+----------------------------------------+
223 | QAIC_TIMESYNC | 20 & 21 | SBL/AMSS | Used to synchronize timestamps in the |
224 | | | | device side logs with the host time |
225 | | | | source. |
226 +----------------+---------+----------+----------------------------------------+
> 227 | QAIC_TIMESYNC_ | 22 & 23 | AMSS | Used to periodically synchronize |
228 | PERIODIC | | | timestamps in the device side logs with|
229 | | | | the host time source. |
230 +----------------+---------+----------+----------------------------------------+
231
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-12 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 16:32 [PATCH 0/2] accel/qaic: Add support for host/device timesync Jeffrey Hugo
2023-10-06 16:32 ` [PATCH 1/2] accel/qaic: Add support for periodic timesync Jeffrey Hugo
2023-10-10 13:08 ` kernel test robot
2023-10-12 6:20 ` kernel test robot [this message]
2023-10-06 16:32 ` [PATCH 2/2] accel/qaic: Support MHI QAIC_TIMESYNC channel Jeffrey Hugo
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=202310121429.uVQ0tmmi-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ogabbay@kernel.org \
--cc=quic_ajitpals@quicinc.com \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_pkanojiy@quicinc.com \
--cc=stanislaw.gruszka@linux.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