From: Linus Walleij <linus.walleij@linaro.org>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
Rob Herring <robh@kernel.org>, Rob Herring <robh+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>,
kernel@pengutronix.de
Subject: Re: [PATCH v3 1/2] gpio: Add gpio latch driver
Date: Tue, 4 Oct 2022 09:27:44 +0200 [thread overview]
Message-ID: <CACRpkdb_j57++UkP3bPFtkY5BaBkEatTOLoBRtGjEeSB4_gvdg@mail.gmail.com> (raw)
In-Reply-To: <20220925153002.makz5eijmwzrgqqs@mobilestation>
On Sun, Sep 25, 2022 at 5:30 PM Serge Semin <fancer.lancer@gmail.com> wrote:
> I couldn't find any generic ready-to-use DT-property for this case.
> So IMO instead the next properties would work:
> 1. "setup-duration-ns" - data input timing after which the clock input
> can be asserted (Tsu in the hw-manual above).
> 2. "clock-duration-ns" - clock input timing for which the CLK signal
> must be kept asserted so the device would perceive the input
> states, the outputs would be updated and the clock signal could be
> driven back to low (Tw including Th in the hw-manual above).
>
> @Rob, @Linus, any suggestion regarding the properties and their naming?
I think your suggestions look fine!
Yours,
Linus Walleij
next prev parent reply other threads:[~2022-10-04 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 7:13 [PATCH v3 0/2] gpio: Add gpio-latch driver Sascha Hauer
2022-09-14 7:13 ` [PATCH v3 1/2] gpio: Add gpio latch driver Sascha Hauer
2022-09-14 14:03 ` Serge Semin
2022-09-22 13:31 ` Sascha Hauer
2022-09-25 15:30 ` Serge Semin
2022-10-04 7:27 ` Linus Walleij [this message]
2022-09-18 14:56 ` Linus Walleij
2022-09-14 7:13 ` [PATCH v3 2/2] dt-bindings: gpio: Add gpio-latch binding document Sascha Hauer
2022-09-14 15:05 ` Rob Herring
2022-09-18 14:57 ` Linus Walleij
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=CACRpkdb_j57++UkP3bPFtkY5BaBkEatTOLoBRtGjEeSB4_gvdg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.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 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).