DMA Engine development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Frank Li <Frank.li@nxp.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	dmaengine@vger.kernel.org, imx@lists.linux.dev,
	krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
	peng.fan@nxp.com, robh@kernel.org, vkoul@kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: dma: fsl-edma: remove 'clocks' from required
Date: Wed, 10 Apr 2024 08:32:28 +0200	[thread overview]
Message-ID: <383141cd-7f6f-4ed0-945b-7761833ecc35@linaro.org> (raw)
In-Reply-To: <680f8830-6cd8-433b-85b7-439070bc528f@linaro.org>

On 10/04/2024 08:30, Krzysztof Kozlowski wrote:
> On 09/04/2024 23:09, Frank Li wrote:
>> On Tue, Apr 09, 2024 at 10:02:32PM +0200, Krzysztof Kozlowski wrote:
>>> On 09/04/2024 20:54, Frank Li wrote:
>>>> fsl,imx8qm-adma and fsl,imx8qm-edma don't require 'clocks'. Remove it from
>>>> required and add 'if' block for other compatible string to keep the same
>>>> restrictions.
>>>>
>>>> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> Signed-off-by: Frank Li <Frank.Li@nxp.com>
>>>> ---
>>>>
>>>> Notes:
>>>>     Change from v2 to v3
>>>>       - rebase to dmaengine/next
>>>
>>> This fails...
>>
>> What's wrong? 
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git/log/?h=next
>>
>>>
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/dma/fsl,edma.yaml b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
>>>> index 825f4715499e5..657a7d3ebf857 100644
>>>> --- a/Documentation/devicetree/bindings/dma/fsl,edma.yaml
>>>> +++ b/Documentation/devicetree/bindings/dma/fsl,edma.yaml
>>>> @@ -82,7 +82,6 @@ required:
>>>>    - compatible
>>>>    - reg
>>>>    - interrupts
>>>> -  - clocks
>>>>    - dma-channels
>>>>  
>>>>  allOf:
>>>> @@ -187,6 +186,22 @@ allOf:
>>>>          "#dma-cells":
>>>>            const: 3
>>>>  
>>>> +  - if:
>>>> +      properties:
>>>> +        compatible:
>>>> +	  contains:
>>>
>>> It does not look like you tested the bindings, at least after quick
>>> look. Please run `make dt_binding_check` (see
>>> Documentation/devicetree/bindings/writing-schema.rst for instructions).
>>> Maybe you need to update your dtschema and yamllint.
>>
>> Strange, Test passed
>>
>> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j8  dt_binding_check DT_SCHEMA_FILES=fsl,edma.yaml
>>   LINT    Documentation/devicetree/bindings
>>   DTEX    Documentation/devicetree/bindings/dma/fsl,edma.example.dts
>>   CHKDT   Documentation/devicetree/bindings/processed-schema.json
>>   SCHEMA  Documentation/devicetree/bindings/processed-schema.json
>>   DTC_CHK Documentation/devicetree/bindings/dma/fsl,edma.example.dtb
> 
> Nope, you tested other patch. Just look at your second patch for this.
> When reviewer points to errors to your code, please investigate?
> 
> NAK, fix your patches.

And to prove it, so you will stop wasting my time:
../Documentation/devicetree/bindings/dma/fsl,edma.yaml:192:1: found
character that cannot start any token

../Documentation/devicetree/bindings/dma/fsl,edma.yaml:192:1: [error]
syntax error: found character '\t' that cannot start any token (syntax)

../Documentation/devicetree/bindings/dma/fsl,edma.yaml:192:1: found
character that cannot start any token

Documentation/devicetree/bindings/dma/fsl,edma.yaml: ignoring, error
parsing file


Best regards,
Krzysztof


  reply	other threads:[~2024-04-10  6:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 18:54 [PATCH v3 1/2] dt-bindings: dma: fsl-edma: remove 'clocks' from required Frank Li
2024-04-09 18:54 ` [PATCH v3 2/2] dt-bindings: dma: fsl-edma: allow 'power-domains' property Frank Li
2024-04-09 20:02 ` [PATCH v3 1/2] dt-bindings: dma: fsl-edma: remove 'clocks' from required Krzysztof Kozlowski
2024-04-09 21:09   ` Frank Li
2024-04-10  6:30     ` Krzysztof Kozlowski
2024-04-10  6:32       ` Krzysztof Kozlowski [this message]
2024-04-10  6:47         ` Krzysztof Kozlowski
2024-04-10 16:24           ` Frank Li

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=383141cd-7f6f-4ed0-945b-7761833ecc35@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=vkoul@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