devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Baruch Siach <baruch@tkos.co.il>,
	linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 0/4] dt-bindings: rtc: convert multiple devices to dtschema
Date: Tue, 26 Mar 2024 14:20:33 -0500	[thread overview]
Message-ID: <20240326192033.GA3240297-robh@kernel.org> (raw)
In-Reply-To: <20240326-rtc-yaml-v3-0-caa430ecace7@gmail.com>

On Tue, Mar 26, 2024 at 02:03:22PM +0100, Javier Carrasco wrote:
> This series converts the following existing bindings to dtschema:
> 
> - armada-380-rtc
> - alphascale,asm9260-rtc
> - digicolor-rtc (moved to trivial-rtc)
> - nxp,lpc1788-rtc
> 
> All bindings include at least one compatible that is referenced in the
> existing dts (arch/arm). Those dts could be tested against the new
> bindings.
> 
> It might be worth mentioning that the reference to nxp,lpc1788-rtc in
> arch/arm/boot/dts/nxp/lpc/lpc18xx.dtsi also includes another compatible
> called nxp,lpc1850-rtc, which is not documented or supported by existing
> drivers. That generates a warning when testing against nxp,lpc1788-rtc.
> 
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
> Changes in v3:
> - alphascale-asm9260-rtc: drop unnecessary reg description.
> - nxp,lpc1788-rtc: drop unnecessary reg description.
> - Link to v2: https://lore.kernel.org/r/20240325-rtc-yaml-v2-0-ff9f68f43dbc@gmail.com
> 
> Changes in v2:
> - General: reference to rtc.yaml
> - digicolor-rtc: move to trivial-rtc
> - Link to v1: https://lore.kernel.org/r/20240323-rtc-yaml-v1-0-0c5d12b1b89d@gmail.com
> 
> ---
> Javier Carrasco (4):
>       dt-bindings: rtc: armada-380-rtc: convert to dtschema
>       dt-bindings: rtc: alphascale,asm9260-rtc: convert to dtschema
>       dt-bindings: rtc: digicolor-rtc: move to trivial-rtc
>       dt-bindings: rtc: nxp,lpc1788-rtc: convert to dtschema

Reviewed-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2024-03-26 19:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 13:03 [PATCH v3 0/4] dt-bindings: rtc: convert multiple devices to dtschema Javier Carrasco
2024-03-26 13:03 ` [PATCH v3 1/4] dt-bindings: rtc: armada-380-rtc: convert " Javier Carrasco
2024-03-26 13:03 ` [PATCH v3 2/4] dt-bindings: rtc: alphascale,asm9260-rtc: " Javier Carrasco
2024-03-26 13:03 ` [PATCH v3 3/4] dt-bindings: rtc: digicolor-rtc: move to trivial-rtc Javier Carrasco
2024-03-26 13:03 ` [PATCH v3 4/4] dt-bindings: rtc: nxp,lpc1788-rtc: convert to dtschema Javier Carrasco
2024-03-26 19:20 ` Rob Herring [this message]
2024-03-29 14:59 ` [PATCH v3 0/4] dt-bindings: rtc: convert multiple devices " Alexandre Belloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240326192033.GA3240297-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=baruch@tkos.co.il \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).