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:   Wed, 11 May 2022 14:38:38 -0500
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
Message-ID: <20220511193838.o62nvhwfo4fgcg7l@overview>
References: <20220511002600.27964-1-nm@ti.com>
 <20220511002600.27964-2-nm@ti.com>
 <d7f124a7-a338-8ada-8d68-9434059db9fc@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <d7f124a7-a338-8ada-8d68-9434059db9fc@linaro.org>
User-Agent: NeoMutt/20171215
Precedence: bulk

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