linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Oleh Kravchenko <oleg@kaa.org.ua>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: add LED driver for CR0014114 board
Date: Thu, 28 Sep 2017 17:24:37 +0200	[thread overview]
Message-ID: <20170928152437.GB2482@amd> (raw)
In-Reply-To: <026d9ec2-f2bd-18b9-d5fa-f593d40e2f57@kaa.org.ua>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Hi!

> > Ok, makes sense. How does the board look?
> 
> Did you mean a photo? Sure http://i.imgur.com/OShLIJx.jpg

Thanks.

> >> The delay between data sends to SPI board should be at least 10 ms
> >> I think it will be bad idea to use shared workqueue from kernel,
> >> so I create separate single threaded work queue :)
> > 
> > If workqueue support in led core can not take 10 msec wait, we should
> > fix it, not add hacks around...
> 
> Could you please explain or give a example?
> Because it's not clear for me, how I can use it.

You use cdev.brightness_set_blocking instead of brightness_set...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2017-09-28 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-12  9:09 [PATCH] leds: add LED driver for CR0014114 board Oleh Kravchenko
2017-08-12  9:30 ` Pavel Machek
2017-08-12 10:28   ` Oleh Kravchenko
2017-08-12 10:56     ` Pavel Machek
2017-08-12 11:34       ` Oleh Kravchenko
2017-08-12 17:46         ` Pavel Machek
2017-08-12 18:50           ` Oleh Kravchenko
2017-08-12 19:13             ` Pavel Machek
2017-08-12 19:39               ` Oleh Kravchenko
2017-09-28 15:24                 ` Pavel Machek [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=20170928152437.GB2482@amd \
    --to=pavel@ucw.cz \
    --cc=linux-leds@vger.kernel.org \
    --cc=oleg@kaa.org.ua \
    /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).