dt-bindings: soc: renesas: Move renesas.yaml from arm to soc

renesas.yaml lists out all the Renesas SoC's and the platforms/EVK's which
is either ARM32/ARM64. It would rather make sense if we move renesas.yaml
to the soc/renesas folder instead. This is in preparation for adding a new
SoC (RZ/Five) from Renesas which is based on RISC-V.

While at it drop the old entry for renesas.yaml from MAINTAINERS file and
there is no need to update the new file path of renesas.yaml as we already
have an entry for Documentation/devicetree/bindings/soc/renesas/ folder.

Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
---
 .../devicetree/bindings/{arm => soc/renesas}/renesas.yaml       | 2 +-
 MAINTAINERS                                                     | 1 -
 2 files changed, 1 insertion(+), 2 deletions(-)
 rename Documentation/devicetree/bindings/{arm => soc/renesas}/renesas.yaml (99%)

On Mon, Aug 15, 2022 at 12:17:08PM +0100, Lad Prabhakar wrote:
> renesas.yaml lists out all the Renesas SoC's and the platforms/EVK's which
> is either ARM32/ARM64. It would rather make sense if we move renesas.yaml
> to the soc/renesas folder instead. This is in preparation for adding a new
> SoC (RZ/Five) from Renesas which is based on RISC-V.

Please post this as part of the above.

bindings/soc/ is just a dumping ground for stuff that doesn't fit 
anywhere. We've mostly cleaned bindings/arm/ of that, so I don't really 
want to start that again. I would propose bindings/board/ instead if we 
move in this direction.

> 
> While at it drop the old entry for renesas.yaml from MAINTAINERS file and
> there is no need to update the new file path of renesas.yaml as we already
> have an entry for Documentation/devicetree/bindings/soc/renesas/ folder.
> 
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> ---
>  .../devicetree/bindings/{arm => soc/renesas}/renesas.yaml       | 2 +-
>  MAINTAINERS                                                     | 1 -
>  2 files changed, 1 insertion(+), 2 deletions(-)
>  rename Documentation/devicetree/bindings/{arm => soc/renesas}/renesas.yaml (99%)
> 
> diff --git a/Documentation/devicetree/bindings/arm/renesas.yaml b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> similarity index 99%
> rename from Documentation/devicetree/bindings/arm/renesas.yaml
> rename to Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> index ff80152f092f..7aae35c5f6aa 100644
> --- a/Documentation/devicetree/bindings/arm/renesas.yaml
> +++ b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> @@ -1,7 +1,7 @@
>  # SPDX-License-Identifier: GPL-2.0
>  %YAML 1.2
>  ---
> -$id: http://devicetree.org/schemas/arm/renesas.yaml#
> +$id: http://devicetree.org/schemas/soc/renesas/renesas.yaml#
>  $schema: http://devicetree.org/meta-schemas/core.yaml#
>  
>  title: Renesas SH-Mobile, R-Mobile, and R-Car Platform Device Tree Bindings
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e3058091899f..e42a7524e3f1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2658,7 +2658,6 @@ S:	Supported
>  Q:	http://patchwork.kernel.org/project/linux-renesas-soc/list/
>  C:	irc://irc.libera.chat/renesas-soc
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git next
> -F:	Documentation/devicetree/bindings/arm/renesas.yaml
>  F:	Documentation/devicetree/bindings/hwinfo/renesas,prr.yaml
>  F:	Documentation/devicetree/bindings/soc/renesas/
>  F:	arch/arm64/boot/dts/renesas/
> -- 
> 2.17.1
> 
>

Hi Rob,

On Tue, Aug 16, 2022 at 6:41 PM Rob Herring <robh@kernel.org> wrote:
>
> On Mon, Aug 15, 2022 at 12:17:08PM +0100, Lad Prabhakar wrote:
> > renesas.yaml lists out all the Renesas SoC's and the platforms/EVK's which
> > is either ARM32/ARM64. It would rather make sense if we move renesas.yaml
> > to the soc/renesas folder instead. This is in preparation for adding a new
> > SoC (RZ/Five) from Renesas which is based on RISC-V.
>
> Please post this as part of the above.
>
Sure, I just wanted to get some feedback on this so had it posted separately.

> bindings/soc/ is just a dumping ground for stuff that doesn't fit
> anywhere. We've mostly cleaned bindings/arm/ of that, so I don't really
> want to start that again. I would propose bindings/board/ instead if we
> move in this direction.
>
OK. So to clarify, how do we separate it further bindings/board/<based
on SoC vendor> or bindings/board/<board manufacturer>?

Cheers,
Prabhakar