All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Ed Wildgoose <lists@wildgooses.com>, linux-kernel@vger.kernel.org
Cc: fe@dev.tdt.de, "Enrico Weigelt,
	metux IT consult" <info@metux.net>,
	Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/2] x86: Remove led/gpio setup from pcengines platform driver
Date: Mon, 12 Oct 2020 21:31:52 +0200	[thread overview]
Message-ID: <5f0efbd5-31ef-bf22-0f72-01db4118f144@metux.net> (raw)
In-Reply-To: <20200921215919.3072-1-lists@wildgooses.com>

On 21.09.20 23:59, Ed Wildgoose wrote:
> The pcengines bios/firmware includes ACPI tables (since 4.10.0.1) which
> will cause the kernel to automatically create led + gpio_key devices for
> the platform. This means that the platform setup now creates duplicates
> of all these led/key devices.

Absolutely not. This breaks a high number of machines in the field,
where FW upgrade is not an option.

> Anyone with a much older bios can use the 'leds-apu' driver to get the
> same set of led devices as created by the kernel with a modern bios.

No, this ancient and obsolete driver does not support more recent boards
and lacks lots of other important functionality, eg. keys, where
userland relies on. Never break userland.

--mtx

-- 
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

      parent reply	other threads:[~2020-10-12 19:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 21:59 [PATCH 1/2] x86: Remove led/gpio setup from pcengines platform driver Ed Wildgoose
2020-09-21 21:59 ` [PATCH 2/2] x86: Support APU5 in PCEngines " Ed Wildgoose
2020-09-21 22:17 ` [PATCH 1/2] x86: Remove led/gpio setup from pcengines " Ed W
2020-10-12 19:39   ` Enrico Weigelt, metux IT consult
2020-10-13  8:48     ` Hans de Goede
2020-10-13 21:46       ` Ed W
2020-10-19 14:28         ` Enrico Weigelt, metux IT consult
2020-10-13 21:40     ` Ed W
2020-10-14  8:41       ` Hans de Goede
2020-10-14 11:21         ` Ed W
2020-10-14 11:29           ` Hans de Goede
2020-10-21 21:54             ` Ed W
2020-10-22 11:48               ` Enrico Weigelt, metux IT consult
2020-10-22 15:10                 ` Ed W
2020-10-22 19:30                   ` Enrico Weigelt, metux IT consult
2020-10-19 15:44         ` Enrico Weigelt, metux IT consult
2020-10-19 18:37           ` Hans de Goede
2020-10-21 12:18             ` Enrico Weigelt, metux IT consult
2020-10-21 21:41             ` [PATCH 1/2] x86: Conditional init of pcengines leds/keys gpios Ed Wildgoose
2020-10-21 21:41               ` [PATCH 2/2] x86: Support APU5 & APU6 in PCEngines platform driver Ed Wildgoose
2020-10-22  0:53               ` [PATCH 1/2] x86: Conditional init of pcengines leds/keys gpios kernel test robot
2020-10-22  0:53                 ` kernel test robot
2020-10-22  9:22               ` Enrico Weigelt, metux IT consult
2020-10-22  9:38                 ` Ed W
2020-10-22 13:20                   ` Enrico Weigelt, metux IT consult
2020-10-22 12:23               ` kernel test robot
2020-10-22 12:23                 ` kernel test robot
2020-10-22 12:23               ` [RFC PATCH] x86: cmp_version() can be static kernel test robot
2020-10-22 12:23                 ` kernel test robot
2020-10-19 16:33       ` [PATCH 1/2] x86: Remove led/gpio setup from pcengines platform driver Enrico Weigelt, metux IT consult
2020-10-12 19:31 ` Enrico Weigelt, metux IT consult [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=5f0efbd5-31ef-bf22-0f72-01db4118f144@metux.net \
    --to=lkml@metux.net \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=fe@dev.tdt.de \
    --cc=info@metux.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@wildgooses.com \
    --cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.