From: kernel test robot <lkp@intel.com>
To: Jyan Chou <jyanchou@realtek.com>,
adrian.hunter@intel.com, ulf.hansson@linaro.org,
jh80.chung@samsung.com
Cc: oe-kbuild-all@lists.linux.dev, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, benchuanggli@gmail.com,
jyanchou@realtek.com
Subject: Re: [PATCH V2][4/4] mmc: Add dt-bindings for realtek mmc driver
Date: Sat, 21 Oct 2023 19:46:43 +0800 [thread overview]
Message-ID: <202310211903.42KO5zwa-lkp@intel.com> (raw)
In-Reply-To: <20231018055326.18256-5-jyanchou@realtek.com>
Hi Jyan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on ulf-hansson-mmc-mirror/next linus/master v6.6-rc6 next-20231020]
[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/Jyan-Chou/mmc-Add-dt-bindings-for-realtek-mmc-driver/20231018-135538
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20231018055326.18256-5-jyanchou%40realtek.com
patch subject: [PATCH V2][4/4] mmc: Add dt-bindings for realtek mmc driver
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231021/202310211903.42KO5zwa-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/202310211903.42KO5zwa-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml:46:7: [error] string value is redundantly quoted with any quotes (quoted-strings)
>> Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml:46:13: [error] syntax error: expected <block end>, but found '<scalar>' (syntax)
--
>> Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml:46:13: did not find expected key
--
>> Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml: ignoring, error parsing file
vim +46 Documentation/devicetree/bindings/mmc/realtek-dw-mshc.yaml
8
9 description:
10 Realtek uses the Synopsys designware mobile storage host controller
11 to interface a SoC with storage medium. This file documents the Realtek
12 specific extensions.
13
14 allOf:
15 - $ref: synopsys-dw-mshc-common.yaml#
16
17 maintainers:
18 - Jyan Chou <jyanchou@realtek.com>
19
20 # Everything else is described in the common file
21 properties:
22 compatible:
23 enum:
24 - realtek,rtd-dw-cqe-emmc
25 reg:
26 maxItems: 1
27
28 interrupts:
29 maxItems: 1
30
31 clocks:
32 minItems: 2
33 maxItems: 4
34 description:
35 Handle to "biu" and "ciu" clocks for the bus interface unit clock and
36 the card interface unit clock.
37
38 clock-names:
39 minItems: 2
40 items:
41 - const: biu
42 - const: ciu
43 - const: vp0
44 - const: vp1
45 description:
> 46 "vp0" and "vp1" are used to control the clock phases.
47
48 power-domains:
49 maxItems: 1
50
51 resets:
52 maxItems: 1
53
54 reset-names:
55 const: reset
56
57 speed-step:
58 maxItems: 1
59 description:
60 "speed-step" represents the bus speed mode of emmc. "3" means HS400,
61 "2" means HS200, "0" means HS.
62
63 pinctrl-names:
64 maxItems: 10
65 items:
66 - const: default
67 - const: sdr50
68 - const: ddr50
69 - const: hs200
70 - const: hs400
71 - const: tune0
72 - const: tune1
73 - const: tune2
74 - const: tune3
75 - const: tune4
76
77 required:
78 - compatible
79 - reg
80 - interrupts
81 - clocks
82 - clock-names
83 - pinctrl-names
84 - pinctrl
85
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-10-21 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 5:53 [PATCH V2][0/4] Add DesignWare Mobile mmc driver Jyan Chou
2023-10-18 5:53 ` [PATCH V2][1/4] mmc: solve DMA boundary limitation of CQHCI driver Jyan Chou
2023-10-19 9:00 ` kernel test robot
2023-10-19 13:00 ` kernel test robot
2023-10-18 5:53 ` [PATCH V2][2/4] mmc: Add Synopsys DesignWare mmc cmdq host driver Jyan Chou
2023-10-18 5:53 ` [PATCH V2][3/4] mmc: Add dw mobile mmc cmdq rtk driver Jyan Chou
2023-10-18 5:53 ` [PATCH V2][4/4] mmc: Add dt-bindings for realtek mmc driver Jyan Chou
2023-10-18 14:24 ` Krzysztof Kozlowski
2023-10-20 5:18 ` Jyan Chou [周芷安]
2023-10-21 11:46 ` 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=202310211903.42KO5zwa-lkp@intel.com \
--to=lkp@intel.com \
--cc=adrian.hunter@intel.com \
--cc=benchuanggli@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=jyanchou@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ulf.hansson@linaro.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