From: Thomas Gleixner <tglx@linutronix.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
johannes.berg@intel.com, linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: trigger: Disable CPU trigger on PREEMPT_RT
Date: Mon, 27 Sep 2021 20:48:27 +0200 [thread overview]
Message-ID: <87mtnxc0sk.ffs@tglx> (raw)
In-Reply-To: <20210927154451.GA17112@duo.ucw.cz>
Pavel,
On Mon, Sep 27 2021 at 17:44, Pavel Machek wrote:
> On Mon 2021-09-27 17:35:02, Thomas Gleixner wrote:
>> Disabling stuff which is not working well with RT is very much a
>> solution in order to make progress.
>>
>> We have surely more essential problems to solve than making leds blink
>> and if anyone cares enough about them, then this can be worked on in
>> parallel. That has been disabled on RT for ever and so far nobody
>> complained or cared enough about it.
>
> Would you mind reading and responding to the rest of the email?
Sure. As Sebastian said, its not only the rwlock in led-triggers, it's
the whole call chain down to led_cdec->set_brightness() with a gazillion
of drivers and quite some of them take locks.
> I'm not applying this.
That's fine with me, I just move arch/arm RT support to the very end of
my todo list then.
Thanks for your support!
tglx
prev parent reply other threads:[~2021-09-27 18:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 11:15 [PATCH] leds: trigger: Disable CPU trigger on PREEMPT_RT Sebastian Andrzej Siewior
2021-09-27 14:23 ` Pavel Machek
2021-09-27 15:35 ` Thomas Gleixner
2021-09-27 15:44 ` Pavel Machek
2021-09-27 17:18 ` Sebastian Andrzej Siewior
2021-09-27 17:36 ` Johannes Berg
2021-09-27 19:06 ` Pavel Machek
2021-09-27 19:34 ` Sebastian Andrzej Siewior
2021-10-13 8:08 ` Pavel Machek
2021-10-13 8:39 ` Sebastian Andrzej Siewior
2021-10-13 8:42 ` Pavel Machek
2021-10-13 9:08 ` Sebastian Andrzej Siewior
2021-10-13 9:37 ` [PATCH v2] " Sebastian Andrzej Siewior
2021-10-13 18:08 ` Pavel Machek
2021-09-28 0:14 ` [PATCH] " Thomas Gleixner
2021-09-27 18:48 ` Thomas Gleixner [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=87mtnxc0sk.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=johannes.berg@intel.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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