From: Linus Walleij <linus.walleij@linaro.org>
To: Conor Dooley <conor@kernel.org>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
Jose Vasconcellos <jvasco@verizon.net>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] rtc: rtc7301: Rewrite bindings in schema
Date: Tue, 26 Sep 2023 12:56:48 +0200 [thread overview]
Message-ID: <CACRpkdZaGJQp8965YQDspjpSMRCVDYD1eyCb+dhg3SEtRS4a_A@mail.gmail.com> (raw)
In-Reply-To: <20230922-magenta-impending-f5ade19286ae@spud>
On Fri, Sep 22, 2023 at 12:45 PM Conor Dooley <conor@kernel.org> wrote:
> On Thu, Sep 21, 2023 at 10:27:42PM +0200, Linus Walleij wrote:
> > This rewrites the Epson RTC7301 bindings to use YAML schema,
> > and adds a property for "reg-io-width" as used in several
> > other bindings to account for different register strides.
>
> It'd probably be good to mention that there is hardware that needs this,
> rather that saying "other bindings use this".
That is an explanation why I call it "reg-io-width", rather than,
say "reg-stride-bytes" as there are other bindings that use this
But I'll mention some hardware, no problem!
Yours,
Linus Walleij
next prev parent reply other threads:[~2023-09-26 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:27 [PATCH 0/2] Support byte access in the RTC7301 driver Linus Walleij
2023-09-21 20:27 ` [PATCH 1/2] rtc: rtc7301: Rewrite bindings in schema Linus Walleij
2023-09-22 10:45 ` Conor Dooley
2023-09-26 10:56 ` Linus Walleij [this message]
2023-09-22 21:19 ` Rob Herring
2023-09-21 20:27 ` [PATCH 2/2] rtc: rtc7301: Support byte-addressed IO Linus Walleij
2023-09-22 22:07 ` 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=CACRpkdZaGJQp8965YQDspjpSMRCVDYD1eyCb+dhg3SEtRS4a_A@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=a.zummo@towertech.it \
--cc=akinobu.mita@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jvasco@verizon.net \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@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 read-only IMAP folder(s) and NNTP newsgroup(s).