From: Pavel Machek <pavel@ucw.cz>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Marek Behun <marek.behun@nic.cz>,
Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-leds@vger.kernel.org
Subject: Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia)
Date: Mon, 29 Apr 2019 20:12:45 +0200 [thread overview]
Message-ID: <20190429181245.GA24658@amd> (raw)
In-Reply-To: <c045db7f-2147-1a58-8d65-8b52fddd932c@metux.net>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Mon 2019-04-29 19:51:40, Enrico Weigelt, metux IT consult wrote:
> On 29.04.19 18:53, Pavel Machek wrote:
> >>> Theoretically. But we both now that probability of that is very low,
> >>> and that likely driver would need other updates, too... right?
> >>
> >> What would be the benefit to add ARM dependency? So that distro
> >> compilations don't ship the turris_omnia driver unnecesarily?
> >
> > That, and so that people are not asked "do you want to enable omnia
> > LEDs?" when they update their kernel on i386.
>
> Is that controller only built-in into some SoCs, or also available
> as a separate chip ?
AFAIU.. separate chip, but runs firmware not likely to be available
outside Turris routers.
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 --]
next prev parent reply other threads:[~2019-04-29 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 9:03 linux-next: Tree for Apr 29 Stephen Rothwell
2019-04-29 14:52 ` linux-next: Tree for Apr 29 (drivers/md/dm-dust) Randy Dunlap
2019-04-29 15:03 ` linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia) Randy Dunlap
2019-04-29 15:32 ` Pavel Machek
2019-04-29 15:38 ` Marek Behun
2019-04-29 16:37 ` Pavel Machek
2019-04-29 16:44 ` Marek Behun
2019-04-29 16:53 ` Pavel Machek
2019-04-29 17:51 ` Enrico Weigelt, metux IT consult
2019-04-29 18:12 ` Pavel Machek [this message]
2019-04-29 18:49 ` Enrico Weigelt, metux IT consult
2019-04-29 19:02 ` Marek Behun
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=20190429181245.GA24658@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkml@metux.net \
--cc=marek.behun@nic.cz \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).