From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Wadim Egorov <W.Egorov@phytec.de>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"upstream@lists.phytec.de" <upstream@lists.phytec.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"a.zummo@towertech.it" <a.zummo@towertech.it>
Subject: Re: [PATCH] dt-bindings: rtc: Add rv3028 to rv3032.yaml dtschema
Date: Fri, 30 Dec 2022 15:44:54 +0100 [thread overview]
Message-ID: <Y675ZsZsbQIga6fG@mail.local> (raw)
In-Reply-To: <08d74257-5f8b-31ae-8077-2c73c1430c0a@phytec.de>
On 30/12/2022 11:09:32+0000, Wadim Egorov wrote:
> Am 28.12.22 um 15:15 schrieb Krzysztof Kozlowski:
> > Your subject is a bit incorrect. You do not add rv3028 to rv3032.yaml.
> > Also drop redundant "dtschema". Instead "Extend rv3028 bindings"
> >
> >
> > On 28/12/2022 15:06, Wadim Egorov wrote:
> >> Move RV3028 RTC bindings from trivial-rtc.yaml into microcrystal,rv3032.yaml.
> >> RV3028 can have a trickle-resitor-ohms property. Make it known to dtschema.
> > I don't understand what is here made known to dtschema, so maybe drop
> > last sentence.
> >
> >> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
> >> ---
> >> .../bindings/rtc/microcrystal,rv3028.yaml | 56 +++++++++++++++++++
> >> .../devicetree/bindings/rtc/trivial-rtc.yaml | 2 -
> >> 2 files changed, 56 insertions(+), 2 deletions(-)
> >> create mode 100644 Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml
> >>
> >> diff --git a/Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml b/Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml
> >> new file mode 100644
> >> index 000000000000..4abe4756bc9b
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/rtc/microcrystal,rv3028.yaml
> >> @@ -0,0 +1,56 @@
> >> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> >> +%YAML 1.2
> >> +---
> >> +$id: http://devicetree.org/schemas/rtc/microcrystal,rv3028.yaml#
> >> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> +
> >> +title: Microchip RV-3028 RTC
> >> +
> >> +allOf:
> >> + - $ref: "rtc.yaml#"
> > Drop quotes.
> >
> >> +
> >> +maintainers:
> >> + - Alexandre Belloni <alexandre.belloni@bootlin.com>
> > This should not be maintainer of subsystem but maintainer of device
> > (unless it is the same person?).
> >
> Hi Krzysztof,
>
> who would be the maintainer for this RTC?
> I am not able to find a maintainer.
>
I am the maintainer for this RTC driver
> Can I keep Alexandre Belloni as the maintainer since there seem to be no
> maintainer for the RV3028 RTC.
>
> Regards,
> Wadim
>
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-12-30 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 14:06 [PATCH] dt-bindings: rtc: Add rv3028 to rv3032.yaml dtschema Wadim Egorov
2022-12-28 14:15 ` Krzysztof Kozlowski
2022-12-30 11:09 ` Wadim Egorov
2022-12-30 13:21 ` Krzysztof Kozlowski
2022-12-30 14:44 ` Alexandre Belloni [this message]
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=Y675ZsZsbQIga6fG@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=W.Egorov@phytec.de \
--cc=a.zummo@towertech.it \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=upstream@lists.phytec.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.