From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: leds-atmel-pwm and atmel-pwm-bl removal
Date: Fri, 14 Mar 2014 20:49:30 +0100 [thread overview]
Message-ID: <20140314194930.GF3106@piout.net> (raw)
Hi,
With the new generic pwm framework and the pwm-atmel driver using it, we
don't need leds-atmel-pwm or atmel-pwm-bl anymore. However, a few boards
are still using those:
arch/arm/mach-at91/board-sam9263ek.c
arch/arm/mach-at91/board-sam9m10g45ek.c
arch/avr32/boards/atngw100/mrmt.c
arch/avr32/boards/merisc/setup.c
arch/avr32/boards/favr-32/setup.c
Some other avr32 boards are compiling it as a module but don't seem to
make any use of it.
I will take care of the mach-at91 boards and I can test on those. I can
do the same for the avr32 boards but I won't be able to test (only
to compile). Is anyone of you interested in testing those changes ?
I couldn't reach the initial authors of those files...
Could we simply remove the driver from the avr32 boards ? I'm under the
impression that they don't get much interest anyway, since april 2009,
I only see tree wide changes and I can't believe they didn't get broken
a way or another.
Regards,
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Haavard Skinnemoen <hskinnemoen@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Nicolas Ferre <nicolas.ferre@atmel.com>
Subject: leds-atmel-pwm and atmel-pwm-bl removal
Date: Fri, 14 Mar 2014 20:49:30 +0100 [thread overview]
Message-ID: <20140314194930.GF3106@piout.net> (raw)
Hi,
With the new generic pwm framework and the pwm-atmel driver using it, we
don't need leds-atmel-pwm or atmel-pwm-bl anymore. However, a few boards
are still using those:
arch/arm/mach-at91/board-sam9263ek.c
arch/arm/mach-at91/board-sam9m10g45ek.c
arch/avr32/boards/atngw100/mrmt.c
arch/avr32/boards/merisc/setup.c
arch/avr32/boards/favr-32/setup.c
Some other avr32 boards are compiling it as a module but don't seem to
make any use of it.
I will take care of the mach-at91 boards and I can test on those. I can
do the same for the avr32 boards but I won't be able to test (only
to compile). Is anyone of you interested in testing those changes ?
I couldn't reach the initial authors of those files...
Could we simply remove the driver from the avr32 boards ? I'm under the
impression that they don't get much interest anyway, since april 2009,
I only see tree wide changes and I can't believe they didn't get broken
a way or another.
Regards,
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2014-03-14 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 19:49 Alexandre Belloni [this message]
2014-03-14 19:49 ` leds-atmel-pwm and atmel-pwm-bl removal Alexandre Belloni
2014-03-16 17:28 ` Hans-Christian Egtvedt
2014-03-16 17:28 ` Hans-Christian Egtvedt
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=20140314194930.GF3106@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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.