[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdb_j57++UkP3bPFtkY5BaBkEatTOLoBRtGjEeSB4_gvdg@mail.gmail.com>
Date: Tue, 4 Oct 2022 09:27:44 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Serge Semin <fancer.lancer@...il.com>
Cc: Sascha Hauer <s.hauer@...gutronix.de>,
Rob Herring <robh@...nel.org>,
Rob Herring <robh+dt@...nel.org>, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Bartosz Golaszewski <brgl@...ev.pl>, kernel@...gutronix.de
Subject: Re: [PATCH v3 1/2] gpio: Add gpio latch driver
On Sun, Sep 25, 2022 at 5:30 PM Serge Semin <fancer.lancer@...il.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
Powered by blists - more mailing lists