Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 15 Aug 2023 15:19:55 +0100
From:   Conor Dooley <conor@kernel.org>
To:     Binbin Zhou <zhoubinbin@loongson.cn>
Cc:     Binbin Zhou <zhoubb.aaron@gmail.com>,
        Huacai Chen <chenhuacai@loongson.cn>,
        Thomas Gleixner <tglx@linutronix.de>,
        Marc Zyngier <maz@kernel.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Huacai Chen <chenhuacai@kernel.org>,
        loongson-kernel@lists.loongnix.cn, devicetree@vger.kernel.org,
        Jiaxun Yang <jiaxun.yang@flygoat.com>, diasyzhang@tencent.com,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interrupt-controller: loongson,liointc: Fix
 warnings about reg and interrupt description
Message-ID: <20230815-certainly-sprang-209024530924@spud>
References: <20230815084713.1627520-1-zhoubinbin@loongson.cn>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="ZyVqBzIaMuBVfm1G"
Content-Disposition: inline
In-Reply-To: <20230815084713.1627520-1-zhoubinbin@loongson.cn>
Precedence: bulk


--ZyVqBzIaMuBVfm1G
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hey,

On Tue, Aug 15, 2023 at 04:47:13PM +0800, Binbin Zhou wrote:
> As we know, some Loongson-2K CPUs are single-core, e.g. Loongson-2K0500,
> and the "isr1" means routing interrupts to core1, which should be
> optional. So add maxItems/minItems limits to reg/reg-names.
> Also, The interrupt-names attribute represents a list of parent
> interrupt names that should change with interrupts.

This should have been with the other series that introduces the users
probably so that things make more sense to the reader.

> Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>
> ---
>  .../interrupt-controller/loongson,liointc.yaml     | 14 ++++++--------
>  1 file changed, 6 insertions(+), 8 deletions(-)
>=20
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/loong=
son,liointc.yaml b/Documentation/devicetree/bindings/interrupt-controller/l=
oongson,liointc.yaml
> index 00b570c82903..adb428211a72 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/loongson,lio=
intc.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/loongson,lio=
intc.yaml
> @@ -11,7 +11,7 @@ maintainers:
> =20
>  description: |
>    This interrupt controller is found in the Loongson-3 family of chips a=
nd
> -  Loongson-2K1000 chip, as the primary package interrupt controller which
> +  Loongson-2K series chips, as the primary package interrupt controller =
which
>    can route local I/O interrupt to interrupt lines of cores.
> =20
>  allOf:
> @@ -33,6 +33,7 @@ properties:
>        - const: main
>        - const: isr0
>        - const: isr1
> +    minItems: 2
> =20
>    interrupt-controller: true
> =20
> @@ -45,11 +46,9 @@ properties:
>    interrupt-names:
>      description: List of names for the parent interrupts.
>      items:
> -      - const: int0
> -      - const: int1
> -      - const: int2
> -      - const: int3
> +      pattern: int[0-3]

=46rom a quick look at the new devicetrees, I don't understand the
ordering relaxation. Do you actually have a system that only has, for
example, int3?

Also, as the interrupt-names are not required, changing the ordering
here is not ABI compatible AFAICT. Does that have any fallout?

Thanks,
Conor.

>      minItems: 1
> +    maxItems: 4
> =20
>    '#interrupt-cells':
>      const: 2
> @@ -73,7 +72,6 @@ required:
>    - '#interrupt-cells'
>    - loongson,parent_int_map
> =20
> -
>  unevaluatedProperties: false
> =20
>  if:
> @@ -86,7 +84,8 @@ if:
>  then:
>    properties:
>      reg:
> -      minItems: 3
> +      minItems: 2
> +      maxItems: 3
> =20
>    required:
>      - reg-names
> @@ -113,7 +112,6 @@ examples:
>                                  <0x0f000000>, /* int1 */
>                                  <0x00000000>, /* int2 */
>                                  <0x00000000>; /* int3 */
> -
>      };
> =20
>  ...
> --=20
> 2.39.3
>=20

--ZyVqBzIaMuBVfm1G
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZNuJiwAKCRB4tDGHoIJi
0hS5AP0XAkJJcHVeqW/yF5gJ9Z/MyINBReOsxwdQjBgsXlPIygEA4tz9NQ2OsYWL
aB7ZCv2HblA3kM5ikbl5HscxuIBlTQg=
=By9N
-----END PGP SIGNATURE-----

--ZyVqBzIaMuBVfm1G--