From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>,
linux-kernel@vger.kernel.org
Cc: pavel@ucw.cz, dmurphy@ti.com, linux-leds@vger.kernel.org
Subject: Re: leds: apu: drop obsolete support for apu>=2
Date: Mon, 22 Jul 2019 22:12:20 +0200 [thread overview]
Message-ID: <bb7a338b-d86d-5016-7ae2-e893e1934d96@gmail.com> (raw)
In-Reply-To: <1563202653-20994-1-git-send-email-info@metux.net>
Hi Enrico,
Thank you for the patch set.
On 7/15/19 4:57 PM, Enrico Weigelt, metux IT consult wrote:
> Hi folks,
>
>
> the legacy apu LEDs driver has been superseded by the more complete
> pcengines-apu2 platform driver, for APU >= 2. It only supports
> the three front LEDs, but lacks all the other GPIOs (eg. button
> or simsw), and conflicts with the pcengines-apu2 driver.
>
> Old APUv1 has a very different chipset.
>
> Therefore I propose dropping the apu>=2 support from the legacy
> driver, reducing it to only the old (obsolete) APUv1 boards.
Patch set applied along with the update for the patch 5/6.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2019-07-22 20:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 14:57 leds: apu: drop obsolete support for apu>=2 Enrico Weigelt, metux IT consult
2019-07-15 14:57 ` [PATCH 1/6] leds: apu: drop superseeded apu2/3 led support Enrico Weigelt, metux IT consult
2019-07-16 19:30 ` Pavel Machek
2019-07-17 14:28 ` Enrico Weigelt, metux IT consult
2019-07-15 14:57 ` [PATCH 2/6] leds: apu: drop enum_apu_led_platform_types Enrico Weigelt, metux IT consult
2019-07-16 19:25 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 3/6] leds: apu: drop iosize field from priv data Enrico Weigelt, metux IT consult
2019-07-16 19:25 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 4/6] leds: apu: drop profile " Enrico Weigelt, metux IT consult
2019-07-16 19:26 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 5/6] leds: apu: fix error on probing failure Enrico Weigelt, metux IT consult
2019-07-16 19:28 ` Pavel Machek
2019-07-17 14:29 ` Enrico Weigelt, metux IT consult
2019-07-17 16:37 ` Jacek Anaszewski
2019-07-22 12:08 ` [PATCH v2] leds: apu: fix error message " Enrico Weigelt, metux IT consult
2019-07-22 12:26 ` Pavel Machek
2019-07-15 14:57 ` [PATCH 6/6] leds: apu: add pr_fmt prefix for better log output Enrico Weigelt, metux IT consult
2019-07-16 19:28 ` Pavel Machek
2019-07-22 20:12 ` Jacek Anaszewski [this message]
2019-08-29 9:08 ` leds: apu: drop obsolete support for apu>=2 Enrico Weigelt, metux IT consult
2019-08-29 19:51 ` Jacek Anaszewski
2019-09-24 12:42 ` Enrico Weigelt, metux IT consult
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=bb7a338b-d86d-5016-7ae2-e893e1934d96@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=dmurphy@ti.com \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).