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:   Fri, 26 May 2023 07:23:24 +0100
From:   Conor Dooley <conor.dooley@microchip.com>
To:     <Claudiu.Beznea@microchip.com>
CC:     <conor@kernel.org>, <robh+dt@kernel.org>,
        <krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
        <Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
        <daniel.lezcano@linaro.org>, <tglx@linutronix.de>,
        <wim@linux-watchdog.org>, <linux@roeck-us.net>,
        <sebastian.reichel@collabora.com>, <devicetree@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        <linux-kernel@vger.kernel.org>, <linux-watchdog@vger.kernel.org>
Subject: Re: [PATCH 3/5] dt-bindings: timer: microchip,sam9x60-pit64b:
 convert to yaml
Message-ID: <20230526-knickers-aim-e01220e6a7cd@wendy>
References: <20230525125602.640855-1-claudiu.beznea@microchip.com>
 <20230525125602.640855-4-claudiu.beznea@microchip.com>
 <20230525-straw-fidgeting-4c1099aa16fe@spud>
 <5edf3d3b-6f59-0af3-6414-940a278962bf@microchip.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="/HQ42Kwig12uCxHh"
Content-Disposition: inline
In-Reply-To: <5edf3d3b-6f59-0af3-6414-940a278962bf@microchip.com>
Precedence: bulk

--/HQ42Kwig12uCxHh
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hey Claudiu,

On Fri, May 26, 2023 at 04:47:28AM +0000, Claudiu.Beznea@microchip.com wrot=
e:
> On 25.05.2023 20:14, Conor Dooley wrote:
> >> Convert Microchip PIT64B to YAML. Along with it clock-names binding has
> >> been added as the driver needs it to get PIT64B clocks.
> > I don't think both of these PIT things need to have different binding
> > files. 90% of it is the same, just the clock-names/number - so you can
>=20
> But these are different hardware blocks with different functionalities and
> different drivers.

Having different drivers doesn't preclude having them in the same
binding provided the function/description etc are more or less
identical. I was confused by:

+description:
+  The 64-bit periodic interval timer provides the operating system schedul=
er
+  interrupt. It is designed to offer maximum accuracy and efficient manage=
ment,
+  even for systems with long response times.

+description:
+  Atmel periodic interval timer provides the operating system=E2=80=99s sc=
heduler
+  interrupt. It is designed to offer maximum accuracy and efficient manage=
ment,
+  even for systems with long response time.

Those seemed like they do the same thing to me!

Cheers,
Conor

>=20
> > combine the two into one file with an
>=20

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

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

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZHBQXAAKCRB4tDGHoIJi
0k0HAP4xl941rIgtYkOPgtuhLrM9Ru4hF5dv2W41bdPW1crkuwEAihbwcVZ/e3bx
CQbjq4bx5WilTAiRH7n/bkxRmjRe4QA=
=xmcQ
-----END PGP SIGNATURE-----

--/HQ42Kwig12uCxHh--