From: Pavel Machek <pavel@ucw.cz>
To: Joseph Strauss <jstrauss16@proton.me>
Cc: linux-leds@vger.kernel.org
Subject: Re: Implementing missing BlinkM LED features
Date: Sun, 21 Aug 2022 13:56:28 +0200 [thread overview]
Message-ID: <20220821115628.GA7663@duo.ucw.cz> (raw)
In-Reply-To: <20220820230337.wp7gaxzzz4qi56eb@libretux>
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
Hi!
> The BlinkM LED is a programmable full-color RGB LED with use cases including industrial design, hobbyist projects, automotive lighting, and wearables. The device is programmable in that specific commands can be send over I2C, including scripts, for more complicated lighting effects. The datasheet can be found here: https://static1.squarespace.com/static/5c155684f407b4100552994c/t/5c2d20ca0e2e7292108eadf8/1546461407535/BlinkM_datasheet.pdf
>
> After glancing through the source code for the existing driver, leds-blinkm.c, I noticed a TODO for implementing several of the device's key features, including setting the time adjust, fade speed, and writing and reading script lines. I would be happy to try implementing and contributing those features, but I wanted to hear some of your thoughts on it before I get started and if you think it would be worth everyone's time.
>
Take a look at pattern trigger. If you can implement that with hw
acceleration...
Actually first step may be rgb-aware pattern trigger, then same
interface with hw acceleration.
Best regards,
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-08-21 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 23:03 Implementing missing BlinkM LED features Joseph Strauss
2022-08-21 11:56 ` Pavel Machek [this message]
[not found] ` <20220821224442.dyip3dig3g2isqmi@libretux>
2022-08-22 10:35 ` Pavel Machek
2022-09-10 18:44 ` Joseph Strauss
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=20220821115628.GA7663@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=jstrauss16@proton.me \
--cc=linux-leds@vger.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).