From: Markus Moll <moll.markus@arcor.de>
To: Rob Herring <robh@kernel.org>
Cc: Pavel Machek <pavel@ucw.cz>, Dan Murphy <dmurphy@ti.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 2/2] dt: bindings: pca9532: add description of pwm and psc settings
Date: Tue, 29 Sep 2020 20:56:02 +0200 [thread overview]
Message-ID: <4565211.GXAFRqVoOG@x2> (raw)
In-Reply-To: <20200929181409.GA890687@bogus>
Am Dienstag, 29. September 2020, 20:14:09 CEST schrieb Rob Herring:
>
> I believe we have standard properties for LED patterns now.
>
Oh... I guess I had completely misunderstood how the timer trigger works.
It's quite possible that the timer trigger + the led-pattern property will
solve all of the problems I originally had and thus eliminate the need for my
device-tree patches.
Markus
prev parent reply other threads:[~2020-09-29 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 19:33 [PATCH v1 2/2] dt: bindings: pca9532: add description of pwm and psc settings Markus Moll
2020-09-29 18:14 ` Rob Herring
2020-09-29 18:56 ` Markus Moll [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=4565211.GXAFRqVoOG@x2 \
--to=moll.markus@arcor.de \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@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 NNTP newsgroup(s).