[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230522-entitle-pediatric-18da6d47df87@wendy>
Date: Mon, 22 May 2023 08:16:28 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: Romain Perier <romain.perier@...il.com>
CC: Conor Dooley <conor@...nel.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Daniel Palmer <daniel@...f.com>,
Rob Herring <robh+dt@...nel.org>, <linux-rtc@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/3] dt-bindings: rtc: Add Mstar SSD20xD RTC devicetree
bindings documentation
On Mon, May 22, 2023 at 08:47:08AM +0200, Romain Perier wrote:
> Le mer. 17 mai 2023 à 19:44, Conor Dooley <conor@...nel.org> a écrit :
> > > +properties:
> > > + compatible:
> > > + enum:
> > > + - mstar,ssd20xd-rtc
> >
> > Is this x a wildcard?
> > In general, having a specific compatible is preferred, and if there are
> > other models that are compatible we can list several "fall back" to the
> > most specific one implemented in a driver.
>
>
> The first SoC being concerned is SSD202D, so "mstar,ssd202d-rtc" ?
Sounds good to me, thanks.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists