linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Suman Anna <s-anna@ti.com>
To: Rob Herring <robh@kernel.org>
Cc: Santosh Shilimkar <ssantosh@kernel.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	Lokesh Vutla <lokeshvutla@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: soc: ti: pruss: Add dma-coherent property
Date: Tue, 3 Aug 2021 14:32:32 -0500	[thread overview]
Message-ID: <411c54ef-6ae6-2a17-c2c4-fb19580b5513@ti.com> (raw)
In-Reply-To: <YQmY7/OSHJxRkM5m@robh.at.kernel.org>

On 8/3/21 2:28 PM, Rob Herring wrote:
> On Thu, Jul 29, 2021 at 10:19:01PM -0500, Suman Anna wrote:
>> Update the PRUSS schema file to include the dma-coherent property
>> that indicates the coherency of the IP. The PRUSS IPs on 66AK2G
>> SoCs do use this property.
>>
>> Signed-off-by: Suman Anna <s-anna@ti.com>
>> ---
>> Hi Santosh,
>>
>> This patch updates the PRUSS binding in preparation for adding the
>> PRUSS nodes for 66AK2G SoCs. Without this, the dtbs_check would
>> complain about the undefined dma-coherent property. Patch is top
>> of the AM64 ICSSG binding update patch [1].
> 
> New required properties are not backwards compatible. You are kind of 
> saying that here (not used yet?), but make that clear in the commit msg.

OK. Yeah, we haven't added the K2G dts nodes yet, and the new required property
is only applicable for that SoC and not others.

regards
Suman

> 
> With that fixed,
> 
> Reviewed-by: Rob Herring <robh@kernel.org>
> 
>>
>> regards
>> Suman
>>
>> [1] https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210623165032.31223-2-s-anna@ti.com/
>>
>>  .../devicetree/bindings/soc/ti/ti,pruss.yaml  | 37 +++++++++++++------
>>  1 file changed, 25 insertions(+), 12 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>> index 47d7fd24bc56..9d128b9e7deb 100644
>> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
>> @@ -85,6 +85,8 @@ properties:
>>    dma-ranges:
>>      maxItems: 1
>>  
>> +  dma-coherent: true
>> +
>>    power-domains:
>>      description: |
>>        This property is as per sci-pm-domain.txt.
>> @@ -324,18 +326,29 @@ additionalProperties: false
>>  # - interrupt-controller
>>  # - pru
>>  
>> -if:
>> -  properties:
>> -    compatible:
>> -      contains:
>> -        enum:
>> -          - ti,k2g-pruss
>> -          - ti,am654-icssg
>> -          - ti,j721e-icssg
>> -          - ti,am642-icssg
>> -then:
>> -  required:
>> -    - power-domains
>> +allOf:
>> +  - if:
>> +      properties:
>> +        compatible:
>> +          contains:
>> +            enum:
>> +              - ti,k2g-pruss
>> +              - ti,am654-icssg
>> +              - ti,j721e-icssg
>> +              - ti,am642-icssg
>> +    then:
>> +      required:
>> +        - power-domains
>> +
>> +  - if:
>> +      properties:
>> +        compatible:
>> +          contains:
>> +            enum:
>> +              - ti,k2g-pruss
>> +    then:
>> +      required:
>> +        - dma-coherent
>>  
>>  examples:
>>    - |
>> -- 
>> 2.32.0
>>
>>


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2021-08-03 19:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  3:19 [PATCH] dt-bindings: soc: ti: pruss: Add dma-coherent property Suman Anna
2021-08-03 10:17 ` Grygorii Strashko
2021-08-03 19:28 ` Rob Herring
2021-08-03 19:32   ` Suman Anna [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=411c54ef-6ae6-2a17-c2c4-fb19580b5513@ti.com \
    --to=s-anna@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=grzegorz.jaszczyk@linaro.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lokeshvutla@ti.com \
    --cc=robh@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).