Re: [PATCH v4 1/6] dt-bindings: ufs: common: add OPP table

[kernel test robot <lkp@intel.com>]

Hi Manivannan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on jejb-scsi/for-next linus/master v6.6-rc4 next-20231003]
[cannot apply to robh/for-next]
[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/Manivannan-Sadhasivam/dt-bindings-ufs-common-add-OPP-table/20231003-191704
base:   https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
patch link:    https://lore.kernel.org/r/20231003111232.42663-2-manivannan.sadhasivam%40linaro.org
patch subject: [PATCH v4 1/6] dt-bindings: ufs: common: add OPP table
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231004/202310040539.MPXMfcgx-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/202310040539.MPXMfcgx-lkp@intel.com/

dtcheck warnings: (new ones prefixed by >>)
>> Documentation/devicetree/bindings/ufs/ufs-common.yaml:90:20: [error] string value is redundantly quoted with any quotes (quoted-strings)
   Documentation/devicetree/bindings/ufs/ufs-common.yaml:91:26: [error] string value is redundantly quoted with any quotes (quoted-strings)
   Documentation/devicetree/bindings/ufs/ufs-common.yaml:91:36: [error] string value is redundantly quoted with any quotes (quoted-strings)

vim +90 Documentation/devicetree/bindings/ufs/ufs-common.yaml

     8	
     9	maintainers:
    10	  - Alim Akhtar <alim.akhtar@samsung.com>
    11	  - Avri Altman <avri.altman@wdc.com>
    12	
    13	properties:
    14	  clocks: true
    15	
    16	  clock-names: true
    17	
    18	  freq-table-hz:
    19	    items:
    20	      items:
    21	        - description: Minimum frequency for given clock in Hz
    22	        - description: Maximum frequency for given clock in Hz
    23	    deprecated: true
    24	    description: |
    25	      Preferred is operating-points-v2.
    26	
    27	      Array of <min max> operating frequencies in Hz stored in the same order
    28	      as the clocks property. If either this property or operating-points-v2 is
    29	      not defined or a value in the array is "0" then it is assumed that the
    30	      frequency is set by the parent clock or a fixed rate clock source.
    31	
    32	  operating-points-v2:
    33	    description:
    34	      Preferred over freq-table-hz.
    35	      If present, each OPP must contain array of frequencies stored in the same
    36	      order for each clock.  If clock frequency in the array is "0" then it is
    37	      assumed that the frequency is set by the parent clock or a fixed rate
    38	      clock source.
    39	
    40	  opp-table: true
    41	
    42	  interrupts:
    43	    maxItems: 1
    44	
    45	  lanes-per-direction:
    46	    $ref: /schemas/types.yaml#/definitions/uint32
    47	    enum: [1, 2]
    48	    default: 2
    49	    description:
    50	      Number of lanes available per direction.  Note that it is assume same
    51	      number of lanes is used both directions at once.
    52	
    53	  vdd-hba-supply:
    54	    description:
    55	      Phandle to UFS host controller supply regulator node.
    56	
    57	  vcc-supply:
    58	    description:
    59	      Phandle to VCC supply regulator node.
    60	
    61	  vccq-supply:
    62	    description:
    63	      Phandle to VCCQ supply regulator node.
    64	
    65	  vccq2-supply:
    66	    description:
    67	      Phandle to VCCQ2 supply regulator node.
    68	
    69	  vcc-supply-1p8:
    70	    type: boolean
    71	    description:
    72	      For embedded UFS devices, valid VCC range is 1.7-1.95V or 2.7-3.6V. This
    73	      boolean property when set, specifies to use low voltage range of
    74	      1.7-1.95V. Note for external UFS cards this property is invalid and valid
    75	      VCC range is always 2.7-3.6V.
    76	
    77	  vcc-max-microamp:
    78	    description:
    79	      Specifies max. load that can be drawn from VCC supply.
    80	
    81	  vccq-max-microamp:
    82	    description:
    83	      Specifies max. load that can be drawn from VCCQ supply.
    84	
    85	  vccq2-max-microamp:
    86	    description:
    87	      Specifies max. load that can be drawn from VCCQ2 supply.
    88	
    89	dependencies:
  > 90	  freq-table-hz: [ 'clocks' ]
    91	  operating-points-v2: [ 'clocks', 'clock-names' ]
    92	
    93	required:
    94	  - interrupts
    95	
    96	allOf:
    97	  - if:
    98	      required:
    99	        - freq-table-hz
   100	    then:
   101	      properties:
   102	        operating-points-v2: false
   103	  - if:
   104	      required:
   105	        - operating-points-v2
   106	    then:
   107	      properties:
   108	        freq-table-hz: false
   109	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki