Received-SPF: pass (google.com: domain of linux-kernel+bounces-75439-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Wed, 21 Feb 2024 20:02:02 +0000
From: Conor Dooley <conor@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "antoniu.miclaus@analog.com" <antoniu.miclaus@analog.com>,
	"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org" <krzysztof.kozlowski+dt@linaro.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"jdelvare@suse.com" <jdelvare@suse.com>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
	Zeynep Arslanbenzer <Zeynep.Arslanbenzer@analog.com>
Subject: Re: [PATCH v7 2/2] dt-bindings: rtc: add max313xx RTCs
Message-ID: <20240221-sputter-tinker-48ed252e0a0a@spud>
References: <20240219221827.3821415-1-chris.packham@alliedtelesis.co.nz>
 <20240219221827.3821415-3-chris.packham@alliedtelesis.co.nz>
 <20240220-unified-payback-13b0964c8c29@spud>
 <021800f9-c81c-41fb-b907-5cb27a8854d2@alliedtelesis.co.nz>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="B9ELagnuuN1Vwj6H"
Content-Disposition: inline
In-Reply-To: <021800f9-c81c-41fb-b907-5cb27a8854d2@alliedtelesis.co.nz>


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

On Tue, Feb 20, 2024 at 08:11:13PM +0000, Chris Packham wrote:
> On 21/02/24 08:21, Conor Dooley wrote:
> > On Tue, Feb 20, 2024 at 11:18:24AM +1300, Chris Packham wrote:

> > The one thing I do want the comment on is the number of examples.
> > I don't really see what we gain from having 3 - I'd roll the clock
> > provider example into with one of the other ones I think.
> The 3 examples are an artifact of me combining the in-flight max313xx=20
> series with the one that landed. The clock output is only valid for some=
=20
> chips but that's probably just a matter of picking the right compatible.

Yeah, I think you could collapse it in, if you modify the compatible
appropriately.

Cheers,
Conor.

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

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

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZdZWugAKCRB4tDGHoIJi
0lNjAP0Y1ftsyNZJ4jgRn5i4R/44xcHG7gHpsUafYTdx6vCcrgEAqGcNnae8VN2n
t+EY+K/WpmW6SUYPoZhTtso5WdqfIQE=
=ldv+
-----END PGP SIGNATURE-----

--B9ELagnuuN1Vwj6H--