From: Sinthu Raja <[email protected]>
Hi All,
The series of patches are meant to help make the rproc bindings for K3
r5f and dsp support independent of board/platform involved.
Changes in V4:
Addressed review comments:
- Removed Fixes tags from the commit descriptions.
- Updated subject and commit description to emphasis on cleaning up of the
example to address the dt_binding_check warnings.
V3: https://lore.kernel.org/all/[email protected]/
V2: https://lore.kernel.org/all/[email protected]/
V1: https://lore.kernel.org/all/[email protected]/
Sinthu Raja (2):
dt-bindings: remoteproc: k3-r5f: Cleanup SoC compatible from DT
example
dt-bindings: remoteproc: k3-dsp: Cleanup SoC compatible from DT
example
.../devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml | 4 +---
.../devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml | 4 +---
2 files changed, 2 insertions(+), 6 deletions(-)
--
2.31.1
From: Sinthu Raja <[email protected]>
The K3 DSP binding example used the root-node with a SoC compatible
property originally to address the dt_binding_check warnings resulting
from using a value of 2 for #address-cells and #size-cells as per most
common usage on K3 SoCs. Clean this up and replace it with a generic soc
node to keep it agnostic of the SoC or board compatibles that are outside
the scope of this binding.
Signed-off-by: Sinthu Raja <[email protected]>
Acked-by: Rob Herring <[email protected]>
Acked-by: Suman Anna <[email protected]>
---
Changes since V4:
* review comment updates, including, commit message and $subject updates
& dropped Fixes tag.
V3: https://lore.kernel.org/all/[email protected]/
V2: https://lore.kernel.org/all/[email protected]/
V1: https://lore.kernel.org/all/[email protected]/
.../devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
index 6070456a7b67..5ec6505ac408 100644
--- a/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
@@ -133,9 +133,7 @@ unevaluatedProperties: false
examples:
- |
- / {
- model = "Texas Instruments K3 J721E SoC";
- compatible = "ti,j721e";
+ soc {
#address-cells = <2>;
#size-cells = <2>;
--
2.31.1
From: Sinthu Raja <[email protected]>
The K3 R5F binding example used the root-node with a SoC compatible
property originally to address the dt_binding_check warnings resulting
from using a value of 2 for #address-cells and #size-cells as per most
common usage on K3 SoCs. Clean this up and replace it with a generic soc
node to keep it agnostic of the SoC or board compatibles that are outside
the scope of this binding.
Signed-off-by: Sinthu Raja <[email protected]>
Acked-by: Rob Herring <[email protected]>
Acked-by: Suman Anna <[email protected]>
---
Changes in V4: new patch in the series.
* review comment updates, including, commit message and $subject updates
& dropped Fixes tag.
V3: https://lore.kernel.org/all/[email protected]/
.../devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
index 130fbaacc4b1..eeef255c4045 100644
--- a/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
@@ -230,9 +230,7 @@ additionalProperties: false
examples:
- |
- / {
- model = "Texas Instruments K3 AM654 SoC";
- compatible = "ti,am654-evm", "ti,am654";
+ soc {
#address-cells = <2>;
#size-cells = <2>;
--
2.31.1
On 16:08-20210927, Sinthu Raja wrote:
> From: Sinthu Raja <[email protected]>
>
> Hi All,
> The series of patches are meant to help make the rproc bindings for K3
> r5f and dsp support independent of board/platform involved.
>
> Changes in V4:
> Addressed review comments:
> - Removed Fixes tags from the commit descriptions.
> - Updated subject and commit description to emphasis on cleaning up of the
> example to address the dt_binding_check warnings.
>
>
> V3: https://lore.kernel.org/all/[email protected]/
> V2: https://lore.kernel.org/all/[email protected]/
> V1: https://lore.kernel.org/all/[email protected]/
>
> Sinthu Raja (2):
> dt-bindings: remoteproc: k3-r5f: Cleanup SoC compatible from DT
> example
> dt-bindings: remoteproc: k3-dsp: Cleanup SoC compatible from DT
> example
>
Reviewed-by: Nishanth Menon <[email protected]>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
On Mon, Sep 27, 2021 at 04:08:09PM +0530, Sinthu Raja wrote:
> From: Sinthu Raja <[email protected]>
>
> Hi All,
> The series of patches are meant to help make the rproc bindings for K3
> r5f and dsp support independent of board/platform involved.
>
> Changes in V4:
> Addressed review comments:
> - Removed Fixes tags from the commit descriptions.
> - Updated subject and commit description to emphasis on cleaning up of the
> example to address the dt_binding_check warnings.
>
>
> V3: https://lore.kernel.org/all/[email protected]/
> V2: https://lore.kernel.org/all/[email protected]/
> V1: https://lore.kernel.org/all/[email protected]/
>
> Sinthu Raja (2):
> dt-bindings: remoteproc: k3-r5f: Cleanup SoC compatible from DT
> example
> dt-bindings: remoteproc: k3-dsp: Cleanup SoC compatible from DT
> example
>
> .../devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml | 4 +---
> .../devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml | 4 +---
> 2 files changed, 2 insertions(+), 6 deletions(-)
I have applied this set.
Thanks,
Mathieu
>
> --
> 2.31.1
>