From: Nishanth Menon <nm@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-rtc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Andrew Davis <afd@ti.com>
Subject: Re: [PATCH V2 1/2] dt-bindings: rtc: Add TI K3 RTC description
Date: Wed, 11 May 2022 14:38:38 -0500 [thread overview]
Message-ID: <20220511193838.o62nvhwfo4fgcg7l@overview> (raw)
In-Reply-To: <d7f124a7-a338-8ada-8d68-9434059db9fc@linaro.org>
On 18:28-20220511, Krzysztof Kozlowski wrote:
> On 11/05/2022 02:25, Nishanth Menon wrote:
[...]
>
> I didn't brought it earlier (I assumed you used existing RTC examples
> for your schema): why this is not including generic rtc.yaml schema?
> Isn't this a RTC?
Oversight, and I suppose I picked a bad example to emulate :(
I assume you mean adding:
allOf:
- $ref: "rtc.yaml#"
Like this:
https://gist.github.com/nmenon/0c326c92fbadecd042209c0078f0af99 ?
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-11 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 0:25 [PATCH V2 0/2] rtc: Introduce rtc-ti-k3 Nishanth Menon
2022-05-11 0:25 ` [PATCH V2 1/2] dt-bindings: rtc: Add TI K3 RTC description Nishanth Menon
2022-05-11 16:28 ` Krzysztof Kozlowski
2022-05-11 19:38 ` Nishanth Menon [this message]
2022-05-12 10:12 ` Krzysztof Kozlowski
2022-05-11 0:25 ` [PATCH V2 2/2] rtc: Introduce ti-k3-rtc Nishanth Menon
2022-05-11 0:52 ` Andrew Davis
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=20220511193838.o62nvhwfo4fgcg7l@overview \
--to=nm@ti.com \
--cc=a.zummo@towertech.it \
--cc=afd@ti.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--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 \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
/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